[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: top level params and xsl:attribute magic?
"S Woodside" <sbwoodside@xxxxxxxxx> wrote in message news:7FCB3007-2B28-11D7-8385-000393414368@xxxxxxxxxxxx > Thanks, 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. > This is not so at all, the (count(ancestor::node()), count(preceding::node()) ) uid will still identify the same node if the changes in the xml document were made in the descendants or following nodes of this node. This is 50% probability that after a single change the uid will still identify the same node. 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. ===== Cheers, Dimitre Novatchev. http://fxsl.sourceforge.net/ -- the home of FXSL __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|