Difference between revisions of "Information Desk"
(Evidence type translator entry) |
|||
Line 38: | Line 38: | ||
|- | |- | ||
|[[Evidence Type Translator]] | |[[Evidence Type Translator]] | ||
− | | Application component taking care of translating one type of evidence | + | | Application component taking care of translating one type of evidence from its domestic form to the corresponding canonical form. The translation has to be implemented both for issuing and processing evidence by DP and DC respectively. Since since [[Canonical Evidence|canonical evidence types]] are the ground for the [[semantic interoperability]] of cross-border evidence, and semantic and syntactic aspects of domestic evidence types can vary significantly, the evidence type translator should be implemented by each evidence consumer and provider according to their specificities, |
− | |||
|[[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI,]] [[Lookup Pattern|LKP]] | |[[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI,]] [[Lookup Pattern|LKP]] | ||
|- | |- |
Revision as of 15:24, 22 June 2021
The Information desk application collaboration that combines multiple co-operating application components. It is a logic component that offers information to help DC and DP to perform the OOP exchanges. For IM And USI, It offers information to the DC for helping the user to locate the proper competent authority to provide the required cross-border evidence and for finding the routing information to do the request. The DP consults the information desk to establish that the DC is authorized/allowed to request some evidence type. Besides, the Information Desk can helps users and civil servants to understand cross-border evidence. For VC the Information Desk serves 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, S&N, LKP |
Service Registry Editor | Application component maintaining the service registry. | IM, USI,VC, S&N, LKP |
Authorization Controller | Application component to establish which data service, e.g. evidence types can be requested and whether this is allowed under allowed under applicable Union or national law without user request and preview. This applies also to the subscription service. | IM, USI, S&N, LKP |
Authorities Editor | Application component maintaining the list of competent authorities and the relationships between those authorities and evidences. | IM, USI, S&N, LKP |
Evidence Type Translator | Application component taking care of translating one type of evidence from its domestic form to the corresponding canonical form. The translation has to be implemented both for issuing and processing evidence by DP and DC respectively. Since since canonical evidence types are the ground for the semantic interoperability of cross-border evidence, and semantic and syntactic aspects of domestic evidence types can vary significantly, the evidence type translator should be implemented by each evidence consumer and provider according to their specificities, | IM, USI, LKP |
Evidence Map Editor | Application component maintaining the evidence mappings.
note Won't be piloted in DE4A |
IM, USI, LKP |
Information Desk to Evidence Interchange Management | Interface to Data Service Lookup exposed to Evidence Interchange Management. | IM, USI, VC, LKP |
Information Desk to Cross-border Notifications | Interface to Cross-border Notifications providing the routing information for the notifications | S&N |
Equivalent Evidence | Interface to Evidence Type Translator for identifying equivalent evidence.
Note Won't be piloted in DE4A |
IM, USI, LKP |
Competent Authorities | Interface exposing the Authorization Controller for establishing that a Competent Authority is allowed to request a certain Evidence Type. | IM, USI, LKP |
Attribute Definition and Label Translation | Application component taking care of the translation of attribute definitions and labels. | IM, USI |
Multi-lingual Translator | Interface to the Attribute Definition and Label Translation for looking up multi-lingual translations of attribute definitions and labels. | IM, USI |
Translation Map Editor | Application component maintaining the mapping used for translations. | IM, USI |