[Bug 29551] New: [FO31] possible ambiguity in Note on fn:uri-collection and relation to streaming

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29551

            Bug ID: 29551
           Summary: [FO31] possible ambiguity in Note on fn:uri-collection
                    and relation to streaming
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

The second bullet in section 14.6.4. fn:uri-collection reads:

<quote>
In XSLT 3.0 it allows the documents in a collection to be processed in
streaming mode using the xsl:stream instruction.
</quote>

In XSLT 3.0, the fn:collection function is grounded, which means it cannot be
used in streaming (or better, it can, but it will, by definition, not be
streamed unless the processor decides to do so for other reasons outside the
scope of the spec)

I think this sentence is not incorrect per se, but it is confusing. I suggest
changing it to "allows the documents in a URI collection ....", or better "MAY
allow...", because the relation between URI collection and streamable documents
is not set. 

Also, this bullet point mentions "xsl:stream", though the only case where
fn:uri-collection comes into play in conjunction with streaming is xsl:merge.
The xsl:stream instruction does *not* accept a collection URI or multiple URIs.

The above remarks combined, I suggest something along the following lines:

<proposal>
In XSLT 3.0 it allows the documents in a URI collection to be processed in
streaming mode, for instance by applying each URI to the xsl:stream
instruction, or by using the result of fn:uri-collection as input for
xsl:merge-source/@for-each-stream.
</proposal>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 2 April 2016 15:41:28 UTC