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-1018) Allow $expand, $select and $filter with modifying requests that return a collection in combination with return=representation to specify the response shape


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

Michael Pizzo updated ODATA-1018:
---------------------------------

    Proposal: 
Extend allowing use of $select, $filter and $expand to data modification requests that return a collection
1) if $expand/$select/$filter are present, implies return=representation
2) if $expand/$select/$filter are present and return=minimal is specified, then service SHOULD NOT return a result and MUST include preference-applied if they DON'T return a result
3) if it returns a result, $expand and $filter MUST be applied if specified and MUST include at least the $selected columns
4) the service MUST NOT fail the request due to the $expand/$select/$filter; if the service cannot return a result with the appropriate $expand, $filter and $select it MUST return No Content



  was:
Extend allowing use of $select, $filter and $expand to data modification requests that return a collection
1) if $expand/$select/$filter are present, implies return=representation
2) if $expand/$select/$filter are present and return=minimal, service MUST include preference-applied if they DON'T return a result
3) if it returns a result, $expand and $filter MUST be applied if specified and MUST include at least the $selected columns
4) the service MUST NOT fail the request due to the $expand/$select/$filter; if the service cannot return a result with the appropriate $expand, $filter and $select it MUST return No Content




> Allow $expand, $select and $filter with modifying requests that return a collection in combination with return=representation to specify the response shape
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-1018
>                 URL: https://issues.oasis-open.org/browse/ODATA-1018
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: Protocol, URL Conventions
>    Affects Versions: V4.0_OS
>         Environment: Proposed
>            Reporter: Hubert Heijkers
>            Assignee: Michael Pizzo
>              Labels: Usability
>             Fix For: V4.01_CSD02
>
>
> This is a clone of ODATA-614 in which we allowed to use $expand and $select already for single entities.
> While discussing this in our meeting on December 1st, we concluded that there is no reason to not allow this for collections either.
> The proposed solution is pretty much just allowing what we already allowed for requests returning a single resource to collections as well. Re-reading the proposal though I wonder if it is obvious that returning 'No Content' implies it couldn't return what was requested but still executed the request. I'm not proposing to fail the request just not sure if the response is in line with what one expects/what a GET request would do if it were asked the same???



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