This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
(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.)
The first test has been modified at some stage to use x037F rather than x037E, so I believe it is now OK, and doing what was intended. The second test does indeed use the two characters x01 and x00 at the start of the name, rather than the single character x0100. I am modifying the description of the test to say that this is what it does; no other change is needed.