Subject: Re: [xsl] top level params and xsl:attribute magic? From: S Woodside <sbwoodside@xxxxxxxxx> Date: Tue, 21 Jan 2003 23:36:04 -0500 |
<snip/>"S Woodside" <sbwoodside@xxxxxxxxx> wrote in message news:7FCB3007-2B28-11D7-8385-000393414368@xxxxxxxxxxxxThanks, I considered this, but I think that passing the full XPath makes debugging easier and will be more robust if I change the source XML (it has a chance of still working, instead of being guaranteed not to work.)
As for easier debugging when using XPath expressions, this is right, but only in the case we know well the source xml document. In case the transformation is designed to be generic and process *any* source xml document, then in the general case when the structure of the source xml is not known to the programmer, using XPath expressions is exactly as helpful as using another uid system.
The big advantage of the coordinate uid method is the fact that nodes can be located very fast by using a key. Future XSLT processors could be optimised to automatically maintain the coordinate uid of every node, so that a programmer would not even have to declare an xsl:key for node() on its coordinates.
simon --- www.simonwoodside.com
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] top level params and xsl:, Wendell Piez | Thread | Re: [xsl] top level params and xsl:, Dimitre Novatchev |
Re: [xsl] top level params and xsl:, S Woodside | Date | Re: [xsl] xpath confusion (compound, S Woodside |
Month |