-
Type: Sub-task
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.01_CS01
-
Fix Version/s: V4.01_CS02
-
Component/s: JSON Format, Protocol
-
Labels:None
-
Proposal:
-
Resolution:
With https://issues.oasis-open.org/browse/ODATA-1066 we added the possibility to mark parameters as optional.
We also added text to Part 1: Protocol describing how function overload resolution works in combination with optional parameters.
Two aspects of optional parameters just came up during implementation that I can’t find in the document or the issue:
- Are services free to interpret the absence of a parameter as best suits the purpose of the function?
- Can actions also have optional parameters?