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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 09 Aug 2011 11:47:32 +0000
To: public-qt-comments@w3.org
Message-Id: <E1QqkmS-0007UZ-Kw@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13674

--- Comment #4 from Oliver Hallam <oliver@cbcl.co.uk> 2011-08-09 11:47:30 UTC ---
I didn't find the meaning of the spec to be as clear as you suggested.
Section 2.1.1 defines the substitution groups as a component of the In-scope
schema definitions, which quite specifically vary from module to module, which
lead to my original interpretation.

4.12 makes it clear that the schema definitions are not imported from another
module, and hence the substitution groups vary from module to module.


In the end I have gone in the direction of weakening some type checking rules
when running with optimistic typing, to assume that you know nothing statically
about the name of a schema-element match, and not to make any inferences about
the child axis on a known schema type.

Without having full control over the schemas we have had to go for the even
more draconian approach of disallowing dynamic schemas entirely if the query is
compiled in static-typing mode.

-- 
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, 9 August 2011 11:47:33 UTC

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