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

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35150#action_35150 ] 

Ralf Handl edited comment on ODATA-546 at 10/7/13 10:54 PM:
------------------------------------------------------------

I don't consider this an editorial mistake, on the contrary: it is a necessary precondition for ODATA-480, where we want to add content-id referencing across change sets.

      was (Author: ralfhandl):
    I don't consider this as an editorial mistake, on the contrary: it is a necessary precondition for ODATA-480, where we want to add content-id referencing across change sets.
  
> Content-Id MUST be unique within Changeset, not within batch
> ------------------------------------------------------------
>
>                 Key: ODATA-546
>                 URL: http://tools.oasis-open.org/issues/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.0_ERRATA01
>
>
> 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 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