[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1043) Clean up context URL syntax
[ https://issues.oasis-open.org/browse/ODATA-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-1043: ------------------------------ Proposal: State in chapter 10 that one purpose of the context URL is to make responses "self-contained" and allow the client to e.g. construct navigation links for selected navigation properties. Otherwise no action, and no relaxation of the context URL patterns. was: 1) deprecate template variable {entity}, provide alternative patterns with {type-name} 2) make context URL optional for JSON with "minimal metadata" in cases where the request URL already identifies the relevant portion of the metadata document > Clean up context URL syntax > --------------------------- > > Key: ODATA-1043 > URL: https://issues.oasis-open.org/browse/ODATA-1043 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: Protocol > Affects Versions: V4.01_CSD01 > Environment: Proposed > Reporter: Ralf Handl > Fix For: V4.01_CSD02 > > > 1) Chapter 10 states: The context URL describes the content of the payload. It consists of the canonical metadata document URL and a fragment *identifying the relevant portion of the metadata document.* > This is somewhat violated by context urls using the template variable {entity} whose value is the canonical URL of an entity, including its key values - the key values aren't needed to identify the relevant portion of the metadata document, for this purpose the type is sufficient. > 2) Chapter 10 states: Request payloads generally do not require context URLs as the type of the payload can generally be determined from the request URL. > Can we have the same for response payloads? Most responses for requests to entity sets or singletons using canonical URLs would not need a context URL, same for navigation paths with a navigation property binding. Instances with a type derived from the declared type carry the @odata.type annotation, so even those don't need a context URL. Same for responses to actions/functions with an EntitySetPath, or action/function imports with a an EntitySet. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]