W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2010

[Bug 11446] Provide alternate result for test K2-Literals-1

From: <bugzilla@jessica.w3.org>
Date: Wed, 01 Dec 2010 09:37:08 +0000
To: public-qt-comments@w3.org
Message-Id: <E1PNj7c-0005sj-0u@jessica.w3.org>

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
                 CC|                            |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> 2010-12-01 09:37:07 UTC ---
Please let's stop torturing ourselves in this way.

Let's be clear: with static errors, there is never one absolutely correct error
code. A static error means that your input text is not in the space of legal
XQuery input texts. The art of finding a good error message is to identify the
nearest legal XQuery in the space of all possible inputs, and to tell the user
how the actual input differs from the legal XQuery that you think he intended.
That will never be a precise art, and we can never legislate that all products
will search for the nearest legal XQuery in the same way.

That's why the test suite rules clearly say that producing the right error code
is not necessary to claim a pass. This is particularly true for static errors.
(For dynamic errors, the situation is a little different, and with try/catch
there is a good incentive to try to achieve interoperability. But for static
errors there is none.)

So please let's stop beating our heads against this brick wall. 

If we add XPST0003 as an expected result for this test then we should add it as
an expected result for every single test that produces a static error, and that
would be crazy.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 1 December 2010 09:37:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:33 UTC