- From: David Carlisle <davidc@nag.co.uk>
- Date: Wed, 24 Mar 2004 15:36:17 GMT
- To: dnovatchev@yahoo.com
- Cc: mhk@mhk.me.uk, public-qt-comments@w3.org
Michael Kay
> We need to decide whether to make the same change to XSLT's key()
> function.
Dimitre Novatchev
> This would be very nice! Having to use more than one key on different
> documents leads to sprinkling of lots of artificial xsl:for-each
I agree with Dimitre that xsl:key and xsl:id should have the same
argument forms but I do question why this is needed (for id() or key())
It is true that the XSLT1 for-each hack was horrible but given that the
XPath2 versions allow id() to be used within a path expression and
index the document current at that point, what is gained by the new
syntax. Isn't id("a",$somedocumentnode) the same as $somedocumentnode/id("a")
in the case when $somedocumentnode is a single document node (and
perhaps also when it is not?)
David
--
http://www.dcarlisle.demon.co.uk/matthew
________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
Received on Wednesday, 24 March 2004 16:19:38 UTC