22936 2013-08-13 10:35:42 +0000 [XSLT 3.0] Streamability : dynamic calls to context dependent functions 2014-05-15 14:00:19 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Working drafts PC All CLOSED FIXED P2 normal --- 1 mike mike public-qt-comments oldest_to_newest 91976 0 mike 2013-08-13 10:35:42 +0000 We say that a NamedFunctionRef is motionless. Similarly we have no special rules for function-lookup(). However, in both cases these constructs are not as innocent as they seem, because they capture the dynamic context at the point they are evaluated, and use that dynamic context later when the resulting function is called. For example: <xsl:variable name="saved-current" select="current#0"/> <xsl:for-each select="transaction"> <xsl:if test="value = $saved-current()/value"> ... </xsl:if> </xsl:for-each> is clearly not streamable. So: (a) A NamedFunctionRef should be free-ranging if the function is dependent on (relevant parts of?) the dynamic context (b) function-lookup() should always be free-ranging (because we have no way of knowing what it might do). (c) Partial function application could also be dangerous in the same way if we had any focus-dependent functions with two or more arguments. Fortunately we don't, though it seems a little odd to assume that. 93739 1 mike 2013-09-24 16:53:23 +0000 Noted that partial function application is currently already free-ranging - we're not sure why. We think this restriction should be removed. For the other cases we agree that the use of focius-dependent functions should be restricted. For function-lookup() we think this should be a dynamic error so that we don't ban all uses of function-lookup(), most of which will be perfectly innocent. 93748 2 mike 2013-09-24 22:00:10 +0000 I'm re-opening this in respect of the rules for function-lookup(). We suggested that this should return a dynamic error if (when streaming?) the function actually selected is a focus-dependent function. However, it's not clear what the actual circumstances for this error should be. In addition, raising such an error would require modification to the XPath specification of function-lookup(), which we should avoid if possible. 93807 3 mike 2013-09-25 15:38:37 +0000 We looked again at the function-lookup case and it starts to make more sense. Given $f := function-lookup("fn:lang", 1) followed by $f("en"), this is supposed to test the language of the node that was the context item at the time function-lookup was called. If this was a node in a streamed document, we can't safe a reference to it in the function closure. So we should define that in this case, in the closure we set the context item to "absent", which leads to a dynamic error if and when $f("en") is actually called. 93858 4 mike 2013-09-26 07:07:55 +0000 Spec updated (section id = #function-lookup)