W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2007

[Bug 2388] Required static error checking unduly constraints implementations

From: <bugzilla@wiggum.w3.org>
Date: Tue, 03 Apr 2007 23:05:07 +0000
To: public-qt-comments@w3.org
Message-Id: <E1HYs3n-00025t-1g@wiggum.w3.org>


mike@saxonica.com changed:

           What    |Removed                     |Added
             Status|CLOSED                      |REOPENED
         Resolution|LATER                       |

------- Comment #3 from mike@saxonica.com  2007-04-03 23:05 -------
Despite Jim Melton's administrative closure of this bug, the WG reviewed it on
15 March 2007 and felt that there was room for further clarification of the
text, which the editor was asked to propose.


In 2.9, in the definition of "static error", change "An error that is detected
by examining a stylesheet before execution starts" to "An error that can be
detected by examining a stylesheet before execution starts".

I feel that this simple change is sufficient to remove any implication that
static analysis and error detection must complete before evaluation starts,
while retaining the rule that if static errors are present, they must be
reported. We already have the rule "If more than one error arises, an
implementation is not required to signal any errors other than the first one
that it detects. It is implementation-dependent which of the several errors is
signaled. This applies both to static errors and to dynamic errors.", which
implies that if both static and dynamic errors are present, the system is
allowed to report a dynamic error in preference to a static error.
Received on Tuesday, 3 April 2007 23:05:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:33 UTC