I can see the point of a system/application role, i.e., user, operator,
system adminstrator, etc. I assume their role is qualified by the name of
the application?
I'm trying to think of another name for the organizational role ATTRIBUTE,
not the object class. I assume it would be considered poor form to give an
attribute
the same name as an object class. Yet the difference between a title and a role
is what matrix management is all about, so this is important. Is the ECMA role
name set in concrete? Could they call theirs applicationRole, perhaps?
How about functionalRole for the attribute name? It is only a little redundant.
Do you have any problem with the Agent attribute, or perhaps we should call it
organizationalAgent?
Bob