Subject: Re: [xsl] Locating an attribute and its value indirectly|
From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 07 Nov 2011 13:12:21 -0500
On 11/7/2011 12:32 PM, Michael Kay wrote:On 11/4/2011 9:27 PM, G. Ken Holman wrote:The current() function returns that node that was current at the beginning of the evaluation of the XPath expression.
I'm sure Ken won't mind if I add a little color commentary. It may help to keep in mind that the "context node" is an XPath concept, while the "current node" is an XSLT concept.
That's the way the 1.0 specifications described it. In 2.0 both specs speak of the context item, and the current() function, rather inelegantly, is defined as returning "the item that was the context item at the point where the [XPath] expression was invoked from the XSLT stylesheet. "
I suppose that's understandable, inasmuch as XSLT 2.0 in general is being pulled in the direction of a generalized data processing language and not just a tree transformation language. (What with xsl:for-each no longer selecting -- or, some day, template rules no longer matching -- only nodes.)
Yet I dare say it may help to keep a rough distinction in mind in any case.
So does this also mean the concepts of "current node list" etc. go by the boards? (Now going to look and see.)
The description of the evaluation context has been changed. The concepts of current node and current node list have been replaced by the XPath concepts of context item, context position, and context size.
-- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/t37DVX Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal