- From: <bugzilla@jessica.w3.org>
- Date: Thu, 11 Sep 2014 21:51:06 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26740 Michael Kay <mike@saxonica.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Michael Kay <mike@saxonica.com> --- The WG resolved today to drop the @visibility attribute from xsl:param. The effective visibility will always be private if the param is static, or public otherwise. If there is a wish to expose static params to another package, it is possible to bind a variable to the value of the parameter and export that variable. Of the other points in comment 2 the WG decided as follows: >Also note, that in this paragraph we do not mention an xsl:accumulator, which is allowed a visibility attribute, and we do not mention xsl:decimal-format... These (editorial) omissions were noted and should be fixed. >- an xsl:initial-template kinda implies public, doesn't it? In the interests of orthogonality we felt users should declare visibility="public" explicitly. The spec needs to point this out. >- and any xsl:package/@default-mode, because that is the mode initially called by the processor, should point to a public mode (or not?). There are use cases for a default mode to be private, so no change. >Further on, I found this, which seems to be contrary to the quoted paragraph above. Oughtn't an implicit mode be very, very private by default instead? Yes, this is an error. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 11 September 2014 21:51:07 UTC