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

Re: Comments on August 22 editors' draft from section 2.8 through 4.2

From: Norman Walsh <ndw@nwalsh.com>
Date: Tue, 28 Aug 2007 14:00:15 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <m2d4x74k0g.fsf@nwalsh.com>
/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
| Norman Walsh writes:
|
|> | 4.2
|> |
|> |   "When a pipeline needs to process a sequence of documents using a
|> |    subpipeline that begins with a step that only accepts a single
|> |    document, the p:for-each construct can be used as a wrapper around
|> |    the step that accepts only a single document."
|> |
|> |     -->
|> |
|> |   "When a pipeline needs to process a sequence of documents using a
|> |    step that only accepts a single document, the p:for-each construct
|> |    can be used as a wrapper around that step."
|>
|> I had that originally. Someone argued that that made it sound like
|> a for-each could only contain a single step.
|
| Hmmm, I see.  Unfortunately the current wording reads as if there's a
| delimited subpipeline already identified.  How about
|
|   "When a pipeline needs to process a sequence of documents using a
|    step that only accepts a single document, the p:for-each construct
|    can be used as a wrapper around that step (and as many of its
|    following siblings as required)."

Ok by me.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | We have fewer friends than we imagine,
http://nwalsh.com/            | but more than we know.--Hugo Von
                              | Hofmannsthal

Received on Tuesday, 28 August 2007 18:00:35 GMT

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