- From: Martin Duerst <duerst@w3.org>
- Date: Thu, 17 Apr 2003 17:25:32 -0400
- To: Paul Hoffman / IMC <phoffman@imc.org>, public-iri@w3.org
Hello Paul, I have tentatively thrown this text into the new section 5.2 (formerly 2.4). I'll have to work on it. Regards, Martin. At 15:41 03/04/16 -0700, Paul Hoffman / IMC wrote: >At 2:43 PM -0400 4/16/03, Martin Duerst wrote: >>Because we do not know how a particular field is treated with >>respect to text normalization, it would be inappropriate to >>allow third parties to normalize an IRI arbitrarily. This does >>not contradict the recommendation that if you create a resource, >>and an IRI for that resource, you try to be as normalized as >>possible (i.e. NFKC if possible). >> >>This is similar to the upper-case/lower-case problems in URIs. >>Some parts of an URI are case-insensitive (domain name). >>For others, it is unclear whether they are case-sensitive or >>case-insensitive, or something in between (e.g. case-sensitive, >>but if you use the wrong case, you get a result such as a >>'Multiple choices' or so). The best recipe we have there is >>that the generator uses a reasonable capitalization, and >>when transfering the URI, you don't change capitalization. > >OK, this makes sense. Adding the above text to the document (possibly with >a descriptive heading) would be valuable. > >--Paul Hoffman, Director >--Internet Mail Consortium
Received on Thursday, 17 April 2003 17:42:25 UTC