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

[Bug 13869] New: XML10-4ed-Excluded-char-{1,2} incorrect

From: <bugzilla@jessica.w3.org>
Date: Mon, 22 Aug 2011 19:54:35 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-13869-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13869

           Summary: XML10-4ed-Excluded-char-{1,2} incorrect
           Product: XML Query Test Suite
           Version: 1.0.3
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XML Query Test Suite
        AssignedTo: benjie.nguyen@gmail.com
        ReportedBy: jmdyck@ibiblio.org
         QAContact: public-qt-comments@w3.org


(1)
The description for test-case XML10-4ed-Excluded-char-1 states:
    "The character #x037E is excluded from the start of a Name
    in XML 1.0 4th edition and older."

But as far as I can tell, that character has been excluded from the start of a
Name in *all* editions of XML 1.0 -- editions up to the 4th have:
    [85] BaseChar ::= ... | [#x02BB-#x02C1] | #x0386 | ...
and the 5th edition has:
    [4] NameStartChar ::= ... | [#x370-#x37D] | [#x37F-#x1FFF] | ...
(And similarly for both editions of XML 1.1.)

(2)
Conversely, the description for XML10-4ed-Excluded-char-2 states:
    "The character #x0100 is excluded from the start of a Name
    in XML 1.0 4th edition and older."

But that character has been *allowed* at the start of a Name in all editions of
XML 1.0 -- editions up to the 4th have:
    [85] BaseChar ::= ... | [#x0100-#x0131] | ...
and the 5th edition has:
    [4] NameStartChar ::= ... | [#xF8-#x2FF] | ...
(And similarly for both editions of XML 1.1.)

(3)
Moreover, in both cases, the associated query does not test the stated
assertion:
-- The query for -1 contains a would-be Name whose first two characters
   are 0x03 and 0x7E, but the UTF-8 encoding of U+037E is 0xCD 0xBE.
-- The query for -2 contains a would-be Name whose first two characters
   are 0x01 and 0x00, but the UTF-8 encoding of U+0100 is 0xC4 0x80.

(In each case,  one of the expected results is a parse error, so a conforming
implementation will pass, as it will raise a parse error because U+0003 and
U+0001 are disallowed.)

-- 
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, 22 August 2011 19:54:37 UTC

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