Re: EXSLT 1.0 Proposed List

My *personal* opinion is that if I can develop XSLT 2.0 applications with 
even the current XSLT 2.0 processors and IDEs for them, I'd never use EXSLT 
for XSLT 1.0 unless I'm paid to do this.

Even after a group of people makes a big effort and produces a library that 
make XSLT 1.0 + EXSLT very *slightly* resemble XSLT 2.0.

On the other side, I will readily use valuable EXSLT extensions for XSLT 2.0 
such as the

   xxx:memo-function attribute

and the

   xxx:compiled-stylesheet element.

Another group of useful extensions to XSLT 2.0 would be a module of 
functions that implement retrospectiveness (although FXSL already provides 
such functions).

I should very definitely express the respect I have towards Uche Ogbuji and 
his XSLT 1.0 + EXSLT related activities. At the same time, I can only accept 
as a personal opinion that is not absolutely true, Uche's statements about 
XSLT 2.0 ("painful excess") and XPath 2.0 ("is a mess").

To be objective we need to hear the opinion of people that are in the heart 
of XSLT 2.0 and XPath 2.0 design, such as Michael Kay.

I strongly believe that EXSLT is and should be the result of collective 
effort, not based just on single opinions and believes.

-- 
Cheers,
Dimitre Novatchev
---------------------------------------
The significant problems we have cannot be solved at the same level of 
thinking with which we created them.





"John L. Clark" <[email protected]> wrote in message 
news:20060213175858.GM10347@rejoice...
> One of our immediate goals is to decide upon a stable set of extensions
> that we can call "EXSLT 1.0".  To this end, several interested people
> have been working to develop an ad-hoc list that provides a high-level
> perspective on both the extensions that we currently have and the
> extensions that we still want to add.  I've attached a copy of this list
> to this email for your review.
>
> We need to decide what to include from this list, to write or modify
> specifications for those items that are not currently provided by EXSLT
> or that need changes, and then, of course, to work on implementations
> (not necessarily in that order).  There is also a fair amount of
> infrastructural upgrading that needs to happen (think XSLT/Web hacking).
> As a result, there is plenty to say and do, so if you feel like
> commenting or contributing, you would be welcome.
>
> Take care,
>
>    John L. Clark
>


--------------------------------------------------------------------------------


> _______________________________________________
> exslt mailing list
> [email protected]
> http://www.exslt.org/list