I've logged this at
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26999
to ensure it gets attention. Please track it there.
Michael Kay
Saxonica
mike(_at_)saxonica(_dot_)com
+44 (0) 118 946 5893
On 8 Oct 2014, at 18:22, Martin Honnen martin(_dot_)honnen(_at_)gmx(_dot_)de
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Playing with the examples in http://www.w3.org/TR/xslt-30/#stream-examples I
wonder whether the last example saying
------------------------------
Additional template rules could be added to process other elements and
attributes in the same pass through the data: for example, to modify the
value of a last-updated attribute (wherever it appears) to the current date
and time, the following rule suffices:
<xsl:template match="@last-updated">
<xsl:attribute name="last-updated" select="current-dateTime()"/>
</xsl:template>
-------------------------------
is not lacking a mode="#all" or mode="delete-ednotes" on the
<xsl:template match="@last-updated">
as otherwise the template would not be applied to the document processed in a
streaming way with the stylesheet presented earlier which does
<xsl:mode name="delete-ednotes" streamable="yes"
on-no-match="shallow-copy"/>
and
<xsl:stream href="book.xml">
<xsl:apply-templates mode="delete-ednotes"/>
</xsl:stream>
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--