- From: <bugzilla@jessica.w3.org>
- Date: Fri, 30 Oct 2015 11:51:55 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29251
Abel Braaksma <abel.braaksma@xs4all.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |abel.braaksma@xs4all.nl
--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Looks good.
Two minor suggestions, editorial:
1) If possible, I would prefer to enumerate the exact function list. I
understand they are visible, but in many likewise situations we enumerate for
completeness.
2) I thought the term "function item" was changed to "function"?
3) I would prefer the system-property to be called
"xsl:supports-higher-order-functions". It matches the text better, plus it
covers better what it does.
Besides, any XSLT implementation will have to support function items (maps and
arrays).
And a few caveats that we may or may not need to address:
4)
> The effect of this rule is that in such an implementation, it is impossible
> to construct function items other than maps and arrays.
Perhaps unlikely, but not entirely inconceivable, the initial match selection
and global context item *may* contain function items. These are not constructed
*in* the implementation, but can be provided from external sources. We should
probably say what happens then.
5)
I don't think we should forbid using (compiled) packages that can operate on
function items. In fact, I don't think we can, because a package can be
compiled with another version of a processor and it may not be visible to the
package. I think it is too high a constraint to impose on package builders if
they want to market their packages.
6)
On the same token: don't we have a rule of some sort on packages that are build
with support for streaming or schema-awareness, used by a stylesheet build with
lesser support?
7)
As a result of (5) and (6), such packages *may* return function items. We
should say what happens if you try to match them (predicate pattern
dot-matches-all). Of course, you can't do anything useful with them, but you
can encounter them.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 30 October 2015 11:51:57 UTC