[OASIS Issue Tracker] (ODATA-637) ATOM and JSON formats do not define representation of operation results

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

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

Michael Pizzo updated ODATA-637:
--------------------------------

    Environment: [Applied]  (was: [Proposed])

> ATOM and JSON formats do not define representation of operation results
> -----------------------------------------------------------------------
>
>                 Key: ODATA-637
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-637
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format , OData JSON Format
>    Affects Versions: V4.0_OS
>         Environment: [Applied]
>            Reporter: Evan Ireland
>            Assignee: Michael Pizzo
>             Fix For: V4.0_ERRATA01
>
>
> 4.0 spec for ATOM and JSON formats doesn't define how values are represented when they are returned from operations (actions or functions).
> For example, the following JSON format sections would appear to be only applicable only to a property within an entity or complex type instance.
> 7.1 Primitive Value
> 7.2 Complex Value
> 7.3 Collection of Primitive Values.
> 7.4 Collection of Complex Values
> 11 Individual Property
> If a value of one of the above types is returned by an action or function, we need to define how it is represented.



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