This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the Microsoft DataTypes tests, test QName009, the following instance is considered to be valid <?xml version='1.0'?> <root xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:noNamespaceSchemaLocation="QName.xsd" > <simpleTest>xmlns:xsi</simpleTest> </root> where simpleTest is of type QName. The spec says (in a Note!) "The mapping between literals in the ·lexical space· and values in the ·value space· of QName requires a namespace declaration to be in scope for the context in which QName is used." According to the Infoset (and the same is true of XDM) "[in-scope namespaces] does not contain an item with the prefix xmlns (used for declaring namespaces), since an application can never encounter an element or attribute with that prefix" Therefore I think that xmlns:xsi is an invalid QName and this instance is therefore invalid.
This issue in the test suite in due to a corresponding issue in the Microsoft Schema processors. The fix will be addressed in a future release. Agreed that the test case should be changed to 'invalid'.
There was discussion on this but no decision on 21 June 2008. It was felt worthy of wider WG discussion.
Although Namespace spec. uses similar language about xml 'prefix' and xmlns 'prefix', the Infoset spec. says no binding for xmlns is present, and XSLT 2.0 explicitly rules it out.
WG agreed on 2010-02-05 telcon that there is no binding for xmlns as a prefix, so these are not valid QNames. HST will change the metadata to instance invalid
instance test now marked as invalid in metadata, per above decision