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 14:33:55 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28525-523-E3tSem430K@http.www.w3.org/Bugs/Public/>

--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
You seem to be suggesting something like the following:

xsl:param in           tunnel       static       select       required
---------------------- ------------ ------------ ------------ -------------
xsl:stylesheet etc     no           yes|no       allowed      yes|no
xsl:package            no           yes|no       allowed      yes|no
xsl:template           yes|no       no           allowed      yes|no
xsl:function           no           no           *** 1)       yes
xsl:iterate            no           no           *** 2)       yes

To bring all in line and make it orthogonal, what should we do with the
select-attribute? For xsl:function it is currently disallowed, for xsl:iterate
it is mandatory.

For xsl:iterate it may be reasonable to have a default value of ".". For
xsl:function we could simply ignore it if present (and a processor can issue a
warning). It could also be used on xsl:function to specify default values for
overloads with missing arguments, but I believe that ship has already sailed

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 30 April 2015 14:33:57 UTC

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