RE: Standard Java XSLT API (was re:SAXON 5.0 is available)

Agreeing a set of XPath-level interfaces to extension functions that should
be available in several products is relatively easy; defining a Java API
that allows implementations of extension functions to work with several
products is much harder, albeit desirable. Start by thinking about
"node-set" which needs to be a visible class in this interface; you then
naturally go on to describe the full tree data model as a set of Java APIs,
and you end up exerting a strong influence on the design of the product's
internal data structures.

Remember that even the DOM API at the moment has no standard extensibility
mechanisms.
> 
> It would be very nice to have both an accepted standard Java 
> XSLT api as well as some reasonably fair and conventional performance 
> benchmarks. 


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