OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Michael Pizzo commented on ODATA-978:

Today, by defining a bound action/function you are implying that you can construct the url for invoking the action or function, although the client may get an error if the bound instance is not in a valid state.

If the intention is to call out cases where an instance is in a state where it cannot be invoked, perhaps an instance annotation to call out that the action/function is not supported on a particular instance.

Perhaps we can use the existing syntax but specify a null value:

"#Model.RemainingVacation": null

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]