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 19084 - [XSLT 3.0] Accumulators and import precedence
Summary: [XSLT 3.0] Accumulators and import precedence
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
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: 2012-09-26 22:55 UTC by Michael Kay
Modified: 2014-05-15 14:00 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2012-09-26 22:55:21 UTC 
We say nothing on the question of whether accumulators can be overridden in an importing stylesheet, or what constraints there are on such overriding; nor do we say anything about accumulators in the context of packages. We give accumulators a "visibility" attribute, but section 3.6.2 defines visibility as a property of a "component", and accumulators are not currently included in the definition of components.
Comment 1 Michael Kay 2013-02-12 10:01:18 UTC 
Agreed that accumulators should be named components, should be subject to import precedence using the usual rules for named components. We shouldn't provide any mechanism to override individual accumulator rules selectively. Editor to draft the required text.
Comment 2 Michael Kay 2013-05-16 11:44:48 UTC 
The principles for the resolution of this were agreed in the Prague F2F and the editor responded by drafting detailed text which is present in the current review draft.
Comment 3 Michael Kay 2013-07-31 15:44:33 UTC 
The new text has now been approved.