- From: Paul Grosso <pgrosso@arbortext.com>
- Date: Mon, 23 Jun 2003 16:02:46 -0500
- To: elharo@metalab.unc.edu
- Cc: www-xml-blueberry-comments@w3.org
In response to your email to the XML 1.1 CR recorded at http://lists.w3.org/Archives/Public/www-xml-blueberry-comments/2002Oct/0002.html the XML Core WG generated, discussed, and resolved the follow issue: Issue Harold-02: normalization in XML 1.1 Summary resolution: rejected Response -------- Regarding "Even if the document isn't transformed into normalized form, the processor might still validate against the normalized form." This is not true; the definition of match (unchanged in XML 1.0) is explicit: Characters with multiple possible representations in ISO/IEC 10646 (e.g., characters with both precomposed and base+diacritic forms) match only if they have the same representation in both strings. Regarding "parsers should be required to continue processing correctly after encountering non-normalized text." While interoperability is of great importance, the XML specification tries to allow leeway for various processors to handle questionable input in ways appropriate to their designed use. As noted, this is not the only place in the specification where such flexibility is permitted. The XML Core WG has consensus on the status quo wording here which leaves it open to implementations how to "report to the application" in the case of input that is not fully normalized. ======== Please let us know whether you accept our resolution of our comment, or wish to have an objection formally recorded. If we do not hear from you within 10 days we will assume that you accept our response (though we would prefer to hear from you in any case if practical). Thank you for your interest in the XML 1.1. Paul Grosso for the XML Core WG
Received on Monday, 23 June 2003 17:04:50 UTC