OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (ODATA-697) Define how/where $<content-id> can be used within a changeset

Michael Pizzo created ODATA-697:

             Summary: Define how/where $<content-id> can be used within a changeset
                 Key: ODATA-697
                 URL: https://tools.oasis-open.org/issues/browse/ODATA-697
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Protocol 
    Affects Versions: V4.0_OS
         Environment: [Proposed]
            Reporter: Michael Pizzo
            Priority: Minor
             Fix For: V4.0_ERRATA01

Currently, in, Referencing Requests in a ChangeSet, we say:
"New entities created by an Insert request within a change set can be referenced by subsequent requests within the same change set by referring to the value of the Content-ID header prefixed with a $ character. When used in this way, $<Content-ID> acts as the resource path that an alias for the URI that identifies the new entity unless $<Content-ID> is identical to the name of a top-level system resource ($batch, $crossjoin, $all, $entity, $id, $metadata, or other system resources defined according to the OData-Version of the protocol specified in the request)."

However, we don't say where/how this "alias" can be used, and it's not really described in the abnf.

Also, for completeness we should reference $root as one of the top-level system resources that the name can't conflict with.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]