This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Since XQuery 3.0 supports the namespace access the dependency should be changed to <dependency type="spec" value="XQ10"/> for the test <test-case name="K2-Axes-54"> <description> The namespace axis is not recognized in XQuery.</description> <created by="Frans Englich" on="2007-11-26+01:00"/> <dependency type="spec" value="XQ10+"/> <test>namespace::*</test> <result> <error code="XPST0003"/> </result> </test-case>
Have I missed something? I wish that XQuery 3.0 did support the namespace axis (now that it supports namespace nodes), but the Dec 2011 draft says twice that it does not, and emotions in the XQuery WG on this topic run sufficiently high that I would not dare to propose changing this.
No, it looks as if it is me who is confused, however, I'm sure I've just introduced support for the namespace axis in XQuery 3.0 to get some test or other to pass. On investigation, it turns out that fn-name-27 fn-string-27 have a dependency on the "namespace-axis" feature rather than a dependency on the specification version. Would it be worth removing the little used "namespace-axis" dependency in favour of a specification dependency? It's only used a few times in fn/generate-id.xml (twice) fn/local-name.xml (once) fn/name.xml (once) fn/path.xml (thrice) fn/string.xml (once) I too wish there wasn't this difference between XPath and XQuery. It's just confusing.
I think we need to retain the namespace-axis dependency to distinguish between XPath processors that support the feature and those that don't, but we could make life a bit easier by ensuring that any test that depends on this feature also has a spec dependency on XPath.
Good point. I'll close this report.