Subject: RE: [xsl] // expanding to descendant-or-self::node() From: "Michael Kay" <mike@xxxxxxxxxxxx> Date: Tue, 16 Sep 2008 16:19:28 +0100 |
> Why does // expand to descendant-or-self::node() rather than > to descendant::x where x is the next item in the path? I've always imagined it was primarily to make //@x work; though I'm not at all convinced it was a smart decision. Certainly in practice it's very rare to see any axis other than "child" after "//" (for example //.., or //following-sibling::x is never seen in practice and never required; and //@x is something one could live without). I think making "//" expand to "/descendant::" might well have been a better design. Michael Kay http://www.saxonica.com/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] // expanding to descendan, Florent Georges | Thread | Re: [xsl] // expanding to descendan, Andrew Welch |
Re: [xsl] Fwd: text nodes, XSL-List Owner | Date | [xsl] Distinct values with XPath qu, Matthew Hailstone |
Month |