This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24493 - xsl:merge streamability rules: roaming and free-ranging
Summary: xsl:merge streamability rules: roaming and free-ranging
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
: 24494 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-02-05 01:22 UTC by Abel Braaksma
Modified: 2014-02-24 15:52 UTC (History)
1 user (show)

See Also:


Attachments

Description Abel Braaksma 2014-02-05 01:22:25 UTC
Perhaps this section (15.4) should better go under section 19? But I believe this was discussed already at the latest telcon.

See also bug 24343 which is related.

The guaranteed streamability rules do not say anything when the rules are not met. A line similar to rules elsewhere "Otherwise, the construct is roaming and free-ranging". However, only if the attribute streamable=yes is supplied.
Comment 1 C. M. Sperberg-McQueen 2014-02-11 12:05:08 UTC
We discussed this in Prague.

With regard to the first issue, we noted that section 19.10 does have a sort of top-level launch pad for all guaranteed-streamability analysis.  

- It would be helpful to have hyperlinks from the first numbered list in 19.10 to the appropriate subsections (e.g. 15.4 and 18.2.7).

- It might be helpful to hyperlink to 19.10 from the opening paragraphs of 19.

We are not inclined to pull 15.4 and 18.2.7 etc. into section 19.

On the issue in the third paragraph, we concluded that no catch-all final clause is actually needed; the work it would do is handled by the following paragraph.
Comment 2 Michael Kay 2014-02-20 16:53:40 UTC
*** Bug 24494 has been marked as a duplicate of this bug. ***