This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
If a schema declares a default attribute with a qualfied name (a:b="some value"), it appears that the PSVI does not fixup the [in-scope namespaces] and [namespace attributes] properties. It is therefore possible for these attributes to get out of sync. See http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2002Jan/0090.html
The WG discussed this at the 01/25 telecon: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Jan/0084.html Related issues are: - CR-41: Should Structures specify how / where to generate a prefix and a namespace declaration for the namespace of an attribute with a qualified name for which the schema processor must supply a default? - The Infoset that results from schema assessment may contain Attribute Information Items that do not have a [normalized value] property and as such, the Infoset that results from schema assessment cannot generally be the subject of schema assessment itself. See: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002JanMar/0280.html The WG decided that these issues should be considered Future Requirements, and be reopened for 1.1