OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [emergency] Fwd: [emergency-comment] CAP Normative Schema isimproperly defined


I asked the folk over on XML-DEV about the simpleType issue since I
was having real trouble remembering where in the XML Schema
documentation this issue is addressed. The answer is that the
normative XML Schema of Schemas clearly prohibits the use of the name
attribute on a local simpleType. Michael Kay and Jeff Rafter both
pointed to the appropriate section of the normative schema:

<xs:complexType name="localSimpleType">
    <xs:complexContent>
      <xs:restriction base="xs:simpleType">
        <xs:sequence>
          <xs:element ref="xs:annotation" minOccurs="0"/>
          <xs:group ref="xs:simpleDerivation"/>
        </xs:sequence>
        <xs:attribute name="name" use="prohibited">

Also, Dare Obasanjo of Microsoft provided the following:
According to
http://www.w3.org/TR/2004/PER-xmlschema-1-20040318/#cvc-elt
"<element>s within <schema> produce global element declarations;
<element>s within <group> or <complexType> produce either particles
which contain global element declarations (if there's a ref attribute)
or local declarations (otherwise). For complete declarations,
top-level or local, the type attribute is used when the declaration
can use a built-in or pre-declared type definition. Otherwise an
anonymous <simpleType> or <complexType> is provided inline."
The last sentence is the relevant one."

Thus, it would appear that the schema is invalid -- even if some tools
are being reported to accept the schema as written. The fact that some
tools accept the CAP V1.0 schema should be considered a bug in those
tools.

		bob wyman



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]