- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Oct 2014 02:09:49 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26788 --- Comment #10 from Abel Braaksma <abel.braaksma@xs4all.nl> --- Are you sure it is fixed in 3.1 (the part on the error codes, I mean)? Because the LCWD of XPath 3.1 currently present at https://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xpath-31.html (member only) still mentions the XQuery-only error-codes: err:XQST0039, should be err:XPST0039 err:XQST0046, should be err:XPST0046 err:XQST0052, should be err:XPST0052 err:XQST0070, should be err:XPST0070 err:XQST0134, should be err:XPST0134 err:XQDY0137, should be err:XPST0137 or am I speaking too soon and was the change not published yet? Or, in response to: > I don't think we can change the names of error conditions that have > appeared in a Recommendation now. We should discuss how to handle 3.0 > errata in a telcon. Did you mean by that that you cannot change them in subsequent versions of the spec either? Because I was under the impression that error codes were changed between versions (think of the XSLT errors for XSLT 2.0 functions that moved to XPath 3.0 and the errors were renumbered). And if you have: a) mention them in an errata for 3.0 b) change them in subsequent versions then wouldn't that suffice? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 2 October 2014 02:09:51 UTC