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: Sat, 10 Sep 2011 16:13:50 +0000
To: public-qt-comments@w3.org
Message-Id: <E1R2QBi-0004zs-Gq@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13674

--- Comment #5 from Jonathan Robie <jonathan.robie@gmail.com> 2011-09-10 16:13:48 UTC ---
(In reply to comment #3)

> <quote>
> schema-element(E) matches an element if (inter alia) "The name of the candidate
> node matches ... the name of an element in a substitution group headed by an
> element named ElementName." - it doesn't say that the element name has to be
> declared in an imported schema or that the element declaration has to be "in
> scope" (whatever that might mean).
> </quote>

The spec also says this:

2.5.5 SequenceType Matching

An XQuery 3.0 implementation must be able to determine relationships among the
types in type annotations in an XDM instance and the types in the in-scope
schema definitions (ISSD). An XQuery 3.0 implementation must be able to
determine relationships among the types in ISSDs used in different modules of
the same query.

Together with what Mike quoted, I think that makes the spec clear here. Am I
missing something? Is there a bug that we need to fix in the spec?

-- 
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 Saturday, 10 September 2011 16:13:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:15 GMT