W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > July to September 2007

[Bug 5053] S4S: Issues on the complex type definition "altType"

From: <bugzilla@wiggum.w3.org>
Date: Sat, 15 Sep 2007 11:54:52 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1IWWEe-0000wI-2i@wiggum.w3.org>


           Summary: S4S: Issues on the complex type definition "altType"
           Product: XML Schema
           Version: 1.1 only
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: cmsmcq@w3.org
        ReportedBy: pmarinel@cs.unibo.it
         QAContact: www-xml-schema-comments@w3.org

Within the Schema for Schema documents [1], type “altType” is defined as

<xs:complexType name="altType">
      <xs:extension base="xs:annotated">
        <xs:choice minOccurs="0">
          <xs:element ref="xs:simpleType"/>
          <xs:element ref="xs:complexType"/>
        <xs:attribute name="test" type="string" use="optional"/>
        <xs:attribute name="type" type="QName" use="optional"/>
        <xs:attribute name="xpathDefaultNamespace"
        <xs:attribute name="id" type="xs:ID"/>

The content model references the global element declarations “simpleType” and
“complexType”. Such global declarations are used to validate the simple and
complex types defined at the top-level of a schema document. So, both of them
requires the attribute “name”. On the other hand, I think that unnamed type
definitions only should be allowed within an <alternative> element. 

Moreover, type “altType” explicitly declares an attribute “id” of type “ID”.
But such an attribute is also inherited from the base type “annotated”. 

See also bug 5052.

Received on Saturday, 15 September 2007 11:55:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:06 UTC