6170 2008-10-17 09:03:22 +0000 Wildcards and defaultAttributes 2008-10-24 17:26:29 +0000 1 1 1 Unclassified XML Schema Structures: XSD Part 1 1.1 only PC Windows NT RESOLVED FIXED resolved P2 normal --- 1 mike cmsmcq www-xml-schema-comments oldest_to_newest 22190 0 mike 2008-10-17 09:03:22 +0000 In 3.4.2.4, XML Mapping summary, property {attribute uses}, it is stated <quote> If the <schema> ancestor has a defaultAttributes attribute, and the <complexType> element does not have defaultAttributesApply = false, then the properties {attribute uses} and {attribute wildcard} are computed as if there were an <attributeGroup> [child] with empty content and a ref [attribute] whose ·actual value· is the same as that of the defaultAttributes [attribute]. </quote> For completeness, it needs to say whether this hypothetical <attributeGroup> child is at the start or the end. This is because when multiple attribute groups are combined, and more than one of them has an attribute wildcard, the effective processContents is taken from the first. (This is a horrible rule, but it's the only one we've got. I've argued in WG email (see http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2008Oct/0009.html - member-only) that at least for defaultAttributes the result should be the union rather than the intersection, and by analogy with derivation by extension, the processContents would then be that of the extended type rather than the base type.). 22191 1 mike 2008-10-17 10:02:01 +0000 Another problem with this text is that it appears in the mapping rule for the {attribute uses} property; it needs to appear again, or be referenced, in the mapping rule for the {attribute wildcard} property. 22198 2 sandygao 2008-10-17 16:53:45 +0000 My intuition is the "end", to allow local rules to override the default. The issue raised in [1] probably warrants an entry in Bugzilla so that we don't lose track of it. [1] http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2008Oct/0009.html 22251 3 sandygao 2008-10-24 17:26:29 +0000 On 2008-10-24, the working group adopted a proposal to address this issue by - Specifying that defaulted attribute group appears after the explicitly referenced attribute groups - Repeating rules around applying default attributes in "3.4.2.5 Mapping Rule for Attribute Wildcard Property" The proposal (along with changes for other bugs) can be found at (member-only): http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.omni0810.html