2008/5/3 Michael M|ller-Hillebrand <mmh@xxxxxxxxxxxxx>:
>  * I guess it would be very useful to visibly report the processor type and
> version.
Yes ... but what would you expect to see in your case (Safari 3.1.1) ?

>  * Regarding the xslt element numbers, it would be useful to know the
> maximum numbers (according to the spec)
>  * Regarding any listed items: it might be useful to know if
> element-available() or function-available() or both triggered their
> appearance
Agree with both, the description was a bit poor, it should be better
now. Please check it:
http://documenta.rudolphina.org/available.xml

Regards,

Manfred

2008/5/3 Michael M|ller-Hillebrand <mmh@xxxxxxxxxxxxx>:
> Am 03.05.2008 um 01:26 schrieb Manfred Staudinger:
>
>
>
> > 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
> >
>
>
>  According to your XML/XSL Safari 3.1.1 supports saxon:output and
> exsl:node-set:
>
>  1. xslt instructions (18 in total)
>  2. xslt top-level-elements (12 in total)
>  3. xslt special-context-elements (5 in total)
>  4. xslt functions (9 in total)
>  5. xpath functions (27 in total)
>  6. extension elements
>    - saxon:output: true
>  7. extension functions
>    - exsl:node-set: true
>
>  Some ideas:
>
>  * I guess it would be very useful to visibly report the processor type and
> version.
>  * Regarding the xslt element numbers, it would be useful to know the
> maximum numbers (according to the spec)
>  * Regarding any listed items: it might be useful to know if
> element-available() or function-available() or both triggered their
> appearance
>
>  - Michael M|ller-Hillebrand
>
>  --
>  _______________________________________________________________
>  Michael M|ller-Hillebrand: Dokumentations-Technologie
>  Adobe Certified Expert, FrameMaker
>  Lvsungen und Training, FrameScript, XML/XSL, Unicode
>  <http://cap-studio.de/> -- Tel. +49 (9131) 28747