Re: Use cases


A friend of mine, M.David Peterson, was responsible for the ivkm port, and
yes, you're right, it was a .NET port across the ivkm platform, not C#. I
tend to use the two terms interchangeably, even though they obviously aren't
in all cases.

I'd heard Michael Kay discuss the Javascript Saxon project, but he didn't
include the link. Thanks.

Kurt Cagle
XML Architect
*Lockheed / US National Archives ERA Project*

On Mon, Jan 3, 2011 at 12:32 AM, John Cowan <> wrote:

> 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 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.
> --

Received on Monday, 3 January 2011 07:26:45 UTC