Re: injecting options and parameters into XProc

/ Vasil Rangelov <boen.robot@gmail.com> was heard to say:
|>A step can't see it's own options.
|
| Does that mean that
| <p:pipeline xmlns:p="http://www.w3.org/ns/xproc">
|     <p:xslt2>
|       <p:input port="stylesheet">
|         <p:document href="stylesheet1.xsl"/>
|       </p:input>
|       <p:option name="allow-version-mismatch" value="no"/>
|  	<p:option name="allow-collections"
| select="$allow-version-mismatch"/>
|     </p:xslt2>
| </p:pipeline>
|
| Is a (static?) error, since there is no allow-version-mismatch option
| anywhere outside the p:xslt2 step, even though there is such within the step
| itself (AND is explicitly specified)? Doesn't seem right...

Yes, it's a static error. Seeming right may be a matter of opinion :-)

Not allowing different options in the same scope to see each other
means that we don't have to worry about the order in which options
occur or circularity of reference.

                                        Be seeing you,
                                          norm

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