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

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

            Bug ID: 26781
           Summary: [XSLT30] An argument / proposal for removing
                    xsl:expose
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org

When xsl:stylesheet was a child of xsl:package it seemed to make sense to have
an extra layer of indirection for exposing elements of that child to the
outside world. Now that xsl:stylesheet is not a child anymore, I think the need
for xsl:expose is gone.

The only things xsl:expose can do is hide things:
- change public to private or final
- change final to private

These options are already available in the visibility attribute of the
declarations. Having the visibility attribute present, exposes them. If someone
wants a declaration hidden, they can change that attribute. I don't see the
need (anymore) for having an extra declaration that can change the already
statically present visibility.

The biggest use-case, I think, was to allow, at package level, to hide parts
that were introduced with xsl:use-package. However, that declaration has an
xsl:accept (by using hidden or absent), in which the user can decide to accept
or not certain items. Again, two ways to achieve, I think, exactly the same.

In short: my proposal is to drop xsl:expose. It also gets rid of potential vs
exposed visibility, which I think is a good thing.

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

Received on Thursday, 11 September 2014 00:19:04 UTC