[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=63474#comment-63474 ] Michael Pizzo commented on ODATA-978: ------------------------------------- I like the simplicity of the default assumption that, if an operation is defined in metadata as bound to a type, it can be called on that type (it might return an error, but it's valid to call it). The question then becomes, if I have an operation that *isn't* always supported, how is it described? We know how it's advertised in payloads, but that payload needs to point back to metadata to describe parameters, return types, etc. > 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. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]