Re: Proposal: remove default binding of non-primary inputs

Correct me if I'm wrong, it just means that for non-primary inputs you MUST
precise which is the port you're refering to

For primary inputs and some special inputs (xpath-context, iteration-source,
viewport-source), the default input is the default redable port

It just means that for using defaulting you have to follow the simple case
where output of previous steps go to primary inputs

May be it is an unnecessary precaution, but I can live with that in V1 if no
one objects

By the way, it clearly means that depending the way your write your pipeline
can be a lot heavier (especially if we remove forward references...)

Mohamed


On Jan 28, 2008 9:35 PM, Norman Walsh <ndw@nwalsh.com> wrote:

> There was some support, and no dissent, to the question I asked about
> removing the default binding of non-primary inputs. In an effort to
> get us to Last Call sooner, I'm going to wait a day or so and if no
> one objects, I'm just going to make the change. So speak now...
>
>                                        Be seeing you,
>                                          norm
>
> --
> Norman Walsh <ndw@nwalsh.com> | Science is a way of talking about the
> http://nwalsh.com/            | universe in words that bind it to a
>                              | common reality. Magic is a method of
>                              | talking to the universe in words that
>                              | it cannot ignore. The two are rarely
>                              | compatible.--Neil Gaiman
>



-- 
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 €