- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 11 Feb 2006 01:42:55 +0000
- To: www-xml-schema-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2857
Summary: RQ-7 Improve interaction between wildcards and
substitution groups (wildcards)
Product: XML Schema
Version: 1.1 only
Platform: Other
OS/Version: All
Status: NEW
Keywords: needsDrafting
Severity: normal
Priority: P2
Component: Structures: XSD Part 1
AssignedTo: ht@w3.org
ReportedBy: cmsmcq@w3.org
QAContact: www-xml-schema-comments@w3.org
This issue was originally reported by Matthew Fuchs.
Address problems with the interaction between wildcards and
substitution groups.
Specifically, resolve the bug where if complex type A has a wildcard,
and B restricts A, then it can restrict the wildcard to a set of
elements that match the wildcard. Not all elements in the substitution
groups of those elements necessarily match the wildcard - so B is not
a subset of A.
See (member-only link) http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2001Apr/0047.html,
http://www.w3.org/2000/12/xmlschema-crcomments.html#x6 (http://www.w3.org/2000/12/xmlschema-crcomments.html#x6).
Cf. RQ-135 (#component-consistency-and-validity).
This item was discussed, and phase-1 agreement was reached, in the
meeting of 2004-03-18
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Mar/0060.html).
All we need to say to discharge this requirement is that
restriction is transitive. The types derived by multiple
restriction steps should also obey the wildcard. There was some
doubt over whether the constructive rules of XML Schema 1.0
achieve this, but the definition of restriction in section 2 seems
to entail it.
According to the requirements document, phase-1 agreement has been reached.
Received on Saturday, 11 February 2006 01:43:00 UTC