Re: EXSLT 1.0 Proposed List

this is an interesting thread, basically asserting that XSLT v1 + EXSLT
= XSLT 2.0 with schema fun;

I must admit that I to am using XSLT 2.0 and mostly ignoring the schema
stuff (seems to pleasantly go into the background, barring some
non-intuitive implicit casting fun). There is also a serious performance
gain using XSLT 2.0 which is making it a compelling answer to some hard
XML processing problems.

a few musings, to broaden it past the typical XSLT 1.0 vs XSLT 2.0 arg;

* is it silly to see something like EXSLT inside of XQUERY and XSLT
v2.0....not sure, esp if its just an EXSLT wrapper around native
functionality.

* is it silly to envision EXSLT embedded in any XML markup ? to be
processed by whatever XML processor acts upon it?

* it does make me a little nervous seeing something like XPATH bloat and
throw lots of diverse functionality under a catchall fn: namespace

* could other efforts like exist.sourceforge.net striking could
seriously benefit from a more standardized approach to function libraries

* should we consider looking at XSLT 2.0 implementations (along with our
existing EXSLT,MSXML, JS, XSLT1)?

I personally would like to see EXSLT broaden its appeal/usage; though I
am unsure of what it means to XSLT v2...perhaps through  new modules 
and  submissions there maybe more uptake...who knows. First things first
and thats to knock what we have now into a good foundation.

cheers, Jim Fuller