[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-276) Fix issues with entity references and rationalize with $links
[ http://tools.oasis-open.org/issues/browse/ODATA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Drees updated ODATA-276: ------------------------------- Resolution: https://www.oasis-open.org/committees/download.php/48526/odata-core-v4.0-wd01-part1-protocol-2013-03-12.doc https://www.oasis-open.org/committees/download.php/48527/odata-core-v4.0-wd01-part2-url-conventions-2013-03-12.doc https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules-v4.0-wd01.txt?rev=211 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=211 https://www.oasis-open.org/committees/download.php/48524/odata-atom-format-v4.0-wd01-2013-12-05-RH.doc https://www.oasis-open.org/committees/download.php/48588/odata-atom-format-v4.0-wd01-2013-03-19.doc https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=208 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=219 https://www.oasis-open.org/committees/download.php/48525/odata-json-format-v4.0-wd01-2013-03-12-RH.doc Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-276 was: https://www.oasis-open.org/committees/download.php/48526/odata-core-v4.0-wd01-part1-protocol-2013-03-12.doc https://www.oasis-open.org/committees/download.php/48527/odata-core-v4.0-wd01-part2-url-conventions-2013-03-12.doc https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules-v4.0-wd01.txt?rev=211 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=211 https://www.oasis-open.org/committees/download.php/48524/odata-atom-format-v4.0-wd01-2013-12-05-RH.doc https://www.oasis-open.org/committees/download.php/48588/odata-atom-format-v4.0-wd01-2013-03-19.doc https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=208 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=219 https://www.oasis-open.org/committees/download.php/48525/odata-json-format-v4.0-wd01-2013-03-12-RH.doc > Fix issues with entity references and rationalize with $links > ------------------------------------------------------------- > > Key: ODATA-276 > URL: http://tools.oasis-open.org/issues/browse/ODATA-276 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData ABNF Construction Rules, OData ATOM Format , OData JSON Format, OData Protocol , OData URL Conventions > Affects Versions: V4.0_WD01 > Environment: [Proposed] > Reporter: Michael Pizzo > Assignee: Ralf Handl > Fix For: V4.0_WD01 > > > In adding Entity References in OData-199, we introduced a few issues. > First, we said that clients could return just references, in place of the actual entity, by putting $ref in the select clause. We then said it wasn't valid to include navigation properties with $ref in the select, but not other non-navigation properties. This is a bit arbitrary; the only data that needs to be returned an object is its references to other object(s); if links from those related objects are also of interest, they can be requested and retrieved as related links of those objects. Also, it's a bit strange to use $select for something that changes the type of object returned, from an entity to an entity reference; a path expression would be more suitable for this. > Second, adding a path representation for relationships gives us a way to rationalize/generalize the special semantics around $links that we have today. We can use the $ref path expression to refer to the links that are added/deleted/enumerated, and provide a consistent representation of an entity reference in the payload (rather than have entity references for referring to entities in one case, and a separate URI construct for referring to entities in another case). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]