[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1419) Use of Core.ContentID by clients if service does not reference Core vocabulary
Ralf Handl created ODATA-1419: --------------------------------- Summary: Use of Core.ContentID by clients if service does not reference Core vocabulary Key: ODATA-1419 URL: https://issues.oasis-open.org/browse/ODATA-1419 Project: OASIS Open Data Protocol (OData) TC Issue Type: Improvement Components: Protocol Affects Versions: V4.01_OS Reporter: Ralf Handl Fix For: V4.01_ERRATA01 Section [11.4.2.2 Create Related Entities When Creating an Entityhttps://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_CreateRelatedEntitiesWhenCreatinganE] states {quote} Clients MAY associate an id with individual nested entities in the request by using the Core.ContentID term defined in [OData-VocCore]. {quote} # 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}}? -- This message was sent by Atlassian Jira (v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]