...
If a Resource represented a Person that this seems like a simple query. This is based on a model such as the one below:
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
However, Resources can be Groups, Organizations, and coffee mugs.
...
From the Authorization OSID viewpoint, the model now looks like:
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
If the service architect uses the Resource OSID and extracts all the Agents associated with a Resource, these Agents can be stashed into the authorization database for fast retrieval. Again, this creates the problem of how to synchronize changes in the Resource OSID with the Authorization OSID Provider. Perhaps it's too soon to design for performance.
Designing around with services is always a choosing with side of the line has ownership of a problem. If the problem of mapping Agents to Resources doesn't belong to the Authorization OSID, then maybe it's a problem for Resource (as what is implied by its definition).
Deeper into the Resource Can