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

Use of Core.ContentID by clients if service does not reference Core vocabulary

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: V4.01_OS
    • Fix Version/s: V4.01_ERRATA01
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      Proposed

    • Proposal:
      Hide

      Services advertising 

      @Capabilities.DeepInsertSupport:{ContentIDSupported:true}

      MUST reference the Core vocabulary in their $metadata.

      Clients MUST use either the Core namespace or the alias defined by the service's reference as the qualifier of ContentID.

      Show
      Services advertising  @Capabilities.DeepInsertSupport:{ContentIDSupported: true } MUST reference the Core vocabulary in their $metadata. Clients MUST use either the Core namespace or the alias defined by the service's reference as the qualifier of ContentID .

      Description

      Section 11.4.2.2 Create Related Entities When Creating an Entity states

      Clients MAY associate an id with individual nested entities in the request by using the Core.ContentID term defined in [OData-VocCore].

      1. Are clients allowed or even required to use an alias defined in the service's $metadata?
      2. Are clients allowed to use this annotation if the service does not reference the Core vocabulary? Should they then use the fully qualified term name Org.OData.Core.V1.ContentID? Or are services required to reference the Core vocabulary when they advertise this feature via Capabilities.DeepInsertSupport?

      Note-to-self: if we had placed the term ContentID in the Capabilities vocabulary, the problem wouldn't exist.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              handl Ralf Handl
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: