W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > June 2007

Re: position() after match in component

From: Richard Tobin <richard@inf.ed.ac.uk>
Date: Thu, 7 Jun 2007 15:51:29 +0100 (BST)
To: Norman Walsh <ndw@nwalsh.com>, public-xml-processing-model-wg@w3.org
Message-Id: <20070607145129.DE86E219311@macpro.inf.ed.ac.uk>

> However, we want to be able to stream many of our microsteps. On that
> basis, I'd be in favor of saying that the context position and context
> size are both 1 when the replace expression is evaluated in
> p:string-replace (and in analagous situations on other steps).

Unless the replace expression is prohibited from accesssing arbitrary
nodes, I don't see much advantage to this.  You have to analyse the
expression to see if it needs the rest of the document, so you might
as well check for calls to position() and size() too.

> Both require an unbounded amount of look ahead.

As does replace="following-sibling::b"

-- Richard
Received on Thursday, 7 June 2007 14:51:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:43 UTC