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

Re: Defaulting pipeline inputs and outputs

From: Innovimax SARL <innovimax@gmail.com>
Date: Fri, 10 Aug 2007 16:29:25 +0200
Message-ID: <546c6c1c0708100729s727de432p52bb4e9fa6af577e@mail.gmail.com>
To: "Norman Walsh" <ndw@nwalsh.com>
Cc: public-xml-processing-model-wg@w3.org

On 8/10/07, Norman Walsh <ndw@nwalsh.com> wrote:
> / "Innovimax SARL" <innovimax@gmail.com> was heard to say:
> |> The p:choose step does not have a primary input port, so the pipeline
> |> doesn't get one.
> |
> | How can we define a primary input port on p:choose ?
>
> First, we'd have to allow p:input on p:choose; we removed p:input from
> all the compound steps (except p:pipeline) a while back.
>
> If we allowed compound steps to declare p:inputs, then I think we
> could write rules for p:choose.
>
> But I'm not sure I want to do that.
>
Me neither, you answer to my concern now

Mohamed


-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Friday, 10 August 2007 14:29:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:54 GMT