- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Sep 2010 16:36:13 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10534 Summary: [XSLT] Definition of XTSE0680 Product: XPath / XQuery / XSLT Version: Working drafts Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: XSLT 2.1 AssignedTo: mike@saxonica.com ReportedBy: oliver@cbcl.co.uk QAContact: public-qt-comments@w3.org This also affects XSLT 2.0 The working draft specifies this: ERR XTSE0680 In the case of xsl:call-template, it is a static error to pass a non-tunnel parameter named x to a template that does not have a template parameter named x, unless the xsl:call-template instruction is processed with XSLT 1.0 behavior. The upshot of this is that it is an error to pass a non-tunnel parameter to a template which doesn't declare this non-tunnel parameter UNLESS it happens to declare a tunnel parameter with the same name (in which case the parameter passed is silently ignored. This interpretation of the spec is confirmed by the test tunnelparam20_015_01. Was it really the intention of the working group that the error should be ignored in this case or is it an oversight? I cannot see how this behaviour is at all beneficial, and can only lead to confusion. I suggest that the wording should be changed to: ERR XTSE0680 In the case of xsl:call-template, it is a static error to pass a non-tunnel parameter named x to a template that does not have a non-tunnel template parameter named x, unless the xsl:call-template instruction is processed with XSLT 1.0 behavior. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 2 September 2010 16:36:14 UTC