[OASIS Issue Tracker] (ODATA-480) $batch: remove restriction "within the same change set " for Content-ID referencing

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

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

Ralf Handl updated ODATA-480:
-----------------------------

    Proposal: 
Remove restriction "within the same change set " for Content-ID referencing and allow referencing requests within the same batch that appear before the reference and thus already have been processed.

Add term BatchContentIdReferencingAcrossChangeSetsSupported to Capabilities vocabulary, similar to the existing term BatchContentIdReferencingInRequestBodiesSupported.

  was:Remove restriction "within the same change set " for Content-ID referencing and allow referencing requests within the same batch that appear before the reference and thus already have been processed.


> $batch: remove restriction "within the same change set " for Content-ID referencing
> -----------------------------------------------------------------------------------
>
>                 Key: ODATA-480
>                 URL: https://issues.oasis-open.org/browse/ODATA-480
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Batch Processing Format
>    Affects Versions: V4.0_CSD03
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: AdoptionBlocker
>             Fix For: V4.01_WD01
>
>
> Currently we restrict content-id referencing to entities created within the same change set. As we define that the content-id must be unique within a batch request, this is unnecessary.



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