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





From george@s... Mon Sep 12 13:22:49 2005
Received: from maggie.w3.org ([193.51.208.68])
	by frink.w3.o