[OASIS Issue Tracker] (ODATA-978) New annotation for availability/advertisement of bound actions/functions

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/ODATA-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-978:
-----------------------------

    Description: 
Actions and functions that are not available on all instances can be advertised in responses, see http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752309.

What's missing is an indicator in $metadata which actions/functions will fall into this category because absence of action/function advertisement in a response payload is ambiguous, clients can't decide whether the service does not advertise a certain action/function at all, or whether the action/function is not applicable on the received instances.

  was:
Actions and functions that are not available on all instances can be advertised in responses, see http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752309.

What's missing is an indicator in $metadata which actions/functions will fall into this category.


The action/function advertisement is the pointer to metadata: the advertisement has the form of a URL fragment that identifies the action/function by its qualified name, and optionally by an additional list of non-binding parameter names to identify a specific overload

{
  "@odata.context": "http://host/service/$metadata#Employees/$entity";,
  "#Model.RemainingVacation": {},
  ...
}

or 

{
  "@odata.context": "http://host/service/$metadata#Employees/$entity";,
  "#Model.RemainingVacation(Year)": {},
  ...
}


> New annotation for availability/advertisement of bound actions/functions
> ------------------------------------------------------------------------
>
>                 Key: ODATA-978
>                 URL: https://issues.oasis-open.org/browse/ODATA-978
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Vocabularies
>    Affects Versions: V4.0_ERRATA03
>         Environment: Annotations, Proposed
>            Reporter: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> Actions and functions that are not available on all instances can be advertised in responses, see http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752309.
> What's missing is an indicator in $metadata which actions/functions will fall into this category because absence of action/function advertisement in a response payload is ambiguous, clients can't decide whether the service does not advertise a certain action/function at all, or whether the action/function is not applicable on the received instances.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)