W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2002

normalizedString

From: Cliff Binstock <binstock@pacifier.net>
Date: Wed, 13 Mar 2002 10:25:09 -0800
Message-ID: <010401c1cabd$ba820f40$280d2b42@moomoo>
To: <www-xml-schema-comments@w3.org>
Part 2, 3.3.1, "normalizedString"
says:

[Definition:]  normalizedString represents white space normalized strings. The ·value space· of normalizedString is the set of strings that do not contain the carriage return (#xD), line feed (#xA) nor tab (#x9) characters. The ·lexical space· of normalizedString is the set of strings that do not contain the carriage return (#xD) nor tab (#x9) characters. The ·base type· of normalizedString is string.

Shouldn't the lexical space of 'normalizedString' also prohibit #A?
If for some reason this is not the case (e.g., implicit conversion to
space), you should say what happens in the mapping.

Similarly, 3.3.2, "token", says:

[Definition:]  token represents tokenized strings. The ·value space· of token is the set of strings that do not contain the line feed (#xA) nor tab (#x9) characters, that have no leading or trailing spaces (#x20) and that have no internal sequences of two or more spaces. The ·lexical space· of token is the set of strings that do not contain the line feed (#xA) nor tab (#x9) characters, that have no leading or trailing spaces (#x20) and that have no internal sequences of two or more spaces. The ·base type· of token is normalizedString. 

Shouldn't 'token' likewise prohibit #D in the value and lexical spaces?
This is admittedly implied as a derivation of 'normalizedString', but
you already reiterate #A.

Thanks!

Cliff Binstock
binstock@pacifier.net
Received on Wednesday, 13 March 2002 13:34:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:15:33 UTC