| Application Service |
Description |
Pattern
|
| eProcedure initiation
|
The user can start a specific eProcedure to receive a public service and provide an initial set of information. The service bundles UI and handling of the data provided by the user.
|
IM, USI, VC
|
| Explicit request
|
The user must make an explicit request for OOP transfer of evidence. This service handles the request.
|
IM, USI
|
| eProcedure termination
|
An eProcedure can be aborted. This service terminates the requested eProcedure (public) service.
|
IM, USI, VC
|
| eProcedure submission
|
After all evidence is available and the requirements of the procedure have been fulfilled the user can submit the request. This service bundles UI and handling of request submission.
|
IM, USI, VC
|
| eProcedure conformation
|
The acknowledgment that all required evidence is received by the DC is confirmed to the U by this service.
|
IM, USI, VC
|
| Verifiable Credential request
|
The service that generates a request for the issuance of evidence in the form of VC on the DP side. It includes the information of the required VC schema.
|
VC
|
| Verifiable Credential Processing initiation
|
The U chooses to request the transfer of evidence in the form of Verifiable Credentials (VC). This service prepares and provides the DC’s DID data, which will be later used for the preparation of a DID Connection between the U and DC.
|
VC
|
| Evidence status overview
|
The DC updates the evidence status. This is supported by this service.
|
VC
|
