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

RE: Iteration position and size

From: <Toman_Vojtech@emc.com>
Date: Mon, 23 Nov 2009 10:46:48 -0500
Message-ID: <997C307BEB90984EBE935699389EC41C286B3E@CORPUSMX70C.corp.emc.com>
To: <public-xml-processing-model-wg@w3.org>
In our implementation, only p:for-each and p:viewport affect the value
of p:iteration-position() and p:iteration-size(). The other built-in
steps use whatever value they inherit. I seem to recall I asked about
this some (long) time ago. I will try to find that e-mail message.


> -----Original Message-----
> From: public-xml-processing-model-wg-request@w3.org 
> [mailto:public-xml-processing-model-wg-request@w3.org] On 
> Behalf Of Norman Walsh
> Sent: Monday, November 23, 2009 4:39 PM
> To: public-xml-processing-model-wg@w3.org
> Subject: Iteration position and size
> The spec says:
>   In the context of a p:for-each or a p:viewport, the
>   p:iteration-position function reports the position of the document
>   being processed in the sequence of documents that will be processed.
>   In the context of other standard XProc compound steps, it returns 1.
> But test viewport-005 checks the position inside a p:choose where we
> clearly expect the value not to be reset. For which other steps do we
> expect the value not to be changed? try/catch? group? 
>                                         Be seeing you,
>                                           norm
> -- 
> Norman Walsh <ndw@nwalsh.com> | The bane of my existence is doing
> http://nwalsh.com/            | things that I know the computer could
>                               | do for me.--Dan Connolly
Received on Monday, 23 November 2009 15:47:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 November 2009 15:47:28 GMT