W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2010

[Bug 11092] New: Error in S4SD: complexType name="all" is not a valid restriction

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 Oct 2010 13:30:36 +0000
To: www-xml-schema-comments@w3.org
Message-ID: <bug-11092-703@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11092

           Summary: Error in S4SD: complexType name="all" is not a valid
                    restriction
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: David_E3@VERIFONE.com
        ReportedBy: mike@saxonica.com
         QAContact: www-xml-schema-comments@w3.org
                CC: cmsmcq@blackmesatech.com


I'm getting the following error compiling the S4SD:

Error on line 906 of s4s11-2010-10-18.xsd:
  The content model of the complex type "all" is not a valid restriction of the
content model of the type "explicitGroup". Definition of element "group"
differs between the restricted type and the base type. Type of element in
restricted content model is not derived by restriction from the type of the
corresponding element in base content model.

In complexType name="all", the particle for element name="group" is defined
within group name="allModel" like this:

        <xs:element name="group">
          <xs:complexType>
            <xs:sequence>
              <xs:element ref="xs:annotation" minOccurs="0"/>
            </xs:sequence>
            <xs:attribute name="ref" type="xs:QName" use="required"/>
            <xs:attribute name="minOccurs" fixed="1"
type="xs:nonNegativeInteger"/>
            <xs:attribute name="maxOccurs" fixed="1"
type="xs:nonNegativeInteger"/>
            <xs:anyAttribute namespace="##other" processContents="lax"/>
          </xs:complexType>
        </xs:element>

wherease the base type (name="explicitGroup") defines it within group
name="particle" like this:

<xs:element name="group" type="xs:groupRef"/>

This problem seems to have been introduced when we made the change to allow
group references within xs:all.

-- 
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 Tuesday, 19 October 2010 13:30:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 October 2010 13:30:48 GMT