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

Re: Chameleon components

From: Alessandro Vernet <avernet@orbeon.com>
Date: Wed, 21 Feb 2007 15:21:59 -0800
Message-ID: <4828ceec0702211521n102262d9yb1536a1808cc95e3@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

On 2/21/07, Jeni Tennison <jeni@jenitennison.com> wrote:
> Application parameters should be settable using 'select' and 'value'
> attributes and with the content of an element.

Yes!

I am on the fence regarding configuration parameters. Defining the
version of XSLT, in the case where we have one processor for both XSLT
1.0 and 2.0, is the only case we discussed where a configuration
parameter could be useful. And this case goes away if we have 2
components for XSLT 1.0 and 2.0. So at this point it looks like
configuration parameters is not a very useful construct. Are there
other use cases that would better demonstrate the value of
configuration parameters?

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

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