Difference between revisions of "EProcedure Rules Engine"
Jump to navigation
Jump to search
| (14 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
|- | |- | ||
| name | | name | ||
| − | | | + | | eProcedure Rules Engine |
|- | |- | ||
| description | | description | ||
| − | | | + | | Application component taking care of matching procedural requirements with evidence and establishing available and missing evidence. |
| + | |- | ||
|- | |- | ||
| 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|eProcedure Portal]] | ||
|} | |} | ||
---- | ---- | ||
| Line 26: | Line 28: | ||
! Application Service !! Description !! Pattern | ! Application Service !! Description !! Pattern | ||
|- | |- | ||
| − | | Procedural | + | | Procedural Requirements Determination |
| The DC determines the applicable requirements for a procedure. This service supports this requirements determination and bundles UI and logic to do so. | | The DC determines the applicable requirements for a procedure. This service supports this requirements determination and bundles UI and logic to do so. | ||
| − | | [[Intermediation Pattern|IM]], [[USI]] [[VC]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]] |
|- | |- | ||
| − | | Requirements/ | + | | Requirements/Evidence Matching |
| The DC matches the requirements with available evidence. This service bundles UI and logic to match the requirements with available evidence in order to establish if there is a delta (missing evidence). | | The DC matches the requirements with available evidence. This service bundles UI and logic to match the requirements with available evidence in order to establish if there is a delta (missing evidence). | ||
The first use of this service takes place after establishing the procedural requirements (i.e. evidence already available in the DC MS), the second use is after evidence collection to establish completeness (i.e. then also including exchanged evidence). | The first use of this service takes place after establishing the procedural requirements (i.e. evidence already available in the DC MS), the second use is after evidence collection to establish completeness (i.e. then also including exchanged evidence). | ||
| − | | [[Intermediation Pattern|IM]], [[USI]], [[VC]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]], [[Lookup Pattern|LKP]] |
| + | |- | ||
| + | | Available Evidence Determination | ||
| + | | Generic. The DC looks what required evidence is already available for the user on national level (doesn’t have to be requested). This service includes querying national base registers for available evidence. | ||
| + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]] | ||
|- | |- | ||
| + | |||
|} | |} | ||
| Line 45: | Line 52: | ||
! Component!! Source !! UC !!Description | ! Component!! Source !! UC !!Description | ||
|- | |- | ||
| − | | | + | | eVS |
| − | | | + | | Ministry for public administration |
| − | | [[ | + | | [[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 | ||
| + | | NL/Rijksdienst voor Ondernemend Nederland | ||
| + | | [[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. | ||
|- | |- | ||
| − | | | + | | ... |
| − | | | + | | to be completed (MA?) |
| − | | | + | | ... |
| − | | | + | | ... |
|- | |- | ||
|} | |} | ||
Latest revision as of 13:07, 21 June 2021
| Item | Description |
|---|---|
| name | eProcedure Rules Engine |
| description | Application component taking care of matching procedural requirements with evidence and establishing available and missing evidence. |
| pattern(s) | IM, USI, VC |
| application collaboration | eProcedure Portal |
| Application Service | Description | Pattern |
|---|---|---|
| Procedural Requirements Determination | The DC determines the applicable requirements for a procedure. This service supports this requirements determination and bundles UI and logic to do so. | IM, USI, VC |
| Requirements/Evidence Matching | The DC matches the requirements with available evidence. This service bundles UI and logic to match the requirements with available evidence in order to establish if there is a delta (missing evidence).
The first use of this service takes place after establishing the procedural requirements (i.e. evidence already available in the DC MS), the second use is after evidence collection to establish completeness (i.e. then also including exchanged evidence). |
IM, USI, VC, LKP |
| Available Evidence Determination | Generic. The DC looks what required evidence is already available for the user on national level (doesn’t have to be requested). This service includes querying national base registers for available evidence. | IM, USI |
| 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. |
| ... | to be completed (MA?) | ... | ... |