W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2015

[Bug 28525] [XSLT30] (editorial) Allowed/disallowed attributes of xsl:param

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Apr 2015 08:19:10 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28525-523-yFQnvGAQSv@http.www.w3.org/Bugs/Public/>

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
The inconsistency between "required" and "tunnel" exists already in the XSLT
2.0 specification. 

For xsl:param/@tunnel (end of 9.2) 2.0 says:

The optional tunnel attribute may be used to indicate that a parameter is a
tunnel parameter. The default is no; the value yes may be specified only for
template parameters.

For xsl:param/@required (earlier in the same section) 2.0 says:

The optional required attribute may be used to indicate that a parameter is
mandatory. This attribute may be specified for stylesheet parameters and for
template parameters; it must not be specified for function parameters, which
are always mandatory.

I'm disinclined to introduce a backwards incompatibility here just in the
interests of tidying this up. I'm more inclined to go the other way, by
allowing the values tunnel="no", required="yes", or static="no" in all cases
where the attribute is currently disallowed.

Having a table to present the options seems an excellent idea.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 30 April 2015 08:19:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:53 UTC