[Bug 29818] [xslt30] Visibility and Applicability of Accumulators

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

Abel Braaksma <abel.braaksma@xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |abel.braaksma@xs4all.nl

--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
The WG asked me to consider the impact of making all accumulators public as a
resolution to this issue (action ACTION 2016-10-06-003).

Proposed condensed set of rules:

1) All accumulators are public by default

2) Accumulators cannot be overridden with xsl:override (status quo)

3) Name clashes of declarations are detected statically, names from used
packages may not clash with one another

4) Normal import precedence rules on names apply (status quo)

5) Accumulators may be used on any tree, unless this is limited by fn:copy-of
etc on a streamed tree, which itself was limited by @use-accumulators.


These rules have the benefit of simplifying the complexity introduced by the
proposal on the "originating document" w.r.t. accumulators, but have the
down-side that a user will not be able to use two packages together if they
have conflicting names (which we could resolve, but only by introducing new
language elements or rules).

I don't really think the suggestion below in comment#1, about names of
different kinds of objects to be handled in the same way, is relevant, we
already have different rules on naming for different kinds of objects
(regrettably so).

However, this proposal does feel a bit like a sledge hammer approach where a
much smaller tool could've been sufficient. I'll reconsider the proposal from
Mike below.

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

Received on Thursday, 6 October 2016 19:28:54 UTC