This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As part of the resolution for defect http://www.w3.org/Bugs/Public/show_bug.cgi?id=4775, the processContents for the smlif:dataType has been changed from lax to skip. Since this change had some not so obvious reasons, I propose to have the spec explain this approach. Proposal : Add this comment to the sml-if.xsd schema, under the dataType type <xs:complexType name="dataType" mixed="false"> <xs:annotation> <xs:documentation> The wildcard with processContents "skip" matches the root element of the model document being packaged. The value of processContents is set to "skip" so that the contained element is not attempted for schema validation. As a result, validity of the packaged document will not affect validity of the IF document itself. </xs:documentation> </xs:annotation> <xs:sequence> <xs:any processContents="skip" minOccurs="0"/> </xs:sequence> </xs:complexType>
Fix per proposal.
The new schema reads as follows: -------- <xs:complexType name="dataType" mixed="false"> <xs:annotation> <xs:documentation> The wildcard with processContents "skip" matches the root element of the model document being packaged. The value of processContents is set to "skip" so that the contained element is not processed for schema validation. As a result, validity of the packaged document will not affect validity of the IF document itself. </xs:documentation> </xs:annotation> <xs:sequence> <xs:any processContents="skip" minOccurs="0" namespace="##any" maxOccurs="1"/> </xs:sequence> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> -------- Note the phrase "the contained element is not **processed** for schema validation". This is a change from the proposal.
I agree with the change in comment# 2.
I also agree with changes in comment #2.
+1 for change described in comment #2
+1 for change described in comment #2.