Hi,
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.)
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--