-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: V4.01_OS
-
Fix Version/s: V4.01_ERRATA01
-
Component/s: Protocol
-
Labels:None
-
Proposal:
-
Resolution:
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].
- 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.