Re: vendor neutral XSL extension namespace ?

[David Carlisle <davidc@xxxxxxxxx>]

> , but I think that they and other
> developers need to sign on to the "Common XSL" idea before anybody
> settles on a namespace.
> 
> The other side of the question is how do you decide what goes into
> "Common XSL" and how often does it change.

Yes, of course. It was just a suggestion that would make my life easier
if it could be made to work:-)

For it to work it would need the various implementors to just agree
between themselves to offer certain functionality from a common
namespace instead, or as well, as from the implementation specific 
namespace.
 
It may be too early yet, but if in a years time xsl 1 is stable, xsl 2
isn't yet even on the drawing board, and every xsl implementation is
offering xt:document functionality from a different namespace, I think
that perhaps an opportunity may have been missed.

On the otherhand if the plan is for xsl2 to follow soon on the heels of 
xsl1, then perhaps the effort required to set up an alternative
namespace coordination would have been wasted, and instead the effort
should go into implementing the functionality as standardised in the
next REC. Who knows....

David


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