DMN13 — Functions resolution

FEEL supports function invocation described in rule 40, for example f(a, b, c)

The specification doesn't describe in details how the function is resolved (name of function is bound to the function definition). For example:

• what are the DMN / FEEL artifacts that the call can be bound to (e.g. DMN invocables visible in context)
• how are the name clashes resolved (e.g. both a BKM and a buil-in function have the same signature)
• how are the binding candidates built (e.g. apply all combinations of implicit conversions) and selected (e.g. exact match takes precedence)

Specify how functions are found in scope and argument types are checked

See attached word doc