Re: p:input vs. p:parameter-input

/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
| Norman Walsh writes:
|
|> * Users should be required to indicate that a particular input port is
|>   only for parameters on the p:declare-step (and on p:pipelines that
|>   they write).
|>
|> * Users should be forbidden from indicating that a particular input
|>   port is only for parameters on the "call" to the step. In other
|>   words, p:input should be used exclusively for both.
|
|> And
|>
|> * I think we should use paramters="yes|no" to indicate whether or not
|>   a particular input port is only for parameters.
|
| I can live with all this -- I note that the combination of the last
| two means in practice that 'parameters' is not allowed on the "call"
| to a step.

I don't follow. If the step being called has a parameter input, then
they can use it, they simply use p:input to do so.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Everything should be made as simple as
http://nwalsh.com/            | possible, but no simpler.