The focus in XSLT 3.0 is on streaming large XML documents, however the need for
streaming large text files has not been overlooked.
Two of the features that were added to make this easier for implementations to
achieve are
(a) the unparsed-text-lines() function. The WG considered that most use cases
for processing large text files started by breaking it into lines, and that it
was easier for implementation to achieve this if there was an explicit function
to read the file as a sequence of lines.
(b) the ability to do xsl:for-each-group starting-with and ending-with with
patterns that match strings rather than nodes
There's no explicit way of saying that you want text input streamed; the WG
felt that given the above constructs, implementations would be able stream the
input without further guidance from the user.
Michael Kay
Saxonica
mike(_at_)saxonica(_dot_)com
+44 (0) 118 946 5893
On 30 Nov 2014, at 22:33, Ihe Onwuka ihe(_dot_)onwuka(_at_)gmail(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Am I right that XSLT 3.0 streaming doesn't extend to very large text files,
i.e 2.0 limitations still apply.
XSL-List info and archive
EasyUnsubscribe (by email)
--~----------------------------------------------------------------
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
--~--