W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > July to September 2005

[Bug 2173] R-175: Questions re: normalizedString

From: <bugzilla@wiggum.w3.org>
Date: Wed, 14 Sep 2005 18:11:45 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1EFbjV-0006xG-M0@wiggum.w3.org>


           Summary: R-175: Questions re: normalizedString
           Product: XML Schema
           Version: 1.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSD Part 2: Datatypes
        AssignedTo: cmsmcq@w3.org
        ReportedBy: sandygao@ca.ibm.com
         QAContact: www-xml-schema-comments@w3.org

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:

Henry's response:
Received on Wednesday, 14 September 2005 18:11:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:04 UTC