I haven't got it.
when considering // it's important to distinguish select expressions
(which use Xpath) to Match patterns (which use an XSLT-specific
construct that looks a lot like a subset of Xpath, but is actually
separately defined). Actually it's important to disinguish these all the
time but usually people find // is the first problem case...
select="foo"
just selects the foo children of teh current node, and
select="//foo"
selects all the foo elements in the document.
however
match="zzzz"
matches the current node if there is any node anywhere in the tree such
that the Xpath zzzz evealuated at this other node would select a node
set that includes the current node.
so
match="foo"
matches any foo element anywhere as evaluating select="foo" on the
parent of that node would select the foo node.
similarly
match="//foo" also matches any element as evaluatinng that on an
ancestor of the current element will select the current element.
Note // is not always redundant in match patters, just redundant at the
beginning.
match="a//b" matches all b elements that have a as an ancestor, as
select="a//b" evaluated on the parent of a would select those b
elements.
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
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--