odata message

Subject: [OASIS Issue Tracker] (ODATA-1274) Clarify that a server MUST respond with content-id annotations and MUST include nested entity IDs

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: odata@lists.oasis-open.org
Date: Thu, 17 Jan 2019 17:01:00 +0000 (UTC)

Matthew Borges created ODATA-1274:
-------------------------------------

             Summary: Clarify that a server MUST respond with content-id annotations and MUST include nested entity IDs
                 Key: ODATA-1274
                 URL: https://issues.oasis-open.org/browse/ODATA-1274
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: Protocol
            Reporter: Matthew Borges


Currently in section 11.4.2.2 in the part 1 protocol document it says that the server SHOULD annotate entities in the response with the same content-id used in the request.Â This SHOULD needs to be a MUST if the server supports content-ids in deep insert/deep update requests.

Â

We also need to clarify that the response must include the entity ID for all entities returned in the response for a create or update if conventional entity IDs are not used.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)