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

[Bug 3122] [XPath] Things we ought to say about errors

From: <bugzilla@wiggum.w3.org>
Date: Wed, 19 Apr 2006 19:41:36 +0000
To: public-qt-comments@w3.org
Message-Id: <E1FWIYS-0003zN-Ko@wiggum.w3.org>


           Summary: [XPath] Things we ought to say about errors
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XPath
        AssignedTo: chamberl@almaden.ibm.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org

I am raising this in response to action A-296-001.

There are some things we don't say about errors that we probably should say.

In 2.3.1, after para 5 ("The outcome of the static analysis phase...") add:

In many implementations the static analysis phase will run to completion before
the dynamic evaluation phase starts, and therefore an [expression|query] will
neither return a result nor raise a dynamic error if there are any static
errors present. However, this specification does not rule out strategies such
as on-demand linking of modules in which static analysis runs in parallel with
dynamic evaluation, and this may result in varying error behavior.

If more than one error is present, or if an error condition comes within the
scope of more than one error defined in this specification, then any non-empty
subset of these errors may be reported.
Received on Wednesday, 19 April 2006 19:41:39 UTC

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