Jim, > let me try to explain the use case I would like; > > I would like to be able to set option values via commandline e.g. this > allows the computing environment to set their own defaults at runtime. > > one can set default values of p:option in declare-step but this means > the original xproc author is embedding how they see steps running (in > all environments); Xproc should be made easy to use by non-xproc folks > to execute. The author of a pipeline can define their pipeline to accept options, and then pass those along when they invoke the declared step. <p:pipeline name="example"> <p:option name="command-line-option" /> <ex:step name="example-step"> <p:option name="step-option" select="$command-line-option" /> </ex:step> </p:pipeline> Which options they choose to expose in this way is up to them. In what way doesn't this address your requirement? Jeni -- Jeni Tennison http://www.jenitennison.comReceived on Monday, 8 October 2007 16:11:05 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:42 GMT