- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 07 Jan 2009 17:03:27 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6382 Summary: Substitution group and "block" Product: XML Schema Version: 1.1 only Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Structures: XSD Part 1 AssignedTo: cmsmcq@w3.org ReportedBy: sandygao@ca.ibm.com QAContact: www-xml-schema-comments@w3.org See the following email thread on the xmlschema-dev list: http://lists.w3.org/Archives/Public/xmlschema-dev/2009Jan/0009.html Is the following schema snippet valid? <xsd:element name="Head" type="Type"/> <xsd:complexType name="Type" block="restriction"/> <xsd:complexType name="derivedFromType"> <xsd:complexContent> <xsd:restriction base="Type"/> </xsd:complexContent> </xsd:complexType> <xsd:element name="Member1" type="derivedFromType" substitutionGroup="Head"/> We require that the sub-group member's type be derived from that of the head, but the actual requirement seems to have changed between 1.0 and 1.1. In 1.0, bullet 4 of "Element Declaration Properties Correct" refers to "Type Derivation OK (Complex) (§3.4.6)". Neither constraint mentions the {prohibited substitutions} property of the base type. So in 1.0, the above is valid. But in 1.1, bullet 4 refers to the definition of "validly substitutable", which takes {prohibited substitutions} of the base type into account. So in 1.1, the above becomes invalid, because the derivation is blocked by "type". Did we intend this change of behavior? -- 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 Wednesday, 7 January 2009 17:03:35 UTC