Difference between revisions of "Data Service Lookup"
Jump to navigation
Jump to search
m |
|||
| Line 16: | Line 16: | ||
|- | |- | ||
| pattern(s) | | pattern(s) | ||
| − | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]], [[Subscription and Notification Pattern|S&N]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]], [[Subscription and Notification Pattern|S&N]], [[Lookup Pattern|LKP]] |
|- | |- | ||
|application collaboration | |application collaboration | ||
| Line 32: | Line 32: | ||
| Inquire Routing Information | | Inquire Routing Information | ||
| The DC looks up where to send the request (e.g. for evidence). This service acts as an API to lookup the routing information. Depending on the chosen solution, this service can be performed in several steps: Identification of the addressed DC competent authority (i.e. a unique identifier), identification of the specific data service provided by that competent authority and lookup of the technical address of that data service. Solution components can realize instances of the Inquire Routing Information service that include all or any of these steps. | | The DC looks up where to send the request (e.g. for evidence). This service acts as an API to lookup the routing information. Depending on the chosen solution, this service can be performed in several steps: Identification of the addressed DC competent authority (i.e. a unique identifier), identification of the specific data service provided by that competent authority and lookup of the technical address of that data service. Solution components can realize instances of the Inquire Routing Information service that include all or any of these steps. | ||
| − | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Subscription and Notification Pattern|S&N]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Subscription and Notification Pattern|S&N,]] [[Lookup Pattern|LKP]] |
|- | |- | ||
| Verifiable Credential Issuer search | | Verifiable Credential Issuer search | ||
Revision as of 13:40, 21 June 2021
| Item | Description |
|---|---|
| name | Data Service Lookup |
| description | Application component for looking up the data service(s) that can be used to request an evidence.
In case of VC it returns the URL of the evidence portal. |
| pattern(s) | IM, USI, VC, S&N, LKP |
| application collaboration | Information Desk |
| Application Service | Description | Pattern |
|---|---|---|
| Inquire Routing Information | The DC looks up where to send the request (e.g. for evidence). This service acts as an API to lookup the routing information. Depending on the chosen solution, this service can be performed in several steps: Identification of the addressed DC competent authority (i.e. a unique identifier), identification of the specific data service provided by that competent authority and lookup of the technical address of that data service. Solution components can realize instances of the Inquire Routing Information service that include all or any of these steps. | IM, USI, S&N, LKP |
| Verifiable Credential Issuer search | The service, based on the information from the information desk, performs a list of all possible issuers of evidence (VC) that may be later used by the user to satisfy procedural requirements. The list consists of the name of the institution, MS, region and a link for its related evidence portal. | VC |
| Component | Source | UC | Description |
|---|---|---|---|
| ESL | DE4A | ... | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |
| Issuing Authority Locator (IAL) | IDK | All | IDK component that helps the DC to find out the issuing authority that can provide the required evidence within a particular country |