This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Collecting attributes from the ancestor-or-self axis
- From: Oleg Tkachenko <olegt at multiconn dot com>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Mon, 19 Nov 2001 14:04:08 +0200
- Subject: Re: [xsl] Collecting attributes from the ancestor-or-self axis
- Organization: Multiconn International
- References: <72FAAE98015DD511B42600D0B747AC7FC1224F@kipling.br.itc.hp.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
WATKIN-JONES,ADAM (HP-UnitedKingdom,ex1) wrote:
> I believe this works as follows:
> 1. the select in copy-of returns a node-set in document order. At this
> point the node set has duplicate attribute names.
I don't think that's right. By definition node-set is "an unordered
collection of nodes without duplicates". So all dublicates have to be
removed at the time of XPath expresison evaluating and the order may be
any one appropriate to XPath processor.
> 2. when copy-of applies these attributes to the output element, the
> duplication is removed by succeeding attribute nodes overwriting the values
> of any attributes that are already present.
<xsl:copy-of> copies nodes in document order, but if you are copying
attributes, why do you care about any order?
--
Oleg Tkachenko
Multiconn International, Israel
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list