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

Re: default pipeline input

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Mon, 12 Mar 2007 12:01:54 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87zm6ilabx.fsf@nwalsh.com>
/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
| But I think on reflection that we should default to the _first_
| of the pipeline's declared inputs even if there are more than one.
| Reason being that I'm pretty sure most implementations will map stdin
| to the first declared input, and it will confuse users if that default
| doesn't carry through inside, as it were.

I don't have any plans to implement stdin that way, but nevermind :-)

I could live with that story.

| Or does this bring us back to the question of defaulting the primary
| input declaration for all containers, which we discussed a while ago
| and stalled on. . .?

I thought the solution we came up with subsumed the discussion.

For every case except the very beginning of a p:pipeline, there will
be a preceding step which either provides a default readable port or
there isn't a default readable port.

Any unbound input on a step is bound to the default readable port.

Some rule that establishes the default readable port in the p:pipeline
gives us complete coverage, I think.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.

Received on Monday, 12 March 2007 16:02:10 GMT

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