W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > May 2008

what about option values on directly invoked p:declare-step

From: James Fuller <james.fuller.2007@gmail.com>
Date: Thu, 1 May 2008 21:39:17 +0200
Message-ID: <a0ad8ffe0805011239q73100494l58d123fee0320c8@mail.gmail.com>
To: public-xml-processing-model-comments@w3.org

in the May 1st spec, it currently states in section 5.8 p:declare-step

'When a declared step is evaluated directly by the XProc processor (as
opposed to occurring as an atomic step in some container), how the
input and output ports are bound to documents is

I imagine this allows direct invocation of a p:declare-step, which
might look something like the following from the commandline;

> xproc -f somexprocfile.xpl somexprocstep

is it an oversight that there is nothing in this section about the
values/handling of other bits like  parameters, options, etc ?

also, I know that we are not specifying the signature of the
commandline, but perhaps we could use the following as an example of
how option/value pairs are 'injected' into the xproc ....

> xproc -f somexprocfile.xpl somexprocstep someoption=someoptionvalue someotheroption=someothervalue

it occurs to me that we might want to consider it an error if an
option is not defined as well.

cheers, Jim Fuller
Received on Thursday, 1 May 2008 19:39:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:25 UTC