Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-697

Define how/where $<content-id> can be used within a changeset

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.0_OS
    • Fix Version/s: V4.0_ERRATA01
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      [Applied]

    • Proposal:
      Hide

      Rather than introduce the term "alias" here (which may be confused with other aliases) just say that this defines a resource path for the new entity that can be used anywhere other resource paths are valid.

      Also, add "root" to the list of top level resources that the name doesn't conflict with.

      Show
      Rather than introduce the term "alias" here (which may be confused with other aliases) just say that this defines a resource path for the new entity that can be used anywhere other resource paths are valid. Also, add "root" to the list of top level resources that the name doesn't conflict with.

      Description

      Currently, in 11.7.3.1, 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.

        Attachments

          Activity

            People

            • Assignee:
              mikep Michael Pizzo
              Reporter:
              mikep Michael Pizzo
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: