-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_OS
-
Fix Version/s: V4.0_ERRATA01
-
Component/s: JSON Format
-
Labels:None
-
Environment:
[Applied]
-
Proposal:
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).