Difference between revisions of "Evidence Interchange Back-end"
Jump to navigation
Jump to search
| (14 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
|- | |- | ||
| name | | name | ||
| − | | | + | | Evidence Interchange Back-end |
|- | |- | ||
| description | | description | ||
| − | | | + | | Application component managing the tracking of evidence requests and supporting the removal of evidences. |
|- | |- | ||
| pattern(s) | | pattern(s) | ||
| − | | [[Intermediation Pattern|IM]], [[USI]], [[VC]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]], [[Lookup Pattern|LKP]] |
| + | |- | ||
| + | |application collaboration | ||
| + | |[[Evidence Interchange Management]] | ||
|- | |- | ||
| Line 26: | Line 29: | ||
! Application Service !! Description !! Pattern | ! Application Service !! Description !! Pattern | ||
|- | |- | ||
| − | | | + | | Evidence status tracker |
| − | | | + | | The DC keeps track of evidence requested versus evidence received. This service bundles the UI and logic to support this. |
| − | | [[Intermediation Pattern|IM]], [[VC]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC,]] [[Lookup Pattern|LKP]] |
|- | |- | ||
| − | | | + | | Evidence request tracker |
| − | | | + | | The DC establishes the technical availability of evidence. Was some piece of evidence received, did a timeout occur (SLA) or was an error code returned by the DP? This service keeps track of requested evidence. |
| − | | [[Intermediation Pattern|IM]], [[USI]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI,]] [[Lookup Pattern|LKP]] |
| + | |- | ||
| + | |Evidence Shredder | ||
| + | |For various reasons (request by user or established time limit for the data) evidence must be deleted. This service bundles UI and logic to support this. | ||
| + | |[[Intermediation Pattern|IM]] | ||
|- | |- | ||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
| Line 48: | Line 51: | ||
! Component!! Source !! UC !!Description | ! Component!! Source !! UC !!Description | ||
|- | |- | ||
| − | | | + | | [[Connector|DE4A Connector]] |
| − | | | + | | D4EA |
| − | | | + | | all? |
| 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 13:54, 21 June 2021
| Item | Description |
|---|---|
| name | Evidence Interchange Back-end |
| description | Application component managing the tracking of evidence requests and supporting the removal of evidences. |
| pattern(s) | IM, USI, VC, LKP |
| application collaboration | Evidence Interchange Management |
| Application Service | Description | Pattern |
|---|---|---|
| Evidence status tracker | The DC keeps track of evidence requested versus evidence received. This service bundles the UI and logic to support this. | IM, USI, VC, LKP |
| Evidence request tracker | The DC establishes the technical availability of evidence. Was some piece of evidence received, did a timeout occur (SLA) or was an error code returned by the DP? This service keeps track of requested evidence. | IM, USI, LKP |
| Evidence Shredder | For various reasons (request by user or established time limit for the data) evidence must be deleted. This service bundles UI and logic to support this. | IM |
| Component | Source | UC | Description |
|---|---|---|---|
| DE4A Connector | D4EA | all? | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |
| abc | descr abc | [[]] | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |