- From: Robie, Jonathan <jonathan.robie@emc.com>
- Date: Tue, 15 Mar 2016 15:03:08 +0000
- To: Michael Dyck <jmdyck@ibiblio.org>, "public-xsl-query@w3.org" <public-xsl-query@w3.org>
I agree with these comments, and committed a new version that attempts to address them. Jonathan ________________________________________ From: Michael Dyck [jmdyck@ibiblio.org] Sent: Friday, March 11, 2016 2:11 PM To: public-xsl-query@w3.org Subject: Re: Changes to 3.1.5.1 Evaluating Static and Dynamic Function Calls On 16-03-11 12:32 PM, Robie, Jonathan wrote: > I have made a few changes to the text Michael Dyck committed for 3.1.5.1 > Evaluating Static and Dynamic Function Calls: > > https://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xquery-31-diff.html#id-eval-function-call Where 5.a says: then the new function's implementation is associated with a static context and a dynamic context in one of two ways, depending on the function implementation It doesn't actually depend on the function's implementation, but rather on whether we've already associated contexts with that implementation. Within 5.b.i.A's <phrase diff="add" at="bug29277"> The static context for this evaluation ... </phrase> there are two embedded diff-phrases, which doesn't make much sense. The inner markup should be eliminated. 5.b.ii says: An API used to invoke external functions must state whether the static and dynamic contexts are available to a function that is invoked. The "whether" is odd, because we've just said that they *are* made available. And: The F&O specification states how the static and dynamic contexts are available to a function that is invoked No, it doesn't really say "how the contexts are available", rather it specifies how each function *depends on* (or uses) the info in those contexts (if at all). And the XPath-only sentence: A host language must state whether and how the static and dynamic contexts are available to a function that is invoked. As above, the "whether" is odd. Maybe "available to" should be "used by". But really, the host language spec would only have that responsibility for functions that *it* adds to the mix. E.g., the XSLT spec doesn't have to state how F+O functions use context info. --- BTW, I noticed that the new Note ("XQuery 3.1 is a host language...") isn't getting diff-highlighted, even though it has diff="add" in the source. -Michael
Received on Tuesday, 15 March 2016 15:03:52 UTC