RE: vendor neutral XSL extension namespace ?

["Richard Reich" <richard@xxxxxxxxx>]

And damn the language lawyers, SAXON's <assign> element would be real nice
too.

-r

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxx]On Behalf Of Sebastian Rahtz
> Sent: Saturday, November 06, 1999 2:26 PM
> To: xsl-list@xxxxxxxxxxxxxxxx
> Subject: Re: vendor neutral XSL extension namespace ?
>
>
> Tony Graham writes:
>  > The other side of the question is how do you decide what goes into
>  > "Common XSL" and how often does it change.  I'm sure that most users
>  > welcome the idea of common extensions that will increase
>  > interoperability of their stylesheets and let them use more of other
>  > people's, but who decides what's "common"?
>
> We could start with the list of desirables at the end of the XSLT
> spec; the items cited (grouping, writing to separate output
> documents) are already there. Just agreeing on names for some of
> those would be nice.
>
> Sebastian
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


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