- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Feb 2014 12:01:18 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24509 --- Comment #3 from Michael Kay <mike@saxonica.com> --- If the proposal in bug #24510 (to drop group binding variables and revert to use of current-group() etc) is adopted, then this problem disappears because use of current-group() and current-grouping-key() within a pattern is already disallowed. If we don't go down that route, then I think it would make sense to disallow these binding variables within patterns, just as we currently disallow the corresponding functions. (I think the reason the fucntion calls are disallowed is primarily to do with template match patterns; we don't want a template to match a node or not depending on the circumstances. This argument doesn't apply directly to the group binding variables because they are not in scope for template match patterns anyway; but similar arguments extend to their use in other patterns, namely those used on xsl:number and xsl:for-each-group). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 24 February 2014 12:01:19 UTC