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

[closed] Re: what about option values on directly invoked p:declare-step

From: Norman Walsh <ndw@nwalsh.com>
Date: Wed, 17 Sep 2008 06:48:50 -0400
To: public-xml-processing-model-comments@w3.org
Message-ID: <m2fxnzf3ot.fsf_-_@nwalsh.com>
Norman Walsh <ndw@nwalsh.com> writes:
> / James Fuller <james.fuller.2007@gmail.com> was heard to say:
> | 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
> | implementation-defined.'
> |
> | 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 ?
>
> Yes, I think so.

I've clarified the spec to make this point explicit about options and
parameters. I believe it was already explicit about inputs and
outputs, though I've moved that from the Introduction down into the
section about Inputs and Outputs.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Syllables govern the world.--John Selden
http://nwalsh.com/            | 

Received on Wednesday, 17 September 2008 10:49:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:41:08 UTC