Difference between revisions of "EProcedure Portal Front-end"
Jump to navigation
Jump to search
| (31 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
|- | |- | ||
| name | | name | ||
| − | | eProcedure | + | | eProcedure Portal Front-end |
|- | |- | ||
| description | | description | ||
| − | | | + | | Application component managing the entire interaction between the user and the eProcedure Portal, including e.g. UI framework, specific forms integration with the eProcedure Portal Backend. In case of VC also handles the establishment of DID connections between DP and users. |
|- | |- | ||
| pattern(s) | | pattern(s) | ||
| − | | [[Intermediation Pattern|IM]], [[USI]], [[VC]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]] |
| + | |- | ||
| + | |application collaboration | ||
| + | |[[eProcedure Portal]] | ||
|- | |- | ||
| Line 26: | Line 29: | ||
! Application Service !! Description !! Pattern | ! Application Service !! Description !! Pattern | ||
|- | |- | ||
| − | | eProcedure | + | | 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. |
| − | | [[Intermediation Pattern|IM]], [[USI]], [[VC]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]] |
|- | |- | ||
| − | | Explicit | + | | Explicit Request |
| − | | | + | | The user must make an explicit request for OOP transfer of evidence. This service handles the request. |
| − | | [[Intermediation Pattern|IM]], [[USI]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]] |
|- | |- | ||
| − | | eProcedure | + | | eProcedure Termination |
| − | | | + | | An eProcedure can be aborted. This service terminates the requested eProcedure (public) service. |
| − | | [[Intermediation Pattern|IM]], [[USI]], [[VC]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|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. | ||
| + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]] | ||
|- | |- | ||
| − | | eProcedure | + | | eProcedure Conformation |
| − | | | + | | The acknowledgment that all required evidence is received by the DC is confirmed to the U by this service. |
| − | | [[Intermediation Pattern|IM]], [[USI]], [[VC]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|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. |
| − | | [[ | + | | [[Verifiable Credentials Pattern|VC]] |
|- | |- | ||
| − | | Verifiable Credential | + | | 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]] | + | | [[Verifiable Credentials Pattern|VC]] |
|- | |- | ||
| − | | | + | | Evidence Status Overview |
| − | | | + | | The DC updates the evidence status. This is supported by this service. |
| − | | [[VC]] | + | | [[Verifiable Credentials Pattern|VC]] |
|- | |- | ||
| − | | | + | |QR-code (UI) |
| − | | | + | |A service that provides a QR code to be displayed on the UI for the user to be scanned. |
| − | | [[VC]] | + | | [[Verifiable Credentials Pattern|VC]] |
|- | |- | ||
| Line 68: | Line 75: | ||
! Component!! Source !! UC !!Description | ! Component!! Source !! UC !!Description | ||
|- | |- | ||
| − | | eVS | + | | [[eVS]] |
| − | | Ministry | + | | Ministry for public administration |
| − | | [[SA (UC1)]] | + | | [[Use Case "Application to Public Higher Education" (SA UC1)|SA (UC1)]] |
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. | | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. | ||
|- | |- | ||
|- | |- | ||
| − | | mijnRVO | + | | [[mijnRVO]] |
| NL/Rijksdienst voor Ondernemend Nederland | | NL/Rijksdienst voor Ondernemend Nederland | ||
| − | | [[DBA (UC1)]] | + | | [[Use Case "Starting a Business in Another Member State" (DBA UC1)|DBA (UC1)]] |
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. | | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. | ||
| + | |- | ||
| + | | ... | ||
| + | | | ||
| + | | | ||
| + | | | ||
|- | |- | ||
|} | |} | ||
Latest revision as of 14:32, 23 June 2021
| Item | Description |
|---|---|
| name | eProcedure Portal Front-end |
| description | Application component managing the entire interaction between the user and the eProcedure Portal, including e.g. UI framework, specific forms integration with the eProcedure Portal Backend. In case of VC also handles the establishment of DID connections between DP and users. |
| pattern(s) | IM, USI, VC |
| application collaboration | eProcedure Portal |
| 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 |
| QR-code (UI) | A service that provides a QR code to be displayed on the UI for the user to be scanned. | VC |
| Component | Source | UC | Description |
|---|---|---|---|
| eVS | Ministry for public administration | SA (UC1) | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |
| mijnRVO | NL/Rijksdienst voor Ondernemend Nederland | DBA (UC1) | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |
| ... |