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-873) Define a default order for deep inserted entities in responses


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

Matthew Borges updated ODATA-873:
---------------------------------

    Proposal: 
Introduce a new contentID annotation that the client can specify in the nested entities in the request.  A server advertises support for the contentID instance annotation through the Capabilities.DeepInsertSupport annotation.  Clients can specify the contentID instance annotation in the nested entities in the request.  Services that support the contentID instance annotation MUST annotate the corresponding nested entities in the response when the return=representation preference is applied.
 
Instance annotation definition:
 
<Term Name=”contentID” Type=”Edm.String”>
    <Annotation Term="Core.Description" String=”A unique identifier for nested entities within a request."/> 
</Term>
 
Introduce a new capabilities annotation for deep inserts:
 
<Term Name="DeepInsertSupport" Type="Capabilities.DeepInsertSupportType" AppliesTo="EntityContainer"> 
  <Annotation Term="Core.Description" String=”Deep Insert Support for the service"/> 
</Term> 

<ComplexType Name="DeepInsertSupportType"> 
  <Property Name="Supported" Type="Edm.Boolean" DefaultValue="true"> 
    <Annotation Term="Core.Description" String="Service supports deep inserts" /> 
  </Property> 
  <Property Name="ContentIDSupported" Type="Edm.Boolean" DefaultValue=”true”> 
    <Annotation Term="Core.Description" String="Service supports accepting and returning nested entities annotated with the contentID instance annotation." /> 
  </Property> 
</ComplexType> 

  was:A response to a request (POST, PUT, or PATCH) that creates nested entities and that specified the Prefer header with a value of return=representation MUST contain the nested entities in the same order they appeared in the request unless explicitly overridden by an $orderby clause.


> Define a default order for deep inserted entities in responses
> --------------------------------------------------------------
>
>                 Key: ODATA-873
>                 URL: https://issues.oasis-open.org/browse/ODATA-873
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Matthew Borges
>            Priority: Minor
>             Fix For: V4.01_WD01
>
>
> There is no defined order for expanded nested entities in the response to a request (POST, PUT or PATCH) that creates new entities by a deep insert.



--
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]