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 30403 - [XSLT30] closure definition in 4.4 seems ambiguous as written
Summary: [XSLT30] closure definition in 4.4 seems ambiguous as written
Status: NEW
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Recommendation
Hardware: PC Windows NT
: P2 normal
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: 2019-02-28 21:39 UTC by Abel Braaksma
Modified: 2019-02-28 21:41 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2019-02-28 21:39:15 UTC
In section 4.4, some prose is devoted to explaining to effect of capturing the closure, notably:

> [...] are defined to retain the XPath static and dynamic context at the point 
> of invocation as part of the closure of the resulting function item, and to 
> use this preserved context when a dynamic function call is subsequently made 
> using the function item. 

This text says "at the point of invocation". But it is not an invocation, that occurs later, which is explained in the second part of the sentence.

What I think it means to say: "at the point where the function item is declared (for doc#x or doc(?)) or looked up (for function-lookup)"

I don't think the intend of this text is unclear, but I needed to read it several times to understand that "invocation" does *not* mean invocation of the function in question.
Comment 1 Abel Braaksma 2019-02-28 21:41:56 UTC
The same text exists at the bottom of section 5.3.4 with the same word choice.