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-794) 14.4.2.2: Create Related Entities When Creating an Entity


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

Martin Zurmuehl updated ODATA-794:
----------------------------------

    Proposal: 
Do not partially restate the 201/204 rule from section 11.4.2.2 and shorten paragraph 3 to:

On success, the service MUST create all entities and relate them. If the service responds with 201 Created, the response MUST be expanded to at least the level that was present in the deep-insert request.

  was:
Do not partially restate the 201/204 rule from section 11.4.2 and shorten paragraph 3 to:

On success, the service MUST create all entities and relate them. If the service responds with 201 Created, the response MUST be expanded to at least the level that was present in the deep-insert request.


> 14.4.2.2: Create Related Entities When Creating an Entity
> ---------------------------------------------------------
>
>                 Key: ODATA-794
>                 URL: https://issues.oasis-open.org/browse/ODATA-794
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Martin Zurmuehl
>            Priority: Minor
>             Fix For: V4.0_ERRATA03
>
>
> Paragraph 3 states that
> On success, the service MUST create all entities and relate them. If the request included a return Prefer header with a value of return=representation and is applied by the service, the response MUST be expanded to at least the level that was present in the deep-insert request.
> This raised the question whether the service has to expand the response if no "return" preference is present.
> The intention was: if something is returned, it has to be expanded.



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