Re: [xsl] General rule for designing XPath expressions to return items in document order?

Subject: Re: [xsl] General rule for designing XPath expressions to return items in document order?
From: davep <davep@xxxxxxxxxxxxx>
Date: Fri, 10 Jan 2014 14:10:50 +0000
On Fri, 10 Jan 2014 12:48:57 +0000
David Carlisle <davidc@xxxxxxxxx> wrote:

> On 10/01/2014 12:01, Michael Kay wrote:
> > b) Unlike //head, //text() is "striding" - the nodes it selects are
> > non-overlapping (because text nodes never overlap). So absorption
> > operations like data(), string(), and <xsl:value-of> are allowed.
> 
> 
> This is all going to keep this list active for ever:-)
> 
> It remains to be seen I think how far just having a naive mental model
> of the kind of things that ought to work in a streaming context will
> lead to expressions that are in fact defined to be streaming in the
> spec (or are streaming in the implementations). It's an impressive
> bit of analysis/specification in any case, I love the terminology:-)


I don't David! I do hope it is glossed well - 
absorbtion operation
vb striding!

I dread to think what else is coming from 3.0!

regards 

Current Thread