- From: Martin Duerst <duerst@w3.org>
- Date: Wed, 18 Aug 2004 14:50:30 +0900
- To: Chris Lilley <chris@w3.org>, public-iri@w3.org
- Cc: www-tag@w3.org, Ted Hardie <hardie@qualcomm.com>
Hello Chris, Many thanks for your comment. I have made it issue why-not-normalize-42 (see http://www.w3.org/International/iri-edit#why-not-normalize-42). A few ideas on how to deal with it below. At 22:22 04/08/11 +0200, Chris Lilley wrote: >Hello , > > > If the IRI is in an Unicode-based character encoding (for example > > UTF-8 or UTF-16): Do not normalize. Apply Step 2 directly to the > > encoded Unicode character sequence. > >I believe that I understand why this step says 'do not normalize' >(otherwise, certain Unicode strings couldnever be used in query parts, >for example). > >However, as the two preceding steps say 'normalize' and this step says >'do not normalize' the reader could be confused - or perhaps consider it >an 'obvious error'. > >Do not tease the reader like this. Please explain *why* at this stage no >normalization is performed. You definitely have a point. But as you have noticed, the explanations are already given elsewhere in the document. I think there are several things that can be done: - capitalize 'NOT', to make clear that this is not an 'obvious error'. - add a pointer to 5.3 Normalization (http://www.w3.org/International/iri-edit/draft-duerst-iri.html#normaliza (http://www.w3.org/International/iri-edit/draft-duerst-iri.html#normalization) - do both of the above Which one do you prefer? Do you think this is enough, or do you have some other idea (actual wording preferred)? Regards, Martin.
Received on Wednesday, 18 August 2004 05:51:56 UTC