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

Re: <input> for <pipeline>

From: Alessandro Vernet <avernet@orbeon.com>
Date: Fri, 5 Oct 2007 15:34:08 -0700
Message-ID: <4828ceec0710051534u26fcce00n3c040371b36e79ae@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

On 10/5/07, Norman Walsh <ndw@nwalsh.com> wrote:
> By way of an attempt to justify allowing default bindings for p:input
> on p:pipeline, consider this pipeline:
> [...]
> This seems like useful behavior to me.

Yes! Definitely.

When using XPL, we often have components or pipelines that take some
kind of "configuration", and this configuration is provided as an XML
document. Since we have options in XProc, I expect that in many cases,
we'll start using options instead of XML document. But when the
configuration is more complex, it will still make sense to provide it
as an XML document. And for those cases it makes sense for the
pipeline to provide a default value for that "configuration".

Alex
-- 
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
http://www.orbeon.com/
Received on Friday, 5 October 2007 22:34:17 GMT

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