This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6161 - 3.10.6.2 Wildcard Subset
Summary: 3.10.6.2 Wildcard Subset
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: editorial, resolved
Depends on:
Blocks:
 
Reported: 2008-10-15 12:21 UTC by Michael Kay
Modified: 2009-03-16 14:33 UTC (History)
1 user (show)

See Also:


Attachments

Description Michael Kay 2008-10-15 12:21:23 UTC
I'm struggling to understand the structure of this contraint. 

It starts with a definition

"sub is a wildcard subset of super  if and only if  one of the following is true..."

and then continues:

"And all of the following must be true..."

Is this part of the definition? (if so, why "must"?)

I would expect the structure here to be

... all of the following are true:

1 One of the following is true:
  1.1
  1.2
  1.3
  1.4
2 Each QName member of super.{disallowed names} is not allowed by sub..
3 If super.{disallowed names} contains defined, then...
4 If super.{disallowed names} contains sibling, then...

(Note also the use of apostrophe rather than dot in the last clause)
Comment 1 David Ezell 2008-10-17 16:14:30 UTC
The WG decided that the editors need to make sure that ands and ors are unambiguous, and that "must" should be changed to "are".
Comment 2 Sandy Gao 2009-03-16 14:23:54 UTC
During its 2009-03-13 telecon, the schema WG adopted a proposal to address this issue.

The proposal can be found at (member-only):
  http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.omni.20090313.html

This implements the WG decision recorded in comment #1, by changing "must" to "are".

Another change made (not shown in the above proposal) was to replace clause 3 "... super's {disallowed names} ..." with "... super.{disallowed names} ...", as suggested in the bug report.

With these changes, the WG believes that the issue raised in this bug report is fully addressed. I'm marking this RESOLVED accordingly.

Michael, as the persons who opened and reopened this issue, if you would indicate your concurrence with or dissent from the WG's disposition of the comment by closing or reopening the issue, we'll be grateful. If we don't hear from you in the next two weeks, we'll assume that silence implies consent.