- From: <bugzilla@jessica.w3.org>
- Date: Sat, 13 Sep 2014 16:19:56 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26788 Bug ID: 26788 Summary: [XPath30] XQuery-only errors in XPath 3.0 specification, like XQST0134 Product: XPath / XQuery / XSLT Version: Recommendation Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: XPath 3.0 Assignee: jonathan.robie@gmail.com Reporter: abel.braaksma@xs4all.nl QA Contact: public-qt-comments@w3.org Some errors seem to have gotten their way into the XPath 3.0 Recommendation (also the internal XPath 3.1 Draft) that are by name and intend XQuery-specific. err:XQST0134: XQuery 3.0 does not support the namespace axis. This error serves an XQuery-specific case. I think that both the error condition and the error code should be removed. If not, then it makes sense to rename the error code to XPST0134, in line with the naming conventions of XPath errors. Furthermore, the way it is written currently under 3.3.5, it appears that XPath 3.0 normatively prohibits the namespace axis, as the text says "if the NodeTest in an axis step is a NamespaceNodeTest then... error", but in the Note following the text, it makes this XQuery-specific. I think the following should be valid XPath: @namespace-node() Other cases, merely editorial, using the wrong naming conventions: err:XQST0039: "It is a static error for an inline function expression to have more than one parameter with the same name." Should be renamed XPST0039. err:XQST0046: "An implementation MAY raise a static error if the value of a BracedURILiteral is of nonzero length and is neither an absolute URI nor a relative URI." Should be renamed XPST0046. err:XQST0052: "The type must be the name of a type defined in the in-scope schema types, and the {variety} of the type must be simple." Should be renamed XPST0052. err:XQST0070: "A static error is raised if one of the predefined prefixes xml or xmlns appears in a namespace declaration or a default namespace declaration[...]" Should be renamed XPST0070. Note: in the current internal XPath 3.1 draft, err:XQDY0136, err:XQDY0137 have been introduced that ought to be errXPDY0136 and err:XPDY0137 respectively. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 13 September 2014 16:19:57 UTC