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.
HR Directory Access Control Policy
{{#eclipseproject:technology.higgins}}
Notes
The above is a second (v2) attempt at modeling this use-case.
- A new diagramming style is used--it is more compact at representing the literal attributes of an Entity within a single rectangular box.
- The entire use case now fits on one diagram (just barely!)
- The new group higgins:subject sub-attribute is now being used
- A new selfInstanceOf higgins:subject sub-attribute is now being used
- See HOWL Update 1.1.104 for related changes to support this use case
The problem found last week remains. These two dimensions of "resource scoping" are orthogonal:
- what Attribute type(s) the Policy is talking about
- the set of Entities that the Policy is talking about
The problem is that ex:p[1-3]'s :read and :modify links all "point" to an Attribute type, but these links don't indicate what set of Entities we're talking about since one Attribute type may be used by N Entity classes.
See Also
- Access Control Use Cases - back to use cases