Re: [xsl] Is it legal to do <xsl:copy-of select="element/@attribute"/>?

[Dimitre Novatchev <dnovatchev@xxxxxxxxx>]

> Can I rely on the rule for <xsl:attribute/>
> being applied that says, when adding an attribute, any already
> existing attribute of the same name is replaced?

Yes, the XSLT 1.0 specification
(http://www.w3.org/TR/1999/REC-xslt-19991116#creating-attributes)  is
precize about this:

"Adding an attribute to an element replaces any existing attribute of
that element with the same expanded-name"



--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play
-------------------------------------
Facts do not cease to exist because they are ignored.



On Tue, Feb 8, 2011 at 3:59 PM, TW <zupftom@xxxxxxxxxxxxxx> wrote:
> Is it legal to copy attributes that are collected from a bunch of
> different elements into a result element using
> B <xsl:copy-of select="element/@attribute"/>?
>
> It works in the processors I've tested, but as the same attribute may
> occur several times in the selected node set, but can only be present
> once in the output, I'm not sure whether it's O.K. to do something
> like this (in XSLT 1.0). B Can I rely on the rule for <xsl:attribute/>
> being applied that says, when adding an attribute, any already
> existing attribute of the same name is replaced?  Or is the processor
> behavior implementation-dependent in such a situation?
>
> Thanks!
> Thomas W.