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] Updated: (ODATA-68) Describe representation of ReferenceTypes in responses


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

Michael Pizzo updated ODATA-68:
-------------------------------

    Proposal: 
1. Always represent references in responses as <metadata:entity-ref> or {"odata.ref":...}.
2. Allow passing entity references in {"odata.ref":...} and KEY(...) notation instead of entities to function and action parameters.
3. Remove edm:ReferenceType element and Ref(...)notation from CSDL. We don't need it anymore for passing parameters, and we want to give the client the choice of appending /$ref if it wants to save bandwidth. Returning only references and requiring additional requests for getting at the representations actually wastes bandwidth.
4. Keep KEY(...) notation in URL Conventions for use case E.
5. Rename odata.entityRef to odata.Ref throughout

For details see https://www.oasis-open.org/committees/download.php/48465/Representing%20Entity%20References%202013-03-05.doc 

  was:
1. Always represent references in responses as <metadata:entity-ref> or {"odata.entityRef":...}.
2. Allow passing entity references in {"odata.entityRef":...} and KEY(...) notation instead of entities to function and action parameters.
3. Remove edm:ReferenceType element and Ref(...)notation from CSDL. We don't need it anymore for passing parameters, and we want to give the client the choice of appending /$ref if it wants to save bandwidth. Returning only references and requiring additional requests for getting at the representations actually wastes bandwidth.
4. Keep KEY(...) notation in URL Conventions for use case E.

For details see https://www.oasis-open.org/committees/download.php/48465/Representing%20Entity%20References%202013-03-05.doc 


> Describe representation of ReferenceTypes in responses
> ------------------------------------------------------
>
>                 Key: ODATA-68
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-68
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format , OData CSDL, OData JSON Format
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> ReferenceType elements define a type derived from an entity type that can be used in function import return types. 
> Describe how they are serialized in Atom and JSON.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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