[OASIS Issue Tracker] Created: (ODATA-539) Delta response encoding is unnecessarily verbose and change type is missing when odata.metadata=none

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

Delta response encoding is unnecessarily verbose and change type is missing when odata.metadata=none
----------------------------------------------------------------------------------------------------

                 Key: ODATA-539
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-539
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData ATOM Format , OData JSON Format, OData Protocol 
    Affects Versions: V4.0_WD01
            Reporter: Evan Ireland
             Fix For: V4.0_WD01


For a number of reasons, the encoding of delta responses is unnecessarily verbose, which will result in excessive network and CPU utilization, particularly for offline-enabled mobile devices.

(1) To distinguish between changed entity, deleted entity, changed link, or deleted link requires use of the Context URL which, as described in ODATA-538, can be unnecessarily verbose. It is not possible.

(2) The "id" in deleted entities and the "source"/"target" in added/deleted links is not required to use a relative URL, and clients cannot control whether the server will or will not use relative URLs.

Additionally, if odata.metadata=none, clients may be unable to decode delta responses, since odata.context may be omitted in that case. Interestingly, odata.deltaLink cannot be omitted from the response, although a delta response without change type for each of the included changes would be useless to a client.


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