Secondary use cases

iSHARE Trust Framework'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 party needs to:

Before initiating Human to Machine use cases, the Service Consumer needs to:

When delegating rights, the Entitled Party needs to:

When authorizing something or -one, the Service Consumer needs to:

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:

In any primary use case, the Service Provider also needs to:

When delegation- or authorization info is requested by a Service Provider, an Authorization Registry or Entitled Party also needs to:

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. This specifically accounts for the registration of delegations: the way in which delegations are registered (as policies, business rules, in a separate register, or on top of existing applications) is not defined.

Last updated