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

Re: Proposed component list

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

On 1/31/07, Norman Walsh <Norman.Walsh@sun.com> wrote:
> I think we want an XSLT1 component that processes XSLT 2.0 stylesheets
> in forwards compatibility mode and an XSLT2 component that processes
> XML 1.0 stylesheets in backwards compatibility mode.
> Defining a single component that does both puts a significant burden
> on implementors and users, IMHO.

On which way would this make it easier for implementors? I can see
that with 2 distinct components implementors won't need write code
that looks at the version attribute to decide which XSLT engine to
use, but I wouldn't consider this a significant burden.

What about users: in which way would two components make this simpler
for users? Isn't this creating unnecessary burden by asking them to
specify the version both in the stylesheet and in the component name?

Orbeon Forms - Web Forms for the Enterprise, Done the Right Way
Received on Thursday, 1 February 2007 01:17:36 UTC

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