Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "HOWL Update 1.1.103"
(→New "managedBy" property) |
(→Revised Access Control Policy representation) |
||
Line 7: | Line 7: | ||
==Access Control Related Changes == | ==Access Control Related Changes == | ||
===Revised Access Control Policy representation=== | ===Revised Access Control Policy representation=== | ||
+ | |||
+ | * We have below two approaches to consider. | ||
+ | * The question is what are the criteria to use to determine which is better | ||
+ | * We decided on the 7.3.2008 call to apply some use cases to each to see which, when these case are modeled, "look better" (less complex to manage) | ||
+ | * However, in parallel I (Paul) have been thinking that the paramount consideration is to minimize the total number of Policy Entities in a Context. The intuition is simply that having fewer of these Entities will be easier to managed all around. | ||
+ | |||
Original approach (circa 1.1.102): | Original approach (circa 1.1.102): | ||
Revision as of 15:57, 3 July 2008
{{#eclipseproject:technology.higgins}}
Contents
Version 1.1.103
- This page describes changes made from version HOWL Update 1.1.102
Access Control Related Changes
Revised Access Control Policy representation
- We have below two approaches to consider.
- The question is what are the criteria to use to determine which is better
- We decided on the 7.3.2008 call to apply some use cases to each to see which, when these case are modeled, "look better" (less complex to manage)
- However, in parallel I (Paul) have been thinking that the paramount consideration is to minimize the total number of Policy Entities in a Context. The intuition is simply that having fewer of these Entities will be easier to managed all around.
Original approach (circa 1.1.102):
Revised approach used in 1.1.103:
- Delete the Operation class (and all subclasses)
- Change higgins:operation into being an abstract super-property whose range is the protected resource.
- Added higgins:read, higgins:add, higgins:modify, and higgins:delete properties (all sub-properties of the revised higgins:operation super-property).
New "managedBy" property
There is currently a problem with the access control constructs in 1.1.102. There is no way to know what Entity is permitted to manage (modify, delete, etc.) a given PolicyEntity. The proposal here is to add a "managedBy" property:
- Added "managedBy" property (domain = Policy, range = Agent who is permitted to manage this Policy Entity)
- Need to discuss this with the Higgins team to see if this is a good way to handle this.
Misc Changes
Simplification:
- instead of including an explicit BlankEntity class in the data model, we simply say that Entities have at most one EntityId, not exactly one. The BlankEntity class has been eliminated.