- From: Kasimier Buchcik <kbuchcik@4commerce.de>
- Date: Fri, 09 Sep 2005 10:20:20 +0200
- To: XML-SCHEMA <xmlschema-dev@w3.org>
Hi, Due to a funky new security mechanism of the W3C mailing list, my last message did not reach the list. I got: "...Your message has NOT been distributed to the list; before we distribute it, we need your permission to include your message in our Web archive of all messages distributed to this list..." After following the process to permit everything needed, I read that the message will be transmitted, but I don't see it transmitted, so I try to repost it. Sorry if the original message pops up from somewhere in the undefined future. 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 08:25:49 UTC