Re: What can a step implementation ask the pipeline processor?

/ Alessandro Vernet <avernet@orbeon.com> was heard to say:
| On 5/17/07, Henry S. Thompson <ht@inf.ed.ac.uk> wrote:
|>  [Wrt step implementations] The XPath context for evaluation of
|>  user-authored xpath expressions evaluated by step implementations
|>  SHOULD include at least all the *in-scope options* in the step
|>  environment visible as bound (XPath) variables, along with
|>  appropriate bindings for p:episode and p:document-position.
|
| Regarding this second rule:
|
| Yes, for the matching-documents components we are talking about.
| No, in general. I wouldn't want to have a blanket statement of that
| sort that applies to all the components. In particular, I wouldn't
| want options to be exposed as variables to stylesheets, as there are
| other more explicit and standard mechanisms to expose the value of a
| pipeline option to a stylesheet (answer: use stylesheet parameters).

Having the options available to the XSLT step as variables through the
XPath context wouldn't have any effect on the variables or parameters
available to the stylesheet. The XSLT spec specifies the initial context
for stylesheet evaluation.

I'd like to avoid making the availability of the options conditional
if at all possible.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Opportunity is missed by most people
http://nwalsh.com/            | because it is dressed in overalls and
                              | looks like work.--Thomas A. Edison