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

[Bug 14921] New: [XQ30] RestrictedChar

From: <bugzilla@jessica.w3.org>
Date: Thu, 24 Nov 2011 11:10:39 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-14921-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14921

           Summary: [XQ30] RestrictedChar
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.0
        AssignedTo: jonathan.robie@gmail.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


XQuery syntax generally mimics XML, and we give license to mimic different
versions of XML.

Test case XML10-5ed-Included-char-1-new in misc-XMLEdition assumes that this
means that an XQuery processor that works according to XML 1.1 rules should
disallow an unescaped DEL character in a query. However, this seems to be
stretching the rules. DEL is a valid Char in XML 1.1; but it is a
RestrictedChar, meaning that in XML documents it cannot appear except as a
numeric character reference. XQuery allows processors to use either the XML 1.0
or XML 1.1 rules for Char, but it does not explicitly give a processor license
to enforce the restrictions associated with a RestrictedChar. Perhaps it
should. Or perhaps, for backwards compatibility, it should not.

-- 
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 Thursday, 24 November 2011 11:10:45 UTC

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