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 IdentityConstraint test set, test idL100, the schema has: <xs:key id="foo123" name="tableu"> <xs:selector xpath=".//myNS:t | .//myNS:u"/> <xs:field xpath="@*"/> </xs:key> and the instance has: <myNS:t myNS:row="1" xsi:nil="true"/> The field selector @* therefore selects two attributes, which makes it invalid. The test is described as valid. Perhaps there is some theory that the XPath expression will not select the xsi:nil attribute. I can't find any justification for this theory, however.
This issue in the test suite in due to a corresponding issue in the Microsoft Schema processors where attributes from the xsi namespaces are not counted towards the node-set members while resolving key-refs. We need clarification from the WG if such attributes should be counted or not.
We think the spec is clear in this case and the instance is therefore invalid. Decided to leave the test as it is and change the expected result.