[tei-council] Internationalised domains

[Kevin Hawkins]

I think we can go as far as saying that whitespace must not be used in 
URIs because such use would conflict with the definition of 
data.pointer.  That is, not just "should", as Martin suggested, but "must".

(Now that I think of it, I think Lou said that P5 uses "should" wherever 
most other standards documents would use "must".  But if that's not the 
case, I stand by my suggestion.)

On 9/26/11 11:44 AM, Martin Holmes wrote:
> This only applies if people are silly enough to use whitespace in URIs.
> And if they're linking to a resource with such a URI, and they (for
> instance) copy-paste it from a browser URI box, it'll come with
> percent-escapes anyway.
>
> I really don't think this is an issue, but if we want to add a note to
> the effect that URIs containing whitespace should be appropriately
> escaped, I think that would be enough.
>
> Cheers,
> Martin
>
> On 11-09-25 12:41 PM, Stuart A. Yeates wrote:
>> Full UTF-8 in the file part of URIs would seem to be a disaster for
>> us. Without whitespace being escaped we can't have whitespace
>> separated lists of URLs, as the definition of @corresp as "1–∞
>> occurrences of data.pointer separated by whitespace" no longer works?
>>
>> cheers
>> stuart