[OASIS Issue Tracker] (ODATA-656) Requesting clarity on payload ordering constraints for clients

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

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

Michael Pizzo updated ODATA-656:
--------------------------------

    Proposal: 
Clarify in Section 4.4 Payload Ordering Constraints that clients may use the odata.streaming=true format parameter to specify that the contents of the payload supplied by the client follow the ordering constraints. In the absence of such a type parameter the service must assume that the properties of json objects are unordered.


  was:
Explicitly state that clients need not support payload ordering constraints for request payload from client to server.



> Requesting clarity on payload ordering constraints for clients
> --------------------------------------------------------------
>
>                 Key: ODATA-656
>                 URL: https://issues.oasis-open.org/browse/ODATA-656
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_OS
>         Environment: Proposed
>            Reporter: Evan Ireland
>            Priority: Minor
>              Labels: Clarification
>             Fix For: V4.01_WD01, V4.0_ERRATA03
>
>
> Section 4.4 Payload Ordering Constraints would appear to apply only to servers/services.
> If there was any intent that it also (optionally) apply to request payload (from client to server), or even if not, we should be clear about this.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)