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

[Bug 13674] [XQ30] schema-element() types behave differently in different modules.

From: <bugzilla@jessica.w3.org>
Date: Fri, 30 Sep 2011 13:14:16 +0000
To: public-qt-comments@w3.org
Message-Id: <E1R9cuu-0003ck-WA@jessica.w3.org>

--- Comment #10 from Jonathan Robie <jonathan.robie@gmail.com> 2011-09-30 13:14:15 UTC ---
(In reply to comment #7)

> I propose adding to the penultimate bullet of 2.2.5 Consistency Constraints
> (which starts "For a given query, define a participating ISSD ...") the
> following: 
> <add>
> "Equivalence" here means that validating an instance against one ISSD will
> always have the same effect as validating the same instance against the other
> ISSD (that is, it will produce the same PSVI, insofar as the PSVI is used
> during subsequent processing). This means, for example, that the membership of
> the substitution group of an element declaration in one ISSD must be the same
> as that of the corresponding element declaration in the other ISSD; that the
> set of types derived by extension from a given type must be the same; and that
> in the presence of a strict or lax wildcard, the set of global element (or
> attribute) declarations capable of matching the wildcard must be the same.
> </add> 

I think this rule changes behavior, and would be incompatible with XQuery 1.0.

Suppose module A imports schema A, and module B imports no schema at all.
Validation will work differently in the two modules.

It's important to allow different modules to use different sets of schemas.
This has been possible since XQuery 1.0, and it's very useful when querying
mixed sets of documents.

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 Friday, 30 September 2011 13:14:18 UTC

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