Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "HR Directory Access Control Policy"

(Notes)
Line 7: Line 7:
  
 
== Notes ==
 
== Notes ==
# Access Control Policy Entity's higgins:operation sub-Attributes point to the ''models'' of the Entity instances, not concrete Entity instances
+
# Access Control Policy Entity's higgins:operation sub-Attributes (the green arcs above) refer to the ''models'' of the Entity instances, not concrete Entity instances. At first glance it would appear that we'd need to implement Jim's new "expressing Entity models by using other Entities" approach. But since there is no need to dereference the green arcs this no actually the case.
 
+
# On problem I [Paul] see with the above is that since Attributes are first class objects in our data model, they may be used by more than one class of Entity. But this is most often not the intended semantic. We want to be able to define which type of Attribute on which class (or its subclass) of Entity (or possibly its sub-part Entity).
  
 
==See Also==
 
==See Also==
 
* [[Access Control Use Cases]] - back to use cases
 
* [[Access Control Use Cases]] - back to use cases

Revision as of 10:23, 9 July 2008

{{#eclipseproject:technology.higgins}}

Higgins logo 76Wx100H.jpg

Hr-dept-use-case-p1.png

Hr-dept-use-case-p2.png

Notes

  1. Access Control Policy Entity's higgins:operation sub-Attributes (the green arcs above) refer to the models of the Entity instances, not concrete Entity instances. At first glance it would appear that we'd need to implement Jim's new "expressing Entity models by using other Entities" approach. But since there is no need to dereference the green arcs this no actually the case.
  2. On problem I [Paul] see with the above is that since Attributes are first class objects in our data model, they may be used by more than one class of Entity. But this is most often not the intended semantic. We want to be able to define which type of Attribute on which class (or its subclass) of Entity (or possibly its sub-part Entity).

See Also

Back to the top