Kimbro Staken wrote:
> Even in the collection case you could certainly
> write an XSLT engine that evaluates all XPaths in a collection context
> rather then a document context and would solve the same problem. That
> wouldn't really be standard XSLT but would be standard XQuery.

It certainly would be standard XSLT, if you simply provide an instance of
XSLT's data model, which consists of a source tree root node that may
contain multiple element nodes, text nodes, etc.  The XQuery "ordered
forest" model of a collection, though currently quite underspecified, is
quite similar to this idea.

Evan Lenz
XYZFind Corp.


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list