This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This change from https://www.w3.org/Bugs/Public/show_bug.cgi?id=22747#c3: > Detailed proposal > > 1. Change the definition of "attribute set" in 10.2 from > > [Definition: The xsl:attribute-set element defines a named attribute set: > that is, a collection of attribute definitions that can be used repeatedly > on different constructed elements.] > > to (text modelled closely on xsl:key): > > Attribute sets provide named collections of attributes that can be used > repeatedly on different elements. IMO glosses over the evaluation of the xsl:attribute instruction(s) for each element. E.g., this xsl:attribute-set: <xsl:attribute-set name="fig"> <xsl:attribute name="id" select="generate-id()" /> </xsl:attribute-set> creates a different (in the sense of deep-equal()) attribute each time it's used, so it's not the same attribute being used repeatedly. While the third paragraph does mention xsl:attribute instructions, the initial paragraph can give the wrong impression if you're just skimming the text.
I have made a further editorial change from Attribute sets provide named collections of attributes that can be used > repeatedly on different elements. to Attribute sets generate named collections of attributes that can be used > repeatedly on different elements. I hope this is sufficient to introduce early on the idea that an attribute set is something actively evaluated rather than merely passive data. I'm marking this resolved; please close it if you agree, or reopen otherwise.