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

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

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I don't think the use case for xsl:expose has gone away. The rationale was to
allow an existing collection of stylesheet code to be packaged without
modifying the code, by writing a package manifest which you now write in the
form

<xsl:package ...>

  <xsl:import href="existing-code.xsl"/>

  <xsl:expose ...>

</xsl:package>

Using xsl:expose here is more self-contained than trawling through all the code
adding visibility attributes; it's more appropriate when you don't own that
code, and it's probably a sensible approach if that code has to continue
working under XSLT 2.0.

The removal of the xsl:stylesheet level changes the way this manifest is
written, but it doesn't alter the need for the feature. We could argue that the
facility is "a bridge too far" and that the need is not strong enough to
justify the complexity, but that's a different argument.

I'm very reluctant to spend time on re-examining requirements at this stage, or
we will never finish.

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

Received on Thursday, 11 September 2014 08:52:45 UTC