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

Re: Chameleon components

From: Alessandro Vernet <avernet@orbeon.com>
Date: Tue, 20 Feb 2007 23:36:00 -0800
Message-ID: <4828ceec0702202336r54e5417etbdf216e05e73e409@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

On 2/18/07, Jeni Tennison <jeni@jenitennison.com> wrote:
> So, on 1:
>
> I think it's a mistake to bundle multiple applications into a single
> component (i.e. have "p:transform" and "p:validate" steps) because they
> have completely different interfaces. [...]

You're exposing your line of reasoning with eloquence, and yes, I am convinced.

> On 2:
>
> (b) parameter names are element names (i.e. we have <p:initial-mode>
> elements inside <p:xslt2>)

I like this as well. In the case of XSLT, there are number of use
cases where those parameters need to be dynamic. So with this syntax
we can easily support on <p:initial-mode> the same constructs we do on
<p:parameter>, for instance:

<p:xslt-2.0>
    <!-- Initial template set statically -->
    <p:initial-template value="some-template"/>
    <!-- Initial mode extracted from a document -->
    <p:initial-mode select="/param/initial-mode">
        <p:pipe step="parameters" port="result"/>
    </p:initial-mode>
</p:xslt-2.0>

Alex
-- 
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/
Received on Wednesday, 21 February 2007 07:36:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:49 GMT