...
Better. However, the service architect feels she is kicking the can down the street. The can arrived at the Resource OSID.
Organizational Resources
Fun With Resources
A Resource is a generic dimension referenced throughout the OSIDs. In typical models, the entity that is managed is the same entity that is referenced for other purposes. For example, Starbucks has an inventory model for things it sells in its store. It manages coffee beans, city mugs, and muffins. Each of these items is managed to track unique information. Some of this information is expressed in the model such as the country or countries from which the coffee originates.
...
Perhaps this can be applied to the authorization dilemma.
The Authorization Perspective
The last iteration of createIssue() showed how an Authorization can be created using a Resource. However, the checking of the Authorization requires an Agent. The service architect has to get from Agent to Resource.
If a Resource represented a Person that this seems like a simple query. However, Resources can be Groups, Organizations, and coffee mugs.