[Bug 5738] [XQuery] Constraints on schemas

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


Jonathan Robie <jonathan.robie@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jonathan.robie@redhat.com




--- Comment #3 from Jonathan Robie <jonathan.robie@redhat.com>  2008-07-29 17:57:05 ---
I don't think there's a technical bug in the original spec, but I do think some
further clarification would be good. I think the best solution is to simply add
the following note in 2.2.5, before the bulleted list:

<add>
Note: The in-scope schema definitions can be augmented by the implementation,
and may include schema components not explicitly imported in a query. See C.1
Static Context Components.
</add>

An implementation could choose to add all schemas associated with a collection
to the ISSD, or to add all schemas used to validate a given document before
processing that document. I think that's what the document says today, and I
don't think we can change that as a bug fix.

Here's my trace of the spec::

2.1.1 Static Context
<Jonathan> [Definition: The static context of an expression is the information
that is available during static analysis of the expression, prior to its
evaluation.] This information can be used to decide whether the expression
contains a static error. If analysis of an expression relies on some component
of the static context that has not been assigned a value, a static error is
raised [err:XPST0001].
The individual components of the static context are summarized below. Rules
governing the scope and initialization of these components can be found in C.1
Static Context Components.

-->
http://www.w3.org/TR/xquery/#id-xq-static-context-components

That table clearly says the ISSD is augmentable by a query processor, and may
include types not in the built-in types and not explicitly imported by the
user.

This flexibility is intentional - we discussed it at great length early in the
history of the Working Group. It does lead to query portability issues, like
everything else that is augmentable in Appendix C.1. A query that relies on any
of that is not portable.


-- 
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 Tuesday, 29 July 2008 17:57:41 UTC