This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
complex004.n2.xml Spec says instance should be valid, since it matches the declared type, and xsi:type defaults should not be honored.
I would like further discussion of this. 3.2.6.4 says: Note: It is legal for Attribute Uses that refer to xsi: attributes to specify default or fixed value constraints (e.g. in a component corresponding to a schema document construct of the form <xs:attribute ref="xsi:type" default="xs:integer"/>), but the practice is not recommended; including such attribute uses will tend to mislead readers of the schema document, because the attribute uses would have no effect; see Element Locally Valid (Complex Type) (
Both Element Locally Valid (Complex Type) (
(In reply to comment #2) > Both Element Locally Valid (Complex Type) (
Expected result of complex004.n2.xml has been changed to "valid".