Section 5.3.3.2 says, under 2nd bullet point:

> The named functionsXP30 (representing the functions accessible using 
> function-available or function-lookupFO30) include all the functions 
> available in the static context, and may also include an additional 
> implementation-defined set of functions that are available dynamically 
> but not statically. 
Then a Note follows:

> This set therefore includes some functions that are not available for 
> dynamic calling using xsl:evaluate, for example stylesheet functions whose 
> visibility is private, and XSLT-defined functions such as current and key. 

I don't quite understand this. This section describes that all static functions are available dynamically, and then says it has them, but doesn't?

I'm sure this was discussed, but I can't remember the conclusion. When I read on under xsl:evaluate it clearly states that fn:current, fn:key are not available there.

But the section above suggests that they *are* available through function-lookup.

If I take this to the letter it seems that:

* function-available and function-lookup from xsl:evaluate should succeed on all functions, including the ones defined in the XSLT REC (fn:current and the like)
* but then *invoking* the found function should lead to a function-not-found error (or something), since xsl:evaluate does not disclose the implementation of that function?
* since function-available is defined in the XSLT REC, this would apply only to function-lookup (I think :S)

I remember that we deliberately limited the availability of functions defined in the spec (except functions in the map-namespace, I think). That limitation also applies to shadow attributes AVT's and xsl:use-when. I'm not saying we change that, but I find it hard to get to a proper understanding of how this is supposed to work.

My main issue is with "it includes all functions" and then "it doesn't include all functions". 

What further confuses is the next Note which says that XPath stipulates that whatever is available in the static context is available in the dynamic context. But it isn't, it seems.

I don't think the spec is broken here, but I do find it confusing how it is defined (and yes, I do remember we had several discussions on the subject, so my apologies for bringing it up again).