29190 2015-10-09 14:11:18 +0000 [QT3TS] K2-Axes-54 2015-11-04 10:29:29 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Candidate Recommendation PC Windows NT CLOSED INVALID P2 normal --- 1 debbie oneil debbie mike public-qt-comments oldest_to_newest 123632 0 debbie 2015-10-09 14:11:18 +0000 XQuery 3.0 includes the error: XQST0134: XQuery 3.0 does not support the namespace axis. (With generalized wording in the XQuery 3.1 spec - XQST0134: The namespace axis is not supported.) So I think the following test should be split in two, a test for XQ10 which expects error XPST0003, and a test for XQ30+ which expects the error XQST0134: <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> 123633 1 debbie 2015-10-09 14:14:10 +0000 Should've said, the test K2-Axes-54 is in the prod-AxisStep test set. 123635 2 mike 2015-10-09 18:00:50 +0000 Hmmm. namespace::* is not allowed by the XQuery 3.1 grammar, so I think XPST0003 is appropriate. The only place XQuery tells you to raise XPST0134 is if the NodeTest in an axis step is a NamespaceNodeTest then a static error is raised [err:XQST0134]. that is, if you encounter something like a/child::namespace-node() Since that's not actually using the namespace axis, the text for XQST0134 is unhelpful, but the error texts aren't normative. XPath 3.1 defines a different error: "An implementation that does not support the namespace axis when XPath 1.0 compatibility mode is false must raise a static error [err:XPST0010] if it is used. " So I think the correct error codes are: for an axis step namespace::* - XQuery: XPST0003 - XPath: if namespace axis not supported: XPST0010 (doesn't apply to Saxon) for a node-test namespace-node(): - XQuery: XPST0134 - XPath: if namespace axis not supported: XPST0134 (doesn't apply to Saxon) If you encounter both in combination namespace::namespace-node() then I think you get to take your pick. 123674 3 debbie 2015-10-13 12:57:04 +0000 Ah ha, my mistake, thanks for the explanation. I guess the text for error XQST0134 added to my confusion, but basically I didn't understand it properly.