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 14239 - [XQuery30] Function signatures vs. "Function signatures" static context component
Summary: [XQuery30] Function signatures vs. "Function signatures" static context compo...
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3.0 (show other bugs)
Version: Working drafts
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-22 09:34 UTC by Ghislain Fourny
Modified: 2011-10-31 21:56 UTC (History)
0 users

See Also:

Attachments

Description Ghislain Fourny 2011-09-22 09:34:21 UTC 
The terminology "function signatures" seems to be used with two different meanings:

1. The function signature of any function (inline or not), for example in 2.5.5.7 Function Test, as well as in the definition of function items in the data model.

2. The function signatures component of the static context, which does not include the function signatures of (dynamically-produced) inline functions.
Comment 1 Jonathan Robie 2011-10-12 20:18:40 UTC 
(In reply to comment #0)
> The terminology "function signatures" seems to be used with two different
> meanings:
> 
> 1. The function signature of any function (inline or not), for example in
> 2.5.5.7 Function Test, as well as in the definition of function items in the
> data model.
> 
> 2. The function signatures component of the static context, which does not
> include the function signatures of (dynamically-produced) inline functions.

We've proposed renaming the static context component "statically known function items". Would that resolve the problem for you?
Comment 2 Ghislain Fourny 2011-10-31 21:56:44 UTC 
Yes it does, thanks!