Hi,
The problem below is interesting. A few of us were discussing this, and
we're not sure what the spec intended. There are some interesting
variations such as :
- the anonymous type for the attribute in the base is the same as the
anonymous type for the attribute in the restriction, except that
ordering of enumeration values is different.
- the anonymous type for the attribute in the base is the same as the
anonymous type for the attribute in the restriction, except that the
facets are ordered differently.
- etc.
It's not clear what it means for 2 anonymous types to "be the same".
I'll post something to get a clarification from the Schema WG.
Lisa.
--------------------------------------------------------------------------------
Xerces generates a different error but because of the use of the following
attribute group within both base and derived type:
<xsd:attributeGroup name="ItemDelivery">
<xsd:attribute name="partNum" type="SKU"/>
<xsd:attribute name="weightKg" type="xsd:decimal"/>
<xsd:attribute name="shipBy" >
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="air"/>
<xsd:enumeration value="sea"/>
<xsd:enumeration value="any"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:attributeGroup>
In this case the error is:
"ComplexType 'ConfirmedItems': derivation-ok-restriction.2.1.2: Type of
attribute 'shipBy' in derivation must be a restriction of type of attribute
in base."
Again, I find it difficult to see any problem with this restriction unless
it has to do with the localness of the simple type on that attribute.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
