Re: injecting options and parameters into XProc

/ Vasil Rangelov <boen.robot@gmail.com> was heard to say:
| XProc doesn't allow that, but it does allow something else, which I
| think is more logical.
|
| You can define a *default* value for an option at the top of a
| pipeline. If a step has the same option, it will use that value.

Not automatically.

| And
| when the pipeline is invoked, it can override the value you've
| specified at the top of the pipeline.
|
| Example:
| <p:pipeline xmlns:p="http://www.w3.org/ns/xproc">
|   <p:option name="allow-version-mismatch" value="yes"/>
|   <p:option name="template-name" value="start"/>
|   <p:xslt2>
|     <p:input port="stylesheet">
|       <p:document href="stylesheet1.xsl"/>
|     </p:input>
      <p:option name="allow-version-mismatch" select="$allow-version-mismatch"/>
|   </p:xslt>
|   <p:xslt2>
|     <p:input port="stylesheet">
|       <p:document href="stylesheet2.xsl"/>
|     </p:input>
      <p:option name="allow-version-mismatch" select="$allow-version-mismatch"/>
|   </p:xslt>
|   <p:xslt2>
|     <p:option name="template-name" value="finish"/>
|     <p:input port="stylesheet">
|       <p:document href="stylesheet2.xsl"/>
|     </p:input>
      <p:option name="allow-version-mismatch" select="$allow-version-mismatch"/>
|   </p:xslt>
| </p:pipeline>

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Simplicity is always a virtue.--Edward
http://nwalsh.com/            | Abbey