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 22721 - [xslt 3.0] Streamability of attribute-sets
Summary: [xslt 3.0] Streamability of attribute-sets
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC All
: 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:
Depends on:
Blocks:
 
Reported: 2013-07-18 13:22 UTC by Michael Kay
Modified: 2014-05-15 14:00 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2013-07-18 13:22:16 UTC
We say that an xsl:element instruction (say) with a use-attribute-sets attribute can be streamable if the attribute set is streamable.

This assumes that at the time we do the streamability analysis, we know which attribute-set will be used. But since this binding is not determined until all the packages making up the stylesheet have been assembled, the result is that we can't assess streamability on a single package individually. This seems unfortunate, especially as streaming may cause radical changes to the way a package is compiled.

In practice most attribute sets will be motionless so it's a shame to disallow their use simply because of the remote possibility of free-ranging behaviour.

We could add an attribute streamable=yes|no to xsl:attribute-set and say that if streamable=yes is specified, the body must be motionless.
Comment 1 Michael Kay 2013-09-22 20:50:36 UTC
At the New York face to face this proposal was accepted, with the additional proviso that a non-streamable attribute set may not override a streamable one.