Re: Steps with non-connected outputs

On 4/11/07, Alessandro Vernet <avernet@orbeon.com> wrote:
>
>
> Consider the following example, inspired by some code Norm sent earlier:
>
> <p:pipeline name="pipeline"
>         xmlns:p="http://www.w3.org/2007/03/xproc"
>         xmlns:ex="http://example.org/ns/xproc-extensions">
>
>     <p:declare-step type="ex:db-query">
>         <p:output port="result" sequence="no"/>
>         <p:parameter name="database" required="yes"/>
>         <p:parameter name="query" required="yes"/>
>     </p:declare-step>
>
>     <ex:db-query name="query">
>         <p:parameter name="database" value="mydb"/>
>         <p:parameter name="query" value="some query"/>
>     </ex:db-query>
>
> </p:pipeline>
>
> The ex:db-query component produces an output, but is not used in this
> pipeline. Questions:
>
> 1) Is this a valid pipeline?


Yes.

2) If it is, should the query be sent to the database (yes, no,
> implementation dependent)?



Yes.


-- 
--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered."

Bertrand Russell in a footnote of Principles of Mathematics