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

Re: <input> for <pipeline>

From: Richard Tobin <richard@inf.ed.ac.uk>
Date: Fri, 28 Sep 2007 13:23:27 +0100 (BST)
To: Norman Walsh <ndw@nwalsh.com>, public-xml-processing-model-wg@w3.org
Message-Id: <20070928122327.DDACF269057@macpro.inf.ed.ac.uk>

> | After more thought, I am convinced that this just shouldn't be
> | allowed.  A p:pipeline is effectively a step declaration along with
> | implementation of the step.  It makes no more sense to allow binding
> | of inputs on p:pipeline than on p:declare-step.

> A binding on an p:input to a p:pipeline is intended to function as a
> default binding if the processor doesn't provide one.

Does it say that anywhere in the spec?

> Doesn't that seem like useful functionality?

Possibly, but if so why does it only to pipelines?  Why not
declare-step too?

And how does it interact with connecting the input to the default
readable port?

-- Richard
Received on Friday, 28 September 2007 12:24:28 UTC

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