RE: annotation question - 14.2.2 Target

[Christof Sprenger <chrispre@microsoft.com>]

Thanks Mike.

 

I haven’t thought about the way the parameters are passed. That explains it clearly. Thanks.

 

Christof

 

From: Michael Pizzo <mikep@microsoft.com>
Sent: Sunday, January 24, 2021 15:12
To: Christof Sprenger <chrispre@microsoft.com>; Handl, Ralf <ralf.handl@sap.com>
Cc: odata@lists.oasis-open.org
Subject: RE: annotation question - 14.2.2 Target

 

Yes; action parameters (other than the binding parameter) are passed in the body of the request (like bound functions, the binding parameter determined by the resource path).  So, in order to be able to resolve the action without parsing the body, it must be unique based on binding parameter type.

 

Since function parameters are passed in the URL, they can be resolved without parsing the body, so we allow overloading based on all of the parameters.

 

From: Christof Sprenger <chrispre@microsoft.com>
Sent: Sunday, January 24, 2021 11:35 AM
To: Handl, Ralf <ralf.handl@sap.com>; Michael Pizzo <mikep@microsoft.com>
Cc: odata@lists.oasis-open.org
Subject: annotation question - 14.2.2 Target

 

Hello,

 

Hopefully a quick question. Section 14.2.2 Target

States the following.

 

·         qualified name of an action followed by parentheses containing the binding parameter type of a bound action overload to identify that bound overload, or by empty parentheses to identify the unbound overload

·         qualified name of a function followed by parentheses containing the comma-separated list of the parameter types of a bound or unbound function overload in the order of their definition in the function overload

 

And there seems to be a key difference in how the target path of an bound action is handled vs that of a bound function.
In a function’s target path it seems all parameter types are specified whereas for an action it is “only” the binding parameter type  

 

Is it true that

• actions allow overloads and they need to be uniquely resolvable by the binding parameter type
• functions allows overloads and they need to be uniquely resolvable by the combination of all parameters type’s

 

12.2 and 12.4 seem to say that but don’t make it very explicit that actions and functions are defined differently in that regard.

 

Christof