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

Re: viewport

From: James Fuller <james.fuller.2007@gmail.com>
Date: Fri, 9 Nov 2007 18:05:37 +0100
Message-ID: <a0ad8ffe0711090905i7b12fb53o8a1e17a7b8a1ef2a@mail.gmail.com>
To: "Norman Walsh" <ndw@nwalsh.com>
Cc: public-xml-processing-model-comments@w3.org

On Nov 9, 2007 4:01 PM, Norman Walsh <ndw@nwalsh.com> wrote:
> Jim,
>
> / Norman Walsh <ndw@nwalsh.com> was heard to say:
> [...]
> | |     Is a viewport naturally a subpipeline?
> |
> | I'm not sure what you mean. A p:viewport is a compound step. The p:viewport
> | in Example 4.3.2 contains a subpipeline that consists of a single p:insert
> | step. Where is the conflict?
> |
> | |     Is it envisaged that the subpipeline, within a viewport, should
> | | encapsulated.... e.g. should there be a
> | |
> | | (p:for-each|p:viewport|p:choose|p:group|p:try|pfx:other-step|p:documentation|ipfx:ignored)*
> | |
> | | element? taking the 4.3.2 example
> |
> | A p:insert is a pfx:other-step :-)
>
> Are you satisfied by this answer?

yes, thank you.

J
Received on Friday, 9 November 2007 17:05:48 GMT

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