[OASIS Issue Tracker] Updated: (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:all-tabpanel ]

Michael Pizzo updated ODATA-546:
--------------------------------


I am pretty sure this was an editorial mistake, as our examples and so forth all show simple integral values for content-id within changesets. Now, whether we want to (or can) fix it at this point may be another question.

Having Content-ID unique within the scope of the changeset does not preclude ODATA-480 from adding the ability to reference statements from other changesets; it just means that such references must be properly qualified with the changeset in which the change occurred. I would actually much rather do this than require content-ids to be unique across the batch and requiring the implementation to look within each changeset to find the right change id.

> 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