[Bug 26781] [XSLT30] An argument / proposal for removing xsl:expose

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

--- Comment #3 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
As per the minutes of the XSL WG of telcon 2014-09-25
(https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Sep/0053.html, members
only), the recorded decision was:

<quote>
RESOLVED: to close bug 26781 by adopting proposal (a) of ABr's message
[1]: if no visibility attribute is present on a declaration, the
visibility of a component is determined by the xsl:expose declarations
at the package level; expose can lower but not raise the level of
visibility (retaining current rules). However, we did not adopt the
proposal to rename xsl:expose.

[1] https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Sep/0032.html

The result of this is that the priority of visibility specifications
is:

  - xsl:expose with explicit name (if more restrictive than the
    explicit value on the declaration)
  - visibility on the declaration itself
  - xsl:expose with wildcard
  - private

We agreed to mark bug 26781 as RESOLVED.
</quote>

This means that, given:

<xsl:function name="my:fun">...</xsl:function>

that the following will make this public:

1) <xsl:expose names="*" visibility="public" />
2) <xsl:expose names="my:*" visibility="public" />
3) <xsl:expose names="my:fun" visibility="public" />

This also means that, given:

<xsl:function name="my:fun" visibility="private">...</xsl:function>

that the same statements (1) and (2) above have no effect, and (3) will raise
an error (TBD).

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

Received on Friday, 26 September 2014 17:15:10 UTC