[Bug 25195] New: Visibility of xsl:param in xml-to-json stylesheet

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 25195] New: Visibility of xsl:param in xml-to-json stylesheet

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25195

            Bug ID: 25195
           Summary: Visibility of xsl:param in xml-to-json stylesheet
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

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

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

Reply | Threaded
Open this post in threaded view
|

[Bug 25195] [XSLT30] Visibility of xsl:param in xml-to-json stylesheet

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25195

Michael Kay <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Michael Kay <[hidden email]> ---
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.

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