When I compared your stylesheet with mine I found I had several
namespaces for EXSLT wrong! On the other hand I think you are missing
a extension-element-prefixes="exsl date func".

I have updated the file with a short description and because
its PI it can also be used directly with the browser.
http://documenta.rudolphina.org/available.xml

Many thanks,

Manfred

2008/5/2 James Fuller <james.fuller.2007@xxxxxxxxx>:
> you may also find my very old EXLST support testing scripts useful
>
>  described here http://jimfuller.blogspot.com/2007/09/testing-exslt-support.html
>
>  or u can directly try in the browser
>
>  http://www.webcomposite.com/func-avail.xsl
>
>  sometimes, u need to repeat the call to this... for reasons I have not
>  quite figured out .... in any event these scripts were meant to be run
>  by XSLT processor.
>
>  hth, Jim Fuller
>
>  On Fri, May 2, 2008 at 8:35 PM, Manfred Staudinger
>
> <manfred.staudinger@xxxxxxxxx> wrote:
>
>
> > 2008/5/2 Abel Braaksma <abel.online@xxxxxxxxx>:
>  >
>  > > Manfred Staudinger wrote:
>  >  >
>  >  > >
>  >  > >
>  >  > > >  In practice, of course, function-available() is almost always called
>  >  > with a
>  >  > > >  string literal as its argument.
>  >  > > >
>  >  > > >
>  >  > > The use case here is to get a quick reference which elements or
>  >  > > functions are not (jet) implemented and which extensions are available
>  >  > > in a certain version of an XSLT 1.0 processor (in a particular
>  >  > > browser).
>  >  > >
>  >  >
>  >  >  You may want to have a look at the post of Peter Mozolik, who showed a way
>  >  > to test for all EXSLT extensions, categorized per module, at 17/06/2007,
>  >  > subject line " EXSLT support report". An archived copy can be found
>  >  > here: http://biglist.com/lists/xsl-list/archives/200706/msg00279.html
>  >
>  >  Abel, thanks for the pointer. You can find my full xsl and xml here:
>  >  http://documenta.rudolphina.org/available.xsl
>  >  http://documenta.rudolphina.org/available.xml
>  >  It shows the state of implementation for xslt elements and functions
>  >  in 7 categories:
>  >     1 xslt instructions [shown when element-available() returns false()]
>  >     2 xslt top-level-elements [shown when element-available() returns true()]
>  >     3 xslt special-context-elements [shown when element-available()
>  >  returns true()]
>  >     4 xslt functions [shown when function-available() returns false()]
>  >     5 xpath functions [shown when function-available() returns false()]
>  >     6 extension elements [shown when element-available() returns true()]
>  >     7 extension functions [shown when function-available() returns true()]
>  >  Categories 2 and 3 are somewhat trivial and may be omited. To keep the
>  >  listing short, it shows only what cannot anticipated from the
>  >  standard: variations, additions etc. If you know of any extension not
>  >  listed in my xml, please tell me.
>  >
>  >
>  >  >  Notice that his code does seem to work with Saxon 6.5.5.
>  >  Cat. 7 from above works for me too, its only 4 and 5 which don't work
>  >  with Saxon 6.5.5!
>  >
>  >  Regards,
>  >
>  >  Manfred