W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > February 2007

Re: XSLT Component

From: Alessandro Vernet <avernet@orbeon.com>
Date: Wed, 31 Jan 2007 18:04:41 -0800
Message-ID: <4828ceec0701311804p509961f2ta0a0eb6dcfb5f68b@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

On 1/31/07, Alex Milowski <alex@milowski.org> wrote:
> A smart implementation can do the right thing a choose the right
> processor.  I did that in smallx in that XSLT 1.0 was handled by my version
> of  XT and XSLT 2.0 was handled by saxon.

I agree.

I just have some doubts about the warning mechanism. I am referring
to: "An implementations are allowed to use and XSLT 2.0 processor to
run an XSLT 1.0 transformation but a warning must be issued". I would
prefer, like Norm suggested, to have an optional parameter that the
pipeline author can set to say that he really wants to use an 1.0
engine or a 2.0 engine, whatever the version attribute in the
stylesheet says. In most cases pipeline authors won't need to worry
about this parameter and everything will work for them as expected.

Orbeon Forms - Web Forms for the Enterprise, Done the Right Way
Received on Thursday, 1 February 2007 02:04:46 UTC

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