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

[Bug 4595] 1.0.3dev: document(*) with undefined context item

From: <bugzilla@wiggum.w3.org>
Date: Wed, 12 Sep 2007 09:11:05 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1IVOFV-00041I-Mn@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4595


frans.englich@telia.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Comment #13 from frans.englich@telia.com  2007-09-12 09:11 -------
My apologies for the late followup.

Implementations are allowed to raise dynamic errors at compile time if they can
infer that the error allways is raised at runtime. However,
concluding/inferring that for instance K2-NodeTest-25:

document-node(schema-element(notBound:ncname))

will raise XPDY0002 at runtime, does not hold since the query cannot be run at
all, as I see it. "A dynamic error is an error that must be detected during the
dynamic evaluation phase and may be detected during the static analysis phase."
The dynamic error can never occur since the query cannot be evaluated, and
hence there's no dynamic error to detect at compile.

The conclusion of this is that a dynamic error can never be raised, not even at
compile time, if the query contains a static error. Using a simple XSL-T
script, it seems no test in XQTSCatalog.xml contradicts that.

How do you think this read?

(I can easily sympathize with the implementation issues Tim describe. It feels
these are word games with a low dignity. But what isn't, when it comes to spec
details.)
Received on Wednesday, 12 September 2007 09:11:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 December 2014 19:59:37 UTC