Re: Minutes for XProc WG telcon of 6 Apr 2006

Norman Walsh wrote:
> Right. That's what we decided last week. You'd have to say:
> 
> <p:pipeline>
>   <p:param name="debug">
>    <true/>
>   </p:param>
> 
>   <p:step name="xslt">
>     ...
>   </p:step>
> 
>   <p:if input="$debug" test="/true">
>     <!-- perform some debugging tasks -->
>   </p:if>
>   ...
> </p:pipeline>
> 
> We might decide that we need something simpler for this case.

Well, if we want consistency between steps and pipelines, I believe we 
should allow the definition of simple parameters (i.e. booleans, 
integers, etc.) in a pipeline, the same way it has been talked regarding 
steps parameters. Having this helps on defining a standardized 
sub-pipeline processing component.

Also, having pipeline parameters defined in in name/value pairs eases 
their assignment in pipeline execution environments (e.g. ./xproc 
mypipe.xml -Ddebug=true).

When more complicated parameters are required, they may be defined the 
way you propose.


Cheers,
Rui