Re: [xsl] Some more stuff about selecting unique elements

Subject: Re: [xsl] Some more stuff about selecting unique elements
From: David Carlisle <davidc@xxxxxxxxx>
Date: Tue, 10 Apr 2001 13:51:08 +0100

shouldn't you be using preceding-sibling rather than using preceding
and then checking on the id of the parent?

Also <xsl:copy is usually safer than   <xsl:element name="{name()}">
and .//stuff would apparently be better as stuff (unless  your documents
are more complicated than shown.)

> Well, the problem i dislike the preceding axis is performance, 
well yes, but preceding-sibling would be more fun, and in either case
you could probably optimise using xsl:key if needed.

> What optimisations do XSL processors (read: Saxon) while processing this
> XSL?
In his talk at the weekend MK suggested that authors write their
stylesheets assuming no optimisation is done (even though they do do

> I suppose in XSLT 1.1 (2.0) where RTFs are gone 
I'll let Jeni tell you about that....

All (?) existing systems let you query into a RTF using an explicit
coersion to a node set (xt saxon. msxsl, xalan etc all have a node-set()
function in theor extension namespace)


This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit

 XSL-List info and archive:

Current Thread