[Bug 26788] [XPath30] XQuery-only errors in XPath 3.0 specification, like XQST0134

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26788

--- Comment #12 from Jonathan Robie <jonathan.robie@gmail.com> ---
(In reply to Abel Braaksma from comment #10)
> 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

We have a 3.0 Recommendation that uses those error codes, so we can't really
change them now.  Imagine a world in which moving from 3.0 to 3.1 changes the
error codes that you get for the same error conditions ... especially if you
have written code that depends on those codes.

I did mention this in the Working Group telcon, and the Working Group affirmed
that we should not change these codes now.  One person made the very valid
observation that we would have been better off with codes that do not identify
the specification, since error conditions are shared across specifications and
what is used by a given specification can change over time.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 2 October 2014 11:45:48 UTC