[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-177) Allow entities to be members of multiple entity sets
[ http://tools.oasis-open.org/issues/browse/ODATA-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-177: -------------------------------- Environment: (was: [Proposed]) Holding over to discuss at Zurich F2F. > Allow entities to be members of multiple entity sets > ---------------------------------------------------- > > Key: ODATA-177 > URL: http://tools.oasis-open.org/issues/browse/ODATA-177 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData Protocol v1.0 > Affects Versions: WD01 > Reporter: Ralf Handl > Fix For: WD01 > > > Section 3 currently states that an entity can be a member of at most one entity set. Given the ability to model entity type hierarchies this restriction seems rather unnatural: "Manager" is a specialization of "Employee", so it seems natural to have two entity sets "Managers" and "Employees", the former being a true subset of the latter, and a new "Manager" entity, POSTed to either set, would automatically appear in both. > Currently the only way to do that is to have an "Employees" entity set and a "Managers" function, with the drawback that the function is not advertised in the service document and thus not consumable in a hypermedia fashion. -- 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]