[OASIS Issue Tracker] Created: (ODATA-547) Clarify that the standard resources $id, $entity, $batch etc. win over content-id referencing

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

Clarify that the standard resources $id, $entity, $batch etc. win over content-id referencing
---------------------------------------------------------------------------------------------

                 Key: ODATA-547
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-547
             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
            Priority: Minor
             Fix For: V4.0_CS02


Content-id referencing uses the magic character $ followed by a token to refer back to a request that specifies that token in its content-id header.

Using one of the standard resource names without a $ prefix as a content-id could lead to confusion as URLs relative to the batch request URL are also relative to the service root and the relative URL for the standard resources thus starts with a $:

--batch_36522ad7-fc75-4b56-8c71-56071383e77b
Content-Type: application/http 
Content-Transfer-Encoding:binary
Content-ID: batch

POST Customers HTTP/1.1

<new customer body>


--batch_36522ad7-fc75-4b56-8c71-56071383e77b
Content-Type: application/http 
Content-Transfer-Encoding:binary
Content-ID: nested-batch

POST $batch HTTP/1.1 
Content-Type: multipart/mixed;boundary=nested_batch_77162fcd-b8da-41ac-a9f8-9357efbbd 
Content-Length: ###       

--nested_batch_77162fcd-b8da-41ac-a9f8-9357efbbd 

<content of nested batch