W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2011

[Bug 14820] Implementation-defined features checklist

From: <bugzilla@jessica.w3.org>
Date: Mon, 14 Nov 2011 18:56:21 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1RQ1hd-00009Y-Nw@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14820

--- Comment #3 from Liam R E Quin <liam@w3.org> 2011-11-14 18:56:20 UTC ---
Well, I see what you mean. It's comparable to the difference between lexical
and value space in XSD: in XML 1.1, where the production S is used, a Unicode
NEL (#x2028) can appear, whereas it would be an error in a 1.0 document. This
is not done editorially by a direct change in the S production, but to the end
of line handling. But it is still a change to the whitespace rules, and
indirectly affects "S".

The difference starts to matter if other languages (e.g. XPath, XQuery) try to
layer on top of XML to use "S" without including the line ending rules. 
However, I don't _think_ it matters for XSD, because an XML 1.1 parser would
have been used to consume the input, and would have normalised NEL to #xA
already.

So I wouldn't want to leave unchallenged the assertion that there's no change
in whitespace rules between 1.0 and 1.1.

For xs:string, it might be worth adding a note, I agree.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 14 November 2011 18:56:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 November 2011 18:56:24 GMT