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-1125) Define by-value/reference expectations for action/function payloads.


George Ericson created ODATA-1125:
-------------------------------------

             Summary: 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
         Environment: Schema and protocol 
            Reporter: George Ericson


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)


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