W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > October 2009

RE: Runtime semantics of p:try

From: <Toman_Vojtech@emc.com>
Date: Thu, 1 Oct 2009 17:47:31 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC787110B8EE2@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-comments@w3.org>
> Indeed. How's this?
>    The output of a multi-container step is the output of exactly one
>    of its subpipelines. In this sense, a multi-container step
>    functions like a compound step. However, evaluating a
>    multi-container step may involve evaluating, or partially
>    evaluating, more than one of its subpipelines. It's possible for
>    steps in a partially evaluated pipeline to have side effects that
>    are visible outside the processor, even if the final output of the
>    multi-container step is the result of some other subpipeline. For
>    example, a web server might record that some interaction was
>    performed, or a file on the local file system might have been
>    modified.

I think this clarifies things very nicely.

Now, ehm, I just found another passage in the spec that seems to have
the same problem (Section 2, Pipeline Concepts):

"A pipeline must behave as if it evaluated each step each time it

Again, the sentence does not take multi-container steps into account.

Received on Thursday, 1 October 2009 21:49:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:27 UTC