Re: Definite list of XSLT 2.0 processors?

> - Native XSLT 2.0 for .NET. The XPath 2.0 datamodel
> is already there

Saxon.NET is 'native' thanks to IKVM.NET

> - Native C/C++ XSLT 2.0 processor for LAMP and others

You can run Saxon.NET on Linux using Mono. You can run Mono on Apache
using mod_mono. No issues with MySQL. You can run PHP on Mono using
http://php-compiler.net/

There it is, XSLT 2.0 on LAMP, although there's nothing native about it :-)
--
Max

2010/1/20 Abel Braaksma <abel.online@xxxxxxxxx>:
> Thanks to everyone for joining in on this discussion, which went slightly
> beyond my original intentions (a good thing), but learnt a few new things
> along the way. Was a bit surprised that throughout this thread, the market
> seems divided between LAMP and Java only. What happened to ASP, C#.NET or
> even desktop/tools? And what about browser's client-side XSLT 2.0?
>
> If I try to compile a little final list of all information so far, it'll
> look something like the following. If you have information about the gaps
in
> my information gathering, I'm (still/always) all ears.
>
>
> Complete implementations
> ------------------------
> - Saxon-HE, open source, basic [1][3]
> - Saxon-PE, commercial closed source, basic [2][3]
> - Saxon-EE, commercial closed source, schema-aware [2][3]
> - AltovaXML, free closed source, schema-aware[4]
> - IBM WebSphere Feature Pack, free* closed source, schema aware[5]
>
> *  the feature pack is free, WebSphere, to which it belongs, is not
>
>
> Incomplete implementations
> --------------------------
> - Intel XSLT 2.0, public beta free dl, basic*, 90% conformance [6]
> - Gestalt, open source, no more development, unknown conformance [7]
> - Oracle 10.1+, unclear status, no dl, unknown conformance [8]
>
> * Intel wants feedback, in particular about whether to implement SA.
>
>
> Alternatives
> ------------
> - EXSLT, extensions to XSLT 1.0 to close the gap, no conformance [9]
> - XSLT 2.0 through XSLT 1.0 (can't find the link anymore)
>
>
> No plans
> --------
> - Microsoft has postponed plans for XSLT 2.0 indefinitely [10]
>
> Wishes
> ------
> - Native XSLT 2.0 for .NET. The XPath 2.0 datamodel is already there
> - Native C/C++ XSLT 2.0 processor for LAMP and others
> - Open source C-interface for implementation in open source browsers
>
>
> References
> ----------
> [1]  http://saxon.sourceforge.net
> [2]  http://saxonica.com
> [3]  http://www.saxonica.com/feature-matrix.html
> [4]  http://www.altova.com/altovaxml.html
> [5]
 http://www-01.ibm.com/software/webservers/appserv/was/featurepacks/xml/
> [6]
>
 http://software.intel.com/en-us/articles/intel-soa-expressway-xslt-20-proces
sor/
> [7]  http://sourceforge.net/projects/gestalt/
> [8]  http://blogs.oracle.com/rammenon/2007/05/xslt_20.html
> [9]  http://www.exslt.org/
> [10] http://stackoverflow.com/questions/1525299/xpath-and-xslt-2-0-for-net
>
>
> Vyacheslav Sedov wrote:
>>
>> for C/C++ world maybe better option is to compile XSLT 2.0 stylesheet
>> into C/C++ code (if you need very fast conversion)
>>
>> but even with this case i suggest that pros and cons not vote for this
>> case too
>>
>> JDK7 with G1 for Saxon (maybe EE) probably much better idea to get
>> lightspeed XSLT 2.0 conversion (don`t forget about second front in
>> face of AMD & Intel "brains")
>>
>> 2010/1/20 Aaron Gray <aaronngray.lists@xxxxxxxxxxxxxx>:
>>>
>>> 2010/1/19 Imsieke, Gerrit, le-tex <gerrit.imsieke@xxxxxxxxx>:
>>>>
>>>> On 19.01.2010 21:51, Aaron Gray wrote:
>>>>>
>>>>> If I had time I would. Would be better if one or a subset of the Saxon
>>>>> development community did it.
>>>>
>>>> Dr. Kay's left leg, for example.
>>>
>>> It authored By one person ! Wow, sorry Dr Kay.
>>>
>>> Aaron