[OASIS Issue Tracker] (ODATA-546) Content-Id MUST be unique within Changeset, not within batch

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

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

Ralf Handl updated ODATA-546:
-----------------------------

    Component/s: OData Protocol
                     (was: OData Batch Processing Format)

> Content-Id MUST be unique within Changeset, not within batch
> ------------------------------------------------------------
>
>                 Key: ODATA-546
>                 URL: https://issues.oasis-open.org/browse/ODATA-546
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_CSD03
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> According to section 11.7.3, Changesets in [Protocol]:
> " In addition each request within a change set MUST specify a Content-ID header with a value unique within the batch request"
> "batch request" in this sentence is actually an editorial mistake; each changeset is atomic, and the content-id unique within the scope of the changeset.



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