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

Corrections in 5.8 p:declare-step

From: Innovimax SARL <innovimax@gmail.com>
Date: Sat, 3 May 2008 10:53:00 +0200
Message-ID: <546c6c1c0805030153v96acccexd5e4370c3bca233c@mail.gmail.com>
To: "XProc WG" <public-xml-processing-model-wg@w3.org>
In 5.8 p:declare-step

Irrespective of the context in which the p:declare-step occurs, there are
initially no option or variable names in-scope inside a p:declare-step. That
is, p:option <http://www.w3.org/XML/XProc/docs/langspec.html#p.option> and
p:variable <http://www.w3.org/XML/XProc/docs/langspec.html#p.variable>elements
can refer to values declared by their preceding siblings, but not
by any of their ancestors.

I would say that it is too restrictive

<p:pipeline xmlns:p="http://www.w3.org/ns/xproc" name="pipeline" xmlns:ix="
    <p:variable name="foo" select="'bar'"/>
    <p:declare-step name="recursive" type="ix:recursive">
        <p:variable name="myfoo" select="$bar"/>          [you want to make
this impossible...]
        <p:variable name="bar" select="'bar'"/>
            <p:variable name="mybar" select="$bar"/>     [...but not this
one, do you ?]

Want you wanted to say, I think, is more

That is, p:option <http://www.w3.org/XML/XProc/docs/langspec.html#p.option>and
p:variable <http://www.w3.org/XML/XProc/docs/langspec.html#p.variable>elements
cannot refer to values declared by ancestors of there innermost

Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Saturday, 3 May 2008 08:54:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:45 UTC