- From: Kasimier Buchcik <K.Buchcik@4commerce.de>
- Date: Thu, 8 Sep 2005 15:23:28 +0200
- To: "XML-SCHEMA" <xmlschema-dev@w3.org>
- Message-ID: <1126185808.1290.38.camel@librax>
Hi, Potential bug in XSV and MSXML related to builing the processContents of complete attribute wildcards. <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:attributeGroup name="attrGroup"> <xs:anyAttribute namespace="##any"/> </xs:attributeGroup> <xs:element name="foo"> <xs:complexType> <xs:attributeGroup ref="attrGroup"/> <xs:anyAttribute namespace="##any" processContents="lax"/> </xs:complexType> </xs:element> </xs:schema> <foo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="attr-wild.xsd" xmlns:b="urn:test:bar" b:bar="BAR" /> XSV 2.10 and MSXML 4.0 are not happy with this scenario, while Xerces-J 2.7.1 is. XSV and MSXML become happy if and only if _both_ attribute wildcards are set to a processContents of "lax". I think only Xerces is working correct here. In [1] we have: "2.2.1 If there is an <anyAttribute> present, then a wildcard whose {process contents} and {annotation} are those of the ·local wildcard·, and whose {namespace constraint} is..." [1] http://www.w3.org/TR/xmlschema-1/#Complex_Type_Definition_details Regards, Kasimier
Received on Friday, 9 September 2005 09:07:49 UTC