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

Variables again

From: Norman Walsh <ndw@nwalsh.com>
Date: Thu, 01 May 2008 12:14:34 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <m2prs6ovbp.fsf@nwalsh.com>
Bah. Our decision to allow p:variable only at the start of a compound 
step introduces another spurious group:

<p:url-form-encode name="foo">
  <p:with-param name="foo" select="'bar'"/>
  <p:with-param name="bar" select="'baz'"/>
</p:url-form-encode>

<p:group>
  <p:variable name="param" select=".">
    <p:pipe step="foo" port="result"/>
  </p:variable>

  <p:string-replace match="whatever">
    <p:input port="source">
      ...
    </p:input>
    <p:option name="replace" select="concat(.,$param)"/>
  </p:string-replace>
</p:group>

We made this rule so that we wouldn't have to deal with what happens
when steps get reordered.

I wonder if it would make sense instead to say:

1. Variables are attached to the step that follows them.
2. No forward references allowed in the (possibly reordered) sequence.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | How can there be laughter, how can
http://nwalsh.com/            | there be pleasure, when the world is
                              | burning?--The Dhammapada (probably 3rd
                              | century BC)

Received on Thursday, 1 May 2008 16:15:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 1 May 2008 16:15:20 GMT