W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2011

[Bug 14921] [XQ30] RestrictedChar

From: <bugzilla@jessica.w3.org>
Date: Sat, 10 Dec 2011 18:51:18 +0000
To: public-qt-comments@w3.org
Message-Id: <E1RZS10-0007ud-M8@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14921

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #3 from Michael Kay <mike@saxonica.com> 2011-12-10 18:51:18 UTC ---
>XML 1.1 allows characters #x7F through #x9F only as character
references, so implementations that support XML 1.1 must also allow these
characters only as character references, they cannot be used directly.

My only quibble with this is the implication that "an implementation that
supports XML 1.1" cannot also support XML 1.0. This sentence seems to impose
some kind of obligation, which has not previously been present, for processors
to support one or the other but not both. Is there an implication here, for
example, that if a 1.0 feature (such as the character x80) is used in one
module of the query, then a 1.1 feature (such as the character x07) cannot be
used in another?

I am reopening, because I think this needs further discussion.

-- 
Configure bugmail: https://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 Saturday, 10 December 2011 18:51:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:37 UTC