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: Thu, 29 Sep 2011 22:46:32 +0000
To: public-qt-comments@w3.org
Message-Id: <E1R9PNA-00023B-9d@jessica.w3.org>

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
             Status|CLOSED                      |REOPENED
         Resolution|WORKSFORME                  |

--- Comment #7 from Michael Kay <mike@saxonica.com> 2011-09-29 22:46:30 UTC ---
Reopening because I don't think the issue has been adequately addressed.

Arguably, the statements on consistency in 2.2.5 already cover the issue. But
they gloss over some of the difficulties, and fail to draw attention to some
significant pitfalls.

I propose adding to the penultimate bullet of 2.2.5 Consistency Constraints
(which starts "For a given query, define a participating ISSD ...") the

"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.

Michael Kay

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 Thursday, 29 September 2011 22:46:34 UTC

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