W3C home > Mailing lists > Public > xproc-dev@w3.org > January 2012

RE: calling for xproc pain points, requested features, etc

From: Geert Josten <geert.josten@dayon.nl>
Date: Tue, 10 Jan 2012 08:54:32 +0100
Message-ID: <943f460408a1da4d2cbf2105ef42235e@mail.gmail.com>
To: Norman Walsh <ndw@nwalsh.com>, xproc-dev@w3.org
(sorry, meant to sent this to the list)

-----Oorspronkelijk bericht-----
Van: Geert Josten [mailto:geert.josten@dayon.nl]
Verzonden: dinsdag 10 januari 2012 8:54
Aan: 'Norman Walsh'
Onderwerp: RE: calling for xproc pain points, requested features, etc

+1 for adding a select on p:for-each. It could work similar to xsl:variable
and xsl:attribute. If there is a select, p:iteration-source is ignored (or
better: disallowed). In other words: keep the syntax compact where possible
and sensible..


> > It would be nice to write instead:
> >
> > <p:for-each select="//chapter" name="chapters">
> >   (do something)
> > </p:for-each>
> > Less typing, more use of existing knowledge.
> Fair enough. The point of p:iteration-source however, isn't the select
> attribute. It's for the binding:
> <p:for-each name="chapters">
>   <p:iteration-source select="//chapter">
>     <p:pipe step="someStep" port="somePort"/>
>   </p:iteration-source>
>   (do something)
> </p:for-each>
> If the select attribute was all that was needed, we would have put it
> on the p:for-each. Having the selection on p:for-each when there *is* a
> binding, seems...odd.
Received on Tuesday, 10 January 2012 10:34:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 10 January 2012 10:34:57 GMT