[OASIS Issue Tracker] Commented: (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=35154#action_35154 ] 

Ralf Handl commented on ODATA-546:
----------------------------------

I was (in fact, still am) pretty sure that we discussed that clients can easily number all requests within a batch, starting at 1 at the top, and not distinguishing between top-level requests and those nested in a change set. No need for hierarchical numbering, but clients are free to do so. They can also put in a guid and make each part globally unique. The current pattern for the content-id allows all of those numbering styles, even roman numerals.

Looking up already processed requests by a single content-id that is unique within a batch seems a bit easier than having to look it up with a top-level content-id that may be followed by a sub-content-id (dictionary of values versus dictionary of dictionaries and values), but both don't require magic.

Using two levels of content-ids for change sets would e.g. require extending the referencing syntax to 

  "$" content-id-of-outer-request [ "$/" content-id-of-inner-request ] "/" ...

With the current formulation we can stick to the one-level referencing scheme, and services can already experimentally allow 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