Use cases

This chapter builds on the iSHARE Trust Framework to showcase the key functionalities in four use cases and their Verifiable Credentials (VC) variant.

Both versions describe the same business goals; they differ only in the technical evidence used for authentication and authorisation:

• [Classic]: JWT artefacts and registry lookups

• [VC variant]: Verifiable Credentials (VCs) and Verifiable Presentations (VPs) (Refer to Glossary)

Many implementers run the classic flow today. The VC pages let you adopt RFC040 gradually and compare flows 1:1. Use whichever matches your deployment.

1. Use case: M2M interaction (with fine-grained authorisation) showcases:

   • Support Machine-to-Machine (M2M) interaction;

   • Facilitate flexible authorisations, applicable in any context.

2. Use case: H2M interaction (with coarse-grained authorisation) showcases:

   • Support Human to Machine (H2M) interaction;

   • Facilitate flexible authorisations, applicable in any context.

3. Use case: portable identity showcases:

   • Facilitate portable identity(s) for parties and humans.

4. Use case: delegation (and management of consent) showcases:

   • Enable data exchange based on delegations - even between unknown parties;

   • Enable control over own data through management of consent.

Structure

Each use case includes:

• A description and depiction of the roles and relations;

• A description of the prerequisites, and a depiction of prerequisite registration;

• A description and depiction of the use case;

• A sequence diagram;

• A reference to what needs to be technically implemented for this use case.

The depicted use cases are only a selection of the iSHARE Trust Framework's use case scope. For the full scope, please refer to the detailed Functional descriptions.