| 3 | | - parentOrganization is not necessary as an attribute, you can express this by making the relation to itself bidirectional |
| 4 | | - There is no concept of a distinguished data and function authorization yet. Data authorization is about who can manipulate which resource. Function is about who can use what functions. Usually function authorisation comes first, then data. Is it correct that this model only talks about functional authorisation? |
| 5 | | - UserRole should be ParticipantRole |
| 6 | | - Not so sure about the need of having the concept of a participant. What is the usecase? |
| | 3 | * parentOrganization is not necessary as an attribute, you can express this by making the relation to itself bidirectional |
| | 4 | * There is no concept of a distinguished data and function authorization yet. Data authorization is about who can manipulate which resource. Function is about who can use what functions. Usually function authorisation comes first, then data. Is it correct that this model only talks about functional authorisation? |
| | 5 | * UserRole should be ParticipantRole |
| | 6 | * Not so sure about the need of having the concept of a participant. What is the usecase? |
