W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2015

[Bug 28210] [XSLT30] we allow calling xsl:override(), but don't say anything about referencing it and calling it elsewhere

From: <bugzilla@jessica.w3.org>
Date: Fri, 13 Mar 2015 18:08:08 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28210-523-uh2WH7TtXo@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28210

--- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
I noted section 3.6.3.5 Dynamic References to Components on dynamic references,
which seems to allow private components to be made available outside of their
own scope, but it is not clear to me whether it covers the case mentioned
above.


Related to this is the process of binding, which is specified under 3.6.3.4
Binding References to Components. That section seems to disallow binding to a
symbolic identifier with another name or to identifiers that are HIDDEN, while
the previous section says the opposite (as quoted above).

<quote>
When reference resolution is performed for a component C, each symbolic
reference R that is present in the declaration of C is processed as follows:

1. If C already contains a binding for R then this binding is retained.

2. If C contains no binding for R then the processor attempts to locate a
component in the containing package of C whose visibility is not hidden and
whose symbolic name matches R. If there is no such component, then a static
error is reported as described elsewhere in this specification. There can never
be more than one. Call the located component D. If D has visibility private or
final, then C acquires a binding that associates the symbolic reference R with
the component D. Otherwise, the reference remains unbound.
</quote>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 13 March 2015 18:08:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:53 UTC