This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In verifying fixes to some problems reported against an earlier draft of XPath 2.1, I noticed a few minor editorial problems in the current XPath 3.0 draft. 1) In the first paragraph of 2.5.6.3 and in the first note in section 3.3.4, there are references to the "XQuery implementation." That should probably say one of, "implementation," "processor," or "XPath 3.0 processor." 2) In section 2.2.4, the last two paragraphs speak of "output declarations," but those are XQuery-specific. 3) There are various references in XPath 3.0 to error messages that were previously XQuery specific: err:XQST0046, err:XQST0039, err:XQST0070, err:XQST0034. It would be nice if they began with "XP" rather than "XQ" - I don't know whether you could make an editorial decision on this one, or the working groups should be consulted.
(In reply to comment #0) > In verifying fixes to some problems reported against an earlier draft of XPath > 2.1, I noticed a few minor editorial problems in the current XPath 3.0 draft. > > 1) In the first paragraph of 2.5.6.3 and in the first note in section 3.3.4, > there are references to the "XQuery implementation." That should probably say > one of, "implementation," "processor," or "XPath 3.0 processor." The only remaining use of this phrase is here: <quote section="3.3.4"> In an implementation that does not support the namespace axis, an attempt to access it it always raises an error. Thus, an XQuery implementation will always raise an error in this case, since XQuery does not support the namespace axis. The namespace axis is deprecated in XPath 2.1, but required in some languages that use XPath, including XSLT. </quote> I believe it is appropriate here - XQuery always raises an error, XPath deprecates the namespace axis but does not mandate an error, XSLT requires the namespace axis. > 2) In section 2.2.4, the last two paragraphs speak of "output declarations," > but those are XQuery-specific. Fixed. > 3) There are various references in XPath 3.0 to error messages that were > previously XQuery specific: err:XQST0046, err:XQST0039, err:XQST0070, > err:XQST0034. It would be nice if they began with "XP" rather than "XQ" - I > don't know whether you could make an editorial decision on this one, or the > working groups should be consulted. This would indeed require a Working Group decision. Stability of error messages is important. I'm keeping the bug open because of this part.
We decided not to change the error codes.