W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2016

[Bug 29811] [XSLT30] 9.6 Static Variables and Parameters

From: <bugzilla@jessica.w3.org>
Date: Mon, 05 Sep 2016 16:28:25 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29811-523-5XZatAdqxv@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29811

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
I think there are a large number of static error conditions that are covered by
the general error codes such as XTSE0010 and XTSE0020, and it's best to have a
general rules describing these rather than be too fine-grained about it.

Interoperability of error codes for static errors has never been a high
priority, and we don't want to be over-prescriptive for example by forcing
processors to check multiple static constraints in a specific order. Nor do we
want to inhibit intelligent diagnostics: for example if an attribute name is
misspelled, we don't want to require a processor to report that a required
attribute is missing, and a disallowed attribute is present, with two different
error codes.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 5 September 2016 16:28:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC