[OASIS Issue Tracker] Updated: (ODATA-451) Provide section that clearly indicates what system query options are allowed on the various combinations of URL type and HTTP method (public comment c201306e00012)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Ralf Handl updated ODATA-451:
-----------------------------

    Proposal: 
When inserting an entity we already specified that the service MUST return at least the expansion level that was present in the (deep) insert request.

As clients should have a complete representation of how the service interpreted their request, the response MUST NOT be projected by the service (this rule is new).

Consequently $expand and $select are not allowed on insert requests, and none of the other system query options make sense either.

Similar argument for update requests: no system query options on update requests.

Delete request don't return data, so no question here.

Summary: CUD operations don't allow system query options.

The rationale for actions is different: there's no predefined semantics for actions, so all system query options applicable to the return type are allowed. For functions they are allowed anyway.

  was:
When inserting an entity we already specified that the service MUST return at least the expansion level that was present in the (deep) insert request.

As clients should have a complete representation of how the service interpreted their request, the response MUST NOT be projected by the service (this rule is new).

Consequently $expand and $select are not allowed on insert requests, and none of the other system query options make sense either.

Similar argument for update requests: no system query options on update requests.

The rationale for actions is different: there's no predefined semantics for actions, so $expand and $select are allowed when invoking an action that returns single or multiple instances of structural types.


> Provide section that clearly indicates what system query options are allowed on the various combinations of URL type and HTTP method (public comment c201306e00012)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-451
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-451
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions 
>    Affects Versions: V4.0_CSD01
>            Reporter: Stefan Drees
>            Priority: Minor
>             Fix For: V4.0_CSD02
>
>
> We received the public Comment #20130600012 on 2013-06-14 with title "feedback/discussion now that public comment period is over".
> Text was: 
> """
> Where can I send comments about or have discussion regarding the OData v4 spec now that the public comment period is over?
> I would like to know if the $select and $expand system query options are allowed on insert entity requests to limit or expand the data that is returned (when it is requested via a PREFER header that data be returned).  A section that clearly indicates what system query options are allowed on the various combinations of URL type and HTTP method would be helpful (unless it exists already and I just missed it).
> """

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