- From: Kasimier Buchcik <kbuchcik@4commerce.de>
- Date: Mon, 12 Sep 2005 15:05:12 +0200
- To: kbuchcik@4commerce.de
- Cc: XML-SCHEMA <xmlschema-dev@w3.org>
Hi,
XSV 2.10 seems to have problems here as well:
attr-2.xsd
----------
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:test:foo"
xmlns:f="urn:test:foo">
<xsd:complexType name="base">
<xsd:attribute name="boo" use="optional"/>
</xsd:complexType>
<xsd:complexType name="type-1">
<xsd:complexContent>
<xsd:restriction base="f:base">
<xsd:attribute name="boo" use="prohibited"/>
<xsd:attribute name="boo"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="type-2">
<xsd:attribute name="boo" use="prohibited"/>
<xsd:attribute name="boo"/>
</xsd:complexType>
<xsd:element name="foo" type="f:type-1"/>
</xsd:schema>
attr-2.xml
----------
<foo xmlns="urn:test:foo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:test:foo attr-2.xsd"
boo="lala"/>
XSV:
attr.xml:1,22: undeclared attribute {None}:boo
If we change the type of the element declaration to "f:type-2",
then XSV reports no errors.
This is inconsistent, as one would expect the attribute uses
of "f:type-1" and "f:type-2" to be equal.
Thoughts?
Regards,
Kasimier
Received on Monday, 12 September 2005 13:07:26 UTC