W3C home > Mailing lists > Public > public-html-xml@w3.org > January 2011

Re: Use cases

From: John Cowan <cowan@mercury.ccil.org>
Date: Mon, 3 Jan 2011 00:32:18 -0500
To: Kurt Cagle <kurt.cagle@gmail.com>
Cc: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, Julian Reschke <julian.reschke@gmx.de>, Norman Walsh <ndw@nwalsh.com>, public-html-xml@w3.org
Message-ID: <20110103053218.GE2160@mercury.ccil.org>
Kurt Cagle scripsit:

> Saxon of course has the canonical XSLT 2.0 implementation, but as few
> browsers are written in Java, it can't be natively compiled into the
> C++ code --

Actually, it could probably be AOT-compiled using gjc, although this
would introduce a dependency on libgjc.

> there is a C# port of Saxon

In fact no.  Saxon for .NET is compiled from Java source
(slightly different from the source for the JVM) using ikvmc.
See http://www.ikvm.net for information on IKVM and ikvmc.

> Of course, if you COULD integrate Saxon into the Webkit stack, that
> would not only give you XSLT 2.0, but would also provide an up-to-date
> version of XQuery, which frankly would probably prove FAR more useful
> to non XML developers; the language is syntactically close enough
> to JavaScript that it could be picked up easily, and it's reasonably
> useful for handling light to moderate transformations, as well as for
> integrating external calls.

Currently, Mike Kay is developing a version of Saxon for
browsers, using GWT to compile a stripped-down version
of the Saxon-EE source into Javascript.  However, it
doesn't include XQuery, and it can't be open sourced.  See
for details.

BALIN FUNDINUL          UZBAD KHAZADDUMU        cowan@ccil.org
BALIN SON OF FUNDIN     LORD OF KHAZAD-DUM      http://www.ccil.org/~cowan
Received on Monday, 3 January 2011 05:32:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:27 UTC