B
Bob Foster
One of the XSD test cases, elemQ016, contains the following:
<xsd:element name="fooTest" nillable="true" fixed="Hello">
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
Xerces does not flag the combination of nillable="true" and fixed as an
error, and indeed it doesn't seem to be. But according to my reading of
3.3.4/3.2.2 an instance like:
<fooTest nil="true"/>
would be invalid because the element has a fixed value.
This seems very odd. Am I reading this right? If this is so, why wasn't the
combination disallowed in the schema?
Thanks.
Bob Foster
<xsd:element name="fooTest" nillable="true" fixed="Hello">
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
Xerces does not flag the combination of nillable="true" and fixed as an
error, and indeed it doesn't seem to be. But according to my reading of
3.3.4/3.2.2 an instance like:
<fooTest nil="true"/>
would be invalid because the element has a fixed value.
This seems very odd. Am I reading this right? If this is so, why wasn't the
combination disallowed in the schema?
Thanks.
Bob Foster