[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-637) ATOM and JSON formats do not define representation of operation results
[ https://tools.oasis-open.org/issues/browse/ODATA-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37194#comment-37194 ] Michael Pizzo edited comment on ODATA-637 at 4/24/14 3:57 PM: -------------------------------------------------------------- Agree with the proposal. This is implied by [Protocol] where we specify the context url (which describes the results) for operation results to be the same as for properties, where the response represents a property, otherwise the primitive type, complex type, or collection of primitive/complex types. We should clarify this in the protocol documents and clarify that the body is the same for a primitive, complex, or collection of primitive/complex types as for a property of that primitive, complex, or collection of primitive/complex types (this is shown in examples, i.e., in section 11 of the JSON document) but should be spelled out explicitly. was (Author: mikep): Agree with the proposal. This is implied by [Protocol] where we specify the context url (which describes the results) for operation results to be the same as for properties, where the response represents a property, otherwise the primitive type, complex type, or collection of primitive/complex types. We should clarify this in the protocol documents and clarify that the body is the same for a primitive, complex, or collection of primitive/complex types as for a property of that primitive, complex, or collection of primitive/complex types. > 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: [Proposed] > Reporter: Evan Ireland > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]