W3C home > Mailing lists > Public > xproc-dev@w3.org > September 2008

Re: How does a processor get selected?

From: James Garriss <james@garriss.org>
Date: Fri, 19 Sep 2008 11:14:22 -0400
To: XProc Dev <xproc-dev@w3.org>
Message-ID: <C4F93A0E.88D%james@garriss.org>

If I were attempting to persuade someone to use XProc instead of writing
their own XML processing code, say in Java, would it be reasonable to say
that the ability to easily select various processors (this one for XSLT,
that one for XSD, some other one for Schematron, etc) and switch back and
forth among them is an advantage that XProc holds?  Or would this merely be
(potentially) an advantage of one XProc processor over another?


James Garriss

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 19 Sep 2008 09:23:19 -0400
To: James Garriss <james@garriss.org>
Cc: XProc Dev <xproc-dev@w3.org>
Subject: Re: How does a processor get selected?

James Garriss <james@garriss.org> writes:

> Suppose Im using Calabash, and it has its own XSLT processor (engine).
> Suppose I later decide I want to use a different XSLT processor, like Saxon.
> Does XProc itself allow me to select which processor to use?  Or is that
> implementation defined?  Or is that even an option?

Calabash doesn't have its own XSLT engine, it relies on Saxon. At the
there aren't any hooks to use a different processor. I'll probably add that
eventually, but there are lots of things higher on the todo list :-)

                                        Be seeing you,

Norman Walsh <ndw@nwalsh.com> | We ought not to heap reproaches on old
http://nwalsh.com/            | age, seeing that we all hope to reach
                              | it.-- Bion
Received on Friday, 19 September 2008 15:15:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:03 UTC