[ODATA-1419] Use of Core.ContentID by clients if service does not reference Core vocabulary - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Proposal:
Hide

Services advertising

@Capabilities.DeepInsertSupport:{ContentIDSupported:true}

MUST reference the Core vocabulary in their $metadata.

Clients MUST use either the namespace of the Core vocabulary 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 namespace of the Core vocabulary or the alias defined by the service's reference as the qualifier of ContentID .
Resolution:

Hide

https://github.com/oasis-tcs/odata-specs/pull/128

Show
https://github.com/oasis-tcs/odata-specs/pull/128

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

Are clients allowed or even required to use an alias defined in the service's $metadata?
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.