Why does // expand to descendant-or-self::node() rather than to
descendant::x where x is the next item in the path?
It seems like because of the implicit child:: axis, // had to expand
to descendant-or-self, even though it doesn't make sense to include
the self axis... In other words, the self axis is only included
because of the implicit child axis - if that wasn't there, it wouldn't
be needed.
For example:
/foo//bar/baz
Why is the // is a step in its own right, rather than "//bar" being a
single step - why can't the above expand to:
/child::foo/descendant::bar/child::baz
This in fact select "foo", then something with descendant "bar", with child
"baz",
and misses "foo", with child "bar", with child "baz".
--
Vladimir Nesterovsky
http://www.nesterovsky-bros.com
--~------------------------------------------------------------------
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>
--~--