This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The validation rules for identity constraints contain constructs like: ---- For an element information item to be locally ·valid· with respect to an identity-constraint all of the following must be true: 1 The {selector}, with the element information item as the context node, evaluates to a node-set (as defined in [XPath]). [Definition:] Call this the target node set. ---- I don't think the namespace prefix bindings to be used in these evaluations are established. Suggested fix: 1) Add a property {namespace-bindings} to the identity constraint definition component, or if preferred in Schema 1.1, make {selector} a property record containing both the XPath and the bindings. In either case, the {namespace-bindings} should be a set of {prefix,namespaceNameURI} pairs. 2) Add to the XML representation mapping rules so the binding property is set. 3) Modify the validation rules to ensure that the bindings are established as context when the XPaths are evaluated.
This issue was discussed by the Schema WG at our ftf meeting 28 March 2007. It seems to be subsumed by the larger issue of specifying the static context for XPath evaluations in general, so we're closing this bug as a duplicate of the other one. *** This bug has been marked as a duplicate of bug 4419 ***
The resolution described in comment 1 applies (like bug 4419) to XSD 1.1 only. The problem is I believe still unresolved in XSD 1.0, so I'm setting the version of this bug report to 1.0 only and reopening in.