W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1812] New: Need explicit statement on global variables and launch options

From: <bugzilla@wiggum.w3.org>
Date: Mon, 25 Jul 2005 00:17:34 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Dwqf0-0007g6-Ce@wiggum.w3.org>


           Summary: Need explicit statement on global variables and launch
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 2.0
        AssignedTo: mike@saxonica.com
        ReportedBy: david_marston@us.ibm.com
         QAContact: public-qt-comments@w3.org

Regarding the 4 April 2005 draft of XSLT 2.0:
Section 2.3 describes aspects of the context I can set at launch time for a 
transformation, including the initial mode and the initial context node. 
Section 9.5 says that the initial context node is NOT the context node for 
global variables unless the node is a document node. Section 9.5 should also 
address any other launch options that could affect the value of a global 
variable, such as the initial mode. I definitely cannot say that the draft 
gives solid assurance about
<xsl:apply-templates select="/fully/qualified/path" mode="#current"/>
in the content constructor of a global variable. Indeed, the use of the above 
statement in a global variable seems like a cheesy way to pass in a pseudo-
parameter by way of setting the initial mode; it would probably better coding 
style to have meaning expressed as an actual launch-time parameter and use 
xsl:choose in each global variable constructor that wants to adjust its value 
based on launch-time settings.
PROPOSED ACTION: if not already decided by the WG, raise an issue, then add 
verbiage to part 9.5 that states whatever you decided.
Received on Monday, 25 July 2005 00:17:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC