7352 2009-08-17 16:37:30 +0000 Default value of "nillable" on (local) element declarations in SD4SD 2009-10-02 15:34:44 +0000 1 1 1 Unclassified XML Schema Structures: XSD Part 1 1.1 only All All CLOSED FIXED resolved P2 normal --- 1 sandygao David_E3 cmsmcq www-xml-schema-comments oldest_to_newest 26489 0 sandygao 2009-08-17 16:37:30 +0000 The default value for "nillable" in the schema for schemas can turn good schema documents into bad ones. Consider: <xs:schema ...> <xs:element name="global" .../> <xs:complexType ...> <xs:sequence> <xs:element ref="tns:global"/> After validating against the SD4SD, a default value for "nillable" is added to the element reference: <xs:element maxOccurs="1" minOccurs="1" nillable="false" ref="tns:global"/> But "nillable" isn't allowed on element refs [1]. It seems that we do not depend on the default value of "nillable" in the mapping rules. Section 3.3.2 has: "{nillable} The ·actual value· of the nillable [attribute], if present, otherwise false." Suggest to remove such default value from the SD4SD, in both 1.0 and 1.1. [1] http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#src-element clause 2.2 27079 1 cmsmcq 2009-09-11 16:27:38 +0000 The WG today accepted this analysis and instructed the editors to fix it. 27292 2 sandygao 2009-09-18 13:04:41 +0000 Concrete proposal. In Appendix A, remove the default value on the attribute declaration for "nillable" from the complex type definition "element". i.e. remove default="false" from the following: <xs:complexType name="element" abstract="true"> <xs:annotation> ... </xs:annotation> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:sequence> ... </xs:sequence> ... <xs:attribute name="nillable" type="xs:boolean" default="false" use="optional"/> ... </xs:extension> </xs:complexContent> </xs:complexType> 27298 3 sandygao 2009-09-18 15:32:20 +0000 WG accepted proposal in comment #2 on 2009-09-18.