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-657) Clarity needed about if/when Control Information" must be specified in payload send from client to server


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

Evan Ireland updated ODATA-657:
-------------------------------

    Description: 
In regard to section 4.5 "Control Information", (apart from section 4.5.1 odata.context) the JSON format spec is written as if it only considers payload sent in responses from server to client.

However it is clear that it must in some cases apply to content sent in payload from client to server.

For example, presumably when an inheritance hierarchy is involved, a POST request needs to set odata.type.

On the other hand, a client might not know a valid entity-id to put in odata.id for a POST request (in particular where the server does not support canonical URLs).

  was:
In regard to section 4.5 "Control Information", the JSON format spec is written as if it only considers payload sent in responses from server to client.

However it is clear that it must in some cases apply to content sent in payload from client to server.

For example, presumably when an inheritance hierarchy is involved, a POST request probably needs to set odata.type.

On the other hand, a client might not know a valid entity-id to put in odata.id for a POST request.


> Clarity needed about if/when Control Information" must be specified in payload send from client to server
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-657
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-657
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_OS
>            Reporter: Evan Ireland
>             Fix For: V4.0_ERRATA01
>
>
> In regard to section 4.5 "Control Information", (apart from section 4.5.1 odata.context) the JSON format spec is written as if it only considers payload sent in responses from server to client.
> However it is clear that it must in some cases apply to content sent in payload from client to server.
> For example, presumably when an inheritance hierarchy is involved, a POST request needs to set odata.type.
> On the other hand, a client might not know a valid entity-id to put in odata.id for a POST request (in particular where the server does not support canonical URLs).



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