Difference between revisions of "Information Desk"
| Line 22: | Line 22: | ||
|- | |- | ||
| [[Authorities Editor]] | | [[Authorities Editor]] | ||
| − | | | + | | Application component maintaining the list of competent authorities and the relationships between those authorities and evidences. |
| [[Intermediation Pattern|IM]], [[USI]], [[VC]] | | [[Intermediation Pattern|IM]], [[USI]], [[VC]] | ||
|- | |- | ||
| [[Evidence Type Translator]] | | [[Evidence Type Translator]] | ||
| − | | | + | | Application component taking care of translating one type of evidence in MS of DC to other (potentially multiple), equivalent, type of evidence in MS of DP by using a mapping of evidences. |
| [[Intermediation Pattern|IM]], USI | | [[Intermediation Pattern|IM]], USI | ||
|- | |- | ||
| [[Evidence Map Editor]] | | [[Evidence Map Editor]] | ||
| − | | | + | | Application component maintaining the evidence mappings. |
| [[Intermediation Pattern|IM]], [[USI]] | | [[Intermediation Pattern|IM]], [[USI]] | ||
|- | |- | ||
Revision as of 08:37, 26 March 2021
The Information desk application collaboration combines multiple co-operating application components. It offers generic functionality used by DC and DP to facilitate the OOP exchanges. It offers functionality to do the cross-border evidence matching, i.e. using an evidence map, mapping required evidences to equivalent evidences in another MS. The DC uses the information desk to lookup routing information, i.e. where to request a piece of evidence. DC can use it to do a legal basis check in case no user request or approval is needed. The DP consults the information desk to establish that the DC is authorized/allowed to request some evidence type.
For VC the Information Desk erves as a supporting mechanism for the User, which can help him find the relevant VC issuer (i.e. possible DP) in case he is missing any evidence for the procedure. The information desk functionality is achieved through the collaboration of several application components. The Data service lookup component provides an interface to the eProcedure, where the User can retrieve the list of competent authorities (i.e. DPs) within a given geographic area for the evidence he is missing. The list is obtained by reading the entries from the Service registry, which communicates with the Authorization controller to register any changes in the Competent authorities list and the Authority to evidence matrix.
| Application Component | Description | Pattern(s) |
|---|---|---|
| Data Service Lookup | 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. |
IM, USI, VC |
| Service Registry Editor | Application component maintaining the service registry. | IM, USI,VC |
| Authorization Controller | Application component to establish which evidence types can be exchanged between competent authorities and whether this is allowed under allowed under applicable Union or national law without user request and preview. | IM, USI, VC |
| Authorities Editor | Application component maintaining the list of competent authorities and the relationships between those authorities and evidences. | IM, USI, VC |
| Evidence Type Translator | Application component taking care of translating one type of evidence in MS of DC to other (potentially multiple), equivalent, type of evidence in MS of DP by using a mapping of evidences. | IM, USI |
| Evidence Map Editor | Application component maintaining the evidence mappings. | IM, USI |
note: USI doesn't have the information desk in the PSA