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

[Bug 9931] Error codes for QName attributes in result-document

From: <bugzilla@jessica.w3.org>
Date: Wed, 16 Jun 2010 16:18:38 +0000
To: public-qt-comments@w3.org
Message-Id: <E1OOvK2-0003eP-0H@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9931





--- Comment #3 from Michael Kay <mike@saxonica.com>  2010-06-16 16:18:37 ---
Personal response: I think it's worth pointing out that the error codes in XSLT
2.0 are not intended to be a conformance issue. See section 2.9:

<quote>These error codes are used to label error conditions in this
specification, and are summarized in E Summary of Error Conditions). They are
provided primarily for ease of reference. Implementations may use these codes
when signaling errors, but they are not required to do so. </quote>

Following this reasoning, test cases publish an expected error code, but an
implementation is not required to deliver the exact same error code in order to
pass the test.

The introduction of try/catch in XSLT 2.1 means we may have to be a bit more
prescriptive about error codes in future, especially those for dynamic errors,
and this feedback is therefore useful. However, I don't think that a failure to
be 100% prescriptive about which error code to raise in every situation should
be regarded as a bug in the 2.0 specification; we never intended to achieve
that level of predictability.

-- 
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, 16 June 2010 16:18:39 UTC

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