XSLT 1.1 is now public

[Sc...@lotus.com]

The new working draft of XSLT 1.1 is now public (
http://www.w3.org/TR/xslt11/).  It has a lot of really good stuff.

One of the things we have to decide is whether it is more important to
upgrade XalanJ2 to the new draft, or if we should focus on "streaming" and
other performance issues for right now.

-scott

Re: XSLT 1.1 is now public

[Thorbjoern Ravn Andersen <tr...@mrbean.stibo.dk>]

* Scott_Boag@lotus.com <Sc...@lotus.com> [Dec 15. 2000 20:23]:
> The new working draft of XSLT 1.1 is now public (
> http://www.w3.org/TR/xslt11/).  It has a lot of really good stuff.
> 
> One of the things we have to decide is whether it is more important to
> upgrade XalanJ2 to the new draft, or if we should focus on "streaming" and
> other performance issues for right now.

I think we would all benefit the most by Xalan 2.0 maturing on the 1.0
spec, and then seeing the new facilities being added to a later release.

Adding new goals in midstream would just delay a release.

-- 
  Thorbjørn Ravn Andersen                   "...sound of... Tubular Bells!"
  http://bigfoot.com/~thunderbear

Re: XSLT 1.1 is now public

[st...@sas.upenn.edu]

Scott_Boag@lotus.com wrote:
> 
> The new working draft of XSLT 1.1 is now public (
> http://www.w3.org/TR/xslt11/).  It has a lot of really good stuff.
> 
> One of the things we have to decide is whether it is more important to
> upgrade XalanJ2 to the new draft, or if we should focus on "streaming" and
> other performance issues for right now.
> 
> -scott

If it is possible to provide an initial implementation of XSLT 1.1 (even
if just the node-set/RTF and xsl:document support hacked in by mapping
the XSL surface onto the extant Xalan internals) without too much effort
I think it would be sensible to do. 

Every day without XSLT 1.1 support increases the number of scripts that
have to be updated.

 Steve