[tei-council] Internationalised domains
Stuart A. Yeates
syeates at gmail.com
Fri Oct 7 23:37:44 EDT 2011
On Sat, Oct 8, 2011 at 9:52 AM, Kevin Hawkins
<kevin.s.hawkins at ultraslavonic.info> wrote:
> On 10/7/2011 4:31 PM, Stuart A. Yeates wrote:
>> I am proposing that we prescribe using a specific encoding for at
>> least the file part of URLs.
>> My rationale for that is that without encoding there is (a) ambiguity
>> about where one URL stops and another starts in lists of 1–∞ URLs and
>> (b) ambiguity about whether the URL is encoded leading to issues with
>> generic conversion to HTML, ODF, RDF, etc needing to guess the
>> encoding of URLs and sometimes getting it wrong.
>> To return to the original question, the answer is: No, I suggest we
>> revise http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.pointer.html
>> to follow RFC 3987 in all details. I further suggest that we include
>> some motivating / worked examples.
> Okay, so to make sure others understand that this isn't a typo, you want
> to change the definition of data.pointer from RFC 3986 to RFC 3987. I
> suppose the declaration would also change from
> data.pointer = xsd:anyURI
> data.pointer = xsd:anyIRI
RFC 3987 describes in some detail how to map IRIs to URIs so this
change is not necessary.
More information about the tei-council