iSHARE's three primary use cases are supported by seven secondary use cases. These include:
- Processes related to registration;
- Processes that recur in primary use cases.
Processes related to registration
These four secondary use cases need to be completed before any, or specific, primary use cases can be initiated.
Any partyparty needs to:
| Panel |
|---|
1a. Register adherence/certification at Scheme Owner and later needs to be able to: 1b. Modify adherence/certification at Scheme Owner |
Before initiating Human to Machine use cases, the Service Consumer needs to:
| Panel |
|---|
2a. Create Service Consumer and/or Human Service Consumer identity at Identity Provider
later, a Service Consumer needs to be able to: 2b. Modify Service Consumer and/or Human Service Consumer identity at Identity Provider |
When delegating rights, the Entitled Party needs to:
| Panel |
|---|
3a. Register delegation at Service Provider, Entitled Party, or Authorization or Authorization Registry
later, an Entitled Party needs to be able to: 3b. Modify delegation at Service Provider, Entitled Party, or Authorization or Authorization Registry |
When authorizing something or -one, the Service Consumer needs to:
| Panel |
|---|
4a. Register authorization at Service Provider, Entitled Party, or Authorization or Authorization Registry
later, a Service Consumer needs to be able to: 4b. Modify authorization at Service Provider, Entitled Party, or Authorization or Authorization Registry |
Processes that recur in primary use cases
These three secondary use cases form the wiring of all primary use cases. Without them, primary use cases cannot be completed successfully.
In any primary use case, any party needs to:
| Panel |
|---|
5a. Check whether its counterparty is iSHARE adherent/certified (with the Scheme Owner) 5b. Check whether its counterparty’s certificate is valid |
In any primary use case, the Service Provider also needs to:
| Panel |
|---|
6. Determine an authorization decision based on entitlement-, delegation-, and/or authorization info in its own contract administration and/or from external PIPs |
When delegation- or authorization info is requested by a Service Provider, an Authorization Registry or Entitled Party also needs to:
| Panel |
|---|
7. Determine authorization decision based on Service Consumer assertion included in Service Provider’s request |
Please note that the secondary use cases will not be detailed more than the above. No depictions or sequence diagrams are to be developed (contrary to for the primary use cases). This (deliberately) leaves freedom in implementation.