This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24553 - Built-in template rule for maps
Summary: Built-in template rule for maps
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows NT
: P2 trivial
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 00:47 UTC by Abel Braaksma
Modified: 2014-02-24 14:55 UTC (History)
1 user (show)

See Also:


Attachments

Description Abel Braaksma 2014-02-06 00:47:08 UTC
Currently, there is no specific mention of what happens with maps if the built-in template rules kick in (see 6.8.1 Built-in Templates: Text-only Copy, http://www.w3.org/TR/xslt-30/#built-in-templates-text-only-copy, first paragraph under the Note).

We already mention function items, which do nothing, but one might expect that the value of a map item is to be returned. My suggestion is to make this explicit (even though the rules do already cover this).
Comment 1 C. M. Sperberg-McQueen 2014-02-13 09:58:19 UTC
We discussed this in Prague.  ABr clarified that the current rules for function items do clearly have the consequence in text-only copy mode that nothing happens / the empty string is returned.  Since some users will expect a different behavior, however, it's worth saying explicitly that for maps nothing happens. No substantive change is now being requested (even by WG members who would have preferred that the built-in text-only copy templates return the text values of maps).  So this is essentially an editorial change to the exposition in the text.
Comment 2 Michael Kay 2014-02-21 14:13:06 UTC
Added clarification: whereever we say that the default rule for functions is to do nothing, we now say "for functions (including maps)...".