[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (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:comment-tabpanel&focusedCommentId=32008#action_32008 ]
Ralf Handl edited comment on ODATA-177 at 12/20/12 12:11 PM:
-------------------------------------------------------------
On second thought I'd prefer to have "MyCustomers", "TopCustomers", "PreferredCustomers", "DelinquentCustomers", "NewCustomers" as first-class citizens directly in the service document, and entity sets are the natural construct for that.
We'd also accept POST on MyCustomers, which will automatically link the customer to the authenticated user.
Servers not being able to accept POST on multiple sets can use the Capabilities vocabulary and annotate exactly one entity set with an InsertRestriction that tells clients not to POST here, or simply only expose models with one entity set per type.
There's no need to restrict all servers.
was (Author: ralfhandl):
On second thought I'd prefer to have "MyCustomers", "TopCustomers", "PreferredCustomers", "DelinquentCustomers", "NewCustomers" as first-class citizens directly in the service document.
> 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
> Environment: [Proposed]
> 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]