This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25195 - [XSLT30] Visibility of xsl:param in xml-to-json stylesheet
Summary: [XSLT30] Visibility of xsl:param in xml-to-json stylesheet
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-28 15:11 UTC by Abel Braaksma
Modified: 2014-08-02 13:56 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2014-03-28 15:11:13 UTC
It took me a while to find out, for a moment I thought there was no default visibility, but under Potential Visibility[1], we write:

"For a component within its declaring package the potential visibility is the value of the visibility attribute on the component's declaration, or private if the attribute is absent."

Under B.2 [2], the appendix containing the xml-to-json stylesheet, none of the parameters have a visibility attribute, but in the text we explicitly state:

"The stylesheets are designed to be configurable by setting parameter values or by overriding selected template rules or functions."

I suggest we add the visibility attribute with value "public" to all parameters that are meant to be public and overridable.

[1] http://www.w3.org/TR/xslt-30/#dt-potential-visibility
[2] http://www.w3.org/TR/xslt-30/#xml-to-json-stylesheet
[3] http://www.w3.org/TR/xslt-30/#xml-to-json
Comment 1 Michael Kay 2014-07-31 13:08:27 UTC
Overtaken by events. The current version of the stylesheet is not in package form; there is an open action to convert it into a package, during which process we will need to look at the question of component visibility.