[OASIS Issue Tracker] (ODATA-1125) Define by-value/reference expectations for action/function payloads.

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

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

Michael Pizzo updated ODATA-1125:
---------------------------------

    Proposal: 
Expectations to be spelled out in Part 1: Protocol, documenting the by-value/by-reference expectations in Part 1: Protocol, with forward-reference to JSON Format for "bind syntax" / "entity references", to be detailed by authors, to be reviewed in document walk-through


  was:
1) Describe the encoding options in the CSDL documents.
2) In the protocol, describe the expectations for different uses when type is an entitytype.
3) cover these in the JSON format document.


> Define by-value/reference expectations for action/function payloads.
> --------------------------------------------------------------------
>
>                 Key: ODATA-1125
>                 URL: https://issues.oasis-open.org/browse/ODATA-1125
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: CSDL JSON , CSDL XML, Protocol
>    Affects Versions: V4.01_CSD03
>         Environment: Schema and protocol 
>            Reporter: George Ericson
>             Fix For: V4.01_CS01
>
>
> Descriptions of parameters and return types do not explain expectations for references to Entities.  
> The metamodel + vocabulary for CSDL allows three types of encodings:
> •	By-reference, represented as a string containing a URL that references the resource.
> •	By-reference, represented as an object containing a partial copy of the resource  that includes just the @odata.id meta property with a value that is a string containing a URL that references the resource.
> •	By-value, represented as an object containing a copy of the resource.
> For parameters and return-types, the question is which of these are expected in a payload.



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