This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The value space of normalizedString allows all characters except xD, xA, and x9. The lexical space allows all characters except xD and x9. What is the mapping from the lexical space to the value space: what happens to an xA character in the lexical space (is it removed? replaced by an x20?). The canonical lexical representation, presumably, is the same as the string in the value space: I think we should be told. Presumably the lexical space represents the value after the XML parser has done its normalization. So in practice, a tab character is allowed in an attribute of type normalizedString (because the XML parser will turn it to a space), but a tab character is not allowed in an element of type normalizedString (because the XML parser will leave it unchanged). Is this interpretation correct? I find it hard to understand why the lexical space doesn't allow any string, with a mapping to the value space achieved by normalizing whitespace characters. Alternatively, the lexical space should be identical to the value space. The current definition seems nonsensical. See question 1 from the following: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0026.html Henry's response: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JulSep/0036.html
Discussed at the Sept. 27 concall. Resolution: The lexical and value spaces should be described in the same way (the more restrictive way). AM: fix 3.3.1. RESOLVED: to classify R-175 as error with erratum and to align the correction with R-83 (bug 2073), E2-17. Proposed text: http://lists.w3.org/Archives/Member/w3c-xml-schema- ig/2002Oct/att-0002/01-ErrataR-175.html was approved at the Oct. 4 telecon.
Fixed in the published 1.0 2E [1]. [1] http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#normalizedString