Subject: Re: [xsl] Re: xsl-list Digest 22 Jun 2005 05:10:01 -0000 Issue 455 From: David Carlisle <davidc@xxxxxxxxx> Date: Wed, 22 Jun 2005 21:37:21 +0100 |
> That there's no current node while processing a scalar value, I > understand, but why can't there be a current document? because current document means essentially the document node that you get by executing ancestor::node()[last()] instance document() and if the current item is a scalar value you can't execute that. Nodes have identity and live in a document. values are just values. (YOu could imagine a system in which "current document" was a separate item in the context that was maintained (or changed) independently of the "current item", but that's not the way it works. David ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. 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 ________________________________________________________________________
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Re: xsl-list Digest 22 Jun 20, Michel Charpentier | Thread | RE: [xsl] Re: xsl-list Digest 22 Ju, Michael Kay |
[xsl] Re: xsl-list Digest 22 Jun 20, Michel Charpentier | Date | [xsl] xsl:element in XSLT 1.0, Jack Matheson |
Month |