Re: <input> for <pipeline>

> | 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