W3C home > Mailing lists > Public > xproc-dev@w3.org > July 2009

Re: Difficulty overriding parameter values

From: Norman Walsh <ndw@nwalsh.com>
Date: Tue, 07 Jul 2009 00:40:02 -0700
To: XProc Dev <xproc-dev@w3.org>
Message-ID: <m27hyl2b71.fsf@nwalsh.com>
"Toman_Vojtech@emc.com" <Toman_Vojtech@emc.com> writes:

> I remember discussing this some time ago, but I cannot find when and
> what the conclusion was. I think that:
>
> <p:pipeline>
>   <p:input port="source">
>     <p:document href="..."/>
>   </p:input>
>   ...
> </p:pipeline>
>
> is allowed, because p:pipeline is just a shortcut for
> p:declare-step. And in p:declare-step, you can provide default
> bindings for the input ports. But I vaguely remember there was
> something strange about p:pipeline in this regard.
>
> As I said, our implementation does allow this, but it may be a bug.
> Norm?

Yes, that's a bug.

<p:pipeline ...>
  <p:input port="source">
    <p:document href="..."/>
  </p:input>
  ...

is exactly the same as

<p:declare-step ...>
  <p:input port="source"/>
  <p:input port="parameters" kind="parameter"/>
  <p:output port="result"/>
  <p:input port="source">
    <p:document href="..."/>
  </p:input>
  ...

which is a duplicate declaration of the input port named "source".

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | One stops being a child when one
http://nwalsh.com/            | realizes that telling one's trouble
                              | does not make it better.--Cesare Pavese

Received on Tuesday, 7 July 2009 07:40:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 7 July 2009 07:40:47 GMT