- From: <bugzilla@jessica.w3.org>
- Date: Fri, 09 Oct 2015 18:00:50 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29190
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mike@saxonica.com
--- Comment #2 from Michael Kay <mike@saxonica.com> ---
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 9 October 2015 18:00:54 UTC