Difference between revisions of "DE4A Issuing Authority Locator (IAL)"

From DE4A
Jump to navigation Jump to search
m (reference to EB in OOTS Hub)
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Issuing Authority Locator (IAL) component helps the DC to find out the issuing authority that can provide the required evidence within a particular country.  
+
Issuing Authority Locator (IAL) component helps Data Consumers (DC) to find out the issuing authority within a particular country either to obtain a canonical evidence type or to subscribe a canonical event catalogue, and know the characteristics of the evidence provision or the subscription provision, respectively.  
  
 
In order to identify the corresponding issuing authority by the DC, this component requires the following preconditions:
 
In order to identify the corresponding issuing authority by the DC, this component requires the following preconditions:
  
# The user has said to the DC that the evidence must be provided by other country.
+
# The user has said to the DC that the evidence or the event must be provided by other country.
# DC knows which canonical criterion or [[canonical evidence]] corresponds to the evidence to get through the technical system
+
# DC knows which [[Canonical Evidence|canonical evidence]] type or canonical event catalogue that corresponds to the evidence or event specified by the user. Domestic evidence and events are nationally matched with canonical evidence type and canonical event catalogues.
# Every issuing authority registered per canonical evidence has a service to provide such an evidence
+
# Every issuing authority registered in the IAL its evidence and subscription provisions, i.e., that there is a service to provide a canonical evidence type or a canonical event catalogue
# Each canonical evidence is only provided by one competent authority within a certain territorial or administrative scope (e.g, in Spain, evidence of a person has some university degree is in the registries of the corresponding university and the Ministry, but only this last one is the competence authority to prove such a fact)
+
# Each canonical evidence type and event catalogue is only provided by one competent authority within an administrative territorial scope; if authorities at different administrative territorial level can provide the same canonical evidence type or event catalogue, the authority within the higher level should be registered. For instance, if evidence of a person has some university degree is in both registries of the corresponding university (at a educational level) and Ministry (at national level), only this last one is the competence authority to be registered in the IAL to participate in the cross-border exchange.
  
There are three possible options and their respective flows:
+
There are several possible options with their respective flows:
  
# '''[[Canonical evidence|Canonical Evidence]] (Main flow):''' when DC sends a request to DP, first DC will enquire from IDK about the issuing authority for a specific canonical evidence based on the respective country. IDK will provide two possible outcomes. The first is that IDK gives the national issuing authority for the canonical evidence. The second possible result is that IDK returns an error message because there is no issuing authority for such canonical evidence in such country.
+
# '''Provisions (Flow A, Main Flow):''' DC enquires at the [[Information Desk|IDK]] about the issuing authorities for one or a list of canonical evidence types and/or canonical event catalogues (at least one). IDK will provide two possible outcomes.  
 +
#* Success: list of provisions that complies with the enquire, grouped by canonical evidence type of event catalogue, country code and administrative territorial level.  
 +
#* Error Not Found: there is no issuing authority to provide the specified list.
 +
# '''Provisions at an administrative territorial unit  (Flow B, subcase of Flow A):''' DC enquires at the [[Information Desk|IDK]] about the issuing authority at a administrative territorial unit for one or a list of canonical evidence types and/or canonical event catalogues. IDK will provide the same possible outcomes than Flow A.
  
# '''Canonical Procedural Criterion (Alternate Flow to Flow A):''' In this option, DC send out a request to DP, DC will ask from IDK about the issuing authority for a given canonical criterion. Following are the possible  results from the IDK for DC:
+
The '''''provision metadata''''' is a set of attributes registered in the IAL: identifier of canonical evidence type or canonical event catalogue, identifier of the issuing authority, preferred label of the issuing authority, administrative territorial level and unit of the issuing authority, and Latin name of the territorial unit. The provision metadata is enough to to interact with the user to select one provision from a list and to locate the connection details of the corresponding data service in the ESL.
  
R1 (Success): list of canonical evidences that can be used to verify the given canonical criterion within such country, along with their particularities if any and the user selects the desired canonical and finally DC can adopt option Flow A (Main Flow) or Flow C (in case of multiple issuing authorities).
+
'''<u>Criteria-based vs evidence-based approach</u>'''
  
R2 (Error): there is no canonical evidence associated to the given canonical criterion within the country e-A2. DC does not choose any canonical evidence, and DC does not able to choose any canonical evidence.
+
The approaches to facilitate the mapping between domestic and cross-border evidences are; ''criteria-based'' or ''evidence-based'', or both, which can together fulfil the needs of both consuming competent authorities that work with procedural criteria and with evidence type.
  
# '''Various Options in a competence distribution Scenario:''' This flow is similar to Flow A with the difference of listing multiple issuing authorities. When DC sends a request to DP for an evidence, first DC will enquire regarding the issuing  authority for a canonical evidence that can be provided by various competent authorities in the given country. Following are the possible results of IDK through IAL to a respective DC request:
+
''Procedure criteria'' can be seen as procedural requirements either as conditions to satisfy directly by “yes/no” such as “is an adult”, or as information to be obtained, so some evidence type is required to prove such criteria. In the context of administrative procedures, criteria to asses may vary over the time, while evidence types rarely change. The '''evidence-based approach''' puts away procedural criteria concerns from the components of the technical system since it is only focused on a common list of evidence types and their canonical forms.
# Success: list of subnational authorities that can issue the canonical evidence within the country that can be done in several steps or the user is prompted to select the item of the returned list until the chosen item is the competent authority.
 
# Error: There is no subnational authorities that can issue the canonical evidence within the country at a certain administrative level or the user has cancelled the search
 
  
 +
Canonical evidence types provide a common classification of evidence relevant for procedures, so data evaluators and data owners can map their domestic evidence types to canonical evidence types. Moreover, canonical evidence is sent along with the lawfully issued domestic evidence to allow a common understanding and processing of the information provided regardless the format and language of domestic evidences, while domestic evidence provides the legal compliance in case of audits are needed.
  
In case of success and listing of the subnational authorities to be selected, NUTS taxonomy can be used but it needs to be considered that it does not correspond with the levels of public administrations in every MS.
+
Both approaches need agreements on the canonical forms of the evidence types from a country-agnostic perspective to guarantee a common understanding of evidences and to ease their processing. Besides, canonical evidence types are required to comply with the GDPR requirements on analysing datasets that are subject of some data processing, such as the data transfer to cross-border public authorities because they are relevant for their procedures.  
  
 
+
In the context of DE4A, the [https://ec.europa.eu/digital-building-blocks/wikis/display/OOTS/Common+and+Supporting+services Evidence Broker] could be used to extend the IAL with canonical procedural criteria that can be proved by canonical evidence types.
The approaches to ease the mapping between domestic and cross-border evidences are; criteria-based or evidence-based, or both, which can together fulfil the needs of both consuming competent authorities that work with procedural requirements and with evidences. For the criteria-based approach, IAL can use the Evidence Broker service (described at section 3.1.10), which is based on procedural requirements, which can be seen as criteria to be met and satisfied directly by “yes/no” evidences such as “is an adult”, or as information requirements to be satisfied by evidences in the form of a document or data. The Evidence Broker includes a data model that extends the CCCEV and combines it with DCAT and Core Agent vocabularies. This service returns a list of types of evidence that can be used to fulfil the requirement, where each type of evidence is expressed as a DCAT dataset. The data structures of these DCAT datasets are defined by agreed canonical data models. The UML diagram of the Evidence Broker data model is presented in Annex V. The evidence-based approach puts away procedural requirements concerns from the components of the technical system. It is only focused on evidence types and their canonical forms that are instantiated in the lawfully issued evidences. Both approaches need agreements on common data models to represent evidences from a country-agnostic perspective. In the context of DE4A, we proposed ontologies that can be used to define evidences based on each pilot requirements that are aligned with existing standard vocabularies and data models. These proposed common data models are created from the domain-specific ontologies described in section 5.3.
 
 
 
IAL covers both the evidence and criteria-based approaches for the mapping between domestic and cross-border evidences, as described in the deliverable D2.4 of the Project Start Architecture [45]. In the context of DE4A, we will reuse the core component of TOOP, the Evidence Broker, to find out the issuing authority that can provide the required evidence within a particular country and extend this according to the requirements of DE4A pilot use cases.
 

Latest revision as of 08:23, 20 January 2023

Issuing Authority Locator (IAL) component helps Data Consumers (DC) to find out the issuing authority within a particular country either to obtain a canonical evidence type or to subscribe a canonical event catalogue, and know the characteristics of the evidence provision or the subscription provision, respectively.

In order to identify the corresponding issuing authority by the DC, this component requires the following preconditions:

  1. The user has said to the DC that the evidence or the event must be provided by other country.
  2. DC knows which canonical evidence type or canonical event catalogue that corresponds to the evidence or event specified by the user. Domestic evidence and events are nationally matched with canonical evidence type and canonical event catalogues.
  3. Every issuing authority registered in the IAL its evidence and subscription provisions, i.e., that there is a service to provide a canonical evidence type or a canonical event catalogue
  4. Each canonical evidence type and event catalogue is only provided by one competent authority within an administrative territorial scope; if authorities at different administrative territorial level can provide the same canonical evidence type or event catalogue, the authority within the higher level should be registered. For instance, if evidence of a person has some university degree is in both registries of the corresponding university (at a educational level) and Ministry (at national level), only this last one is the competence authority to be registered in the IAL to participate in the cross-border exchange.

There are several possible options with their respective flows:

  1. Provisions (Flow A, Main Flow): DC enquires at the IDK about the issuing authorities for one or a list of canonical evidence types and/or canonical event catalogues (at least one). IDK will provide two possible outcomes.
    • Success: list of provisions that complies with the enquire, grouped by canonical evidence type of event catalogue, country code and administrative territorial level.
    • Error Not Found: there is no issuing authority to provide the specified list.
  2. Provisions at an administrative territorial unit (Flow B, subcase of Flow A): DC enquires at the IDK about the issuing authority at a administrative territorial unit for one or a list of canonical evidence types and/or canonical event catalogues. IDK will provide the same possible outcomes than Flow A.

The provision metadata is a set of attributes registered in the IAL: identifier of canonical evidence type or canonical event catalogue, identifier of the issuing authority, preferred label of the issuing authority, administrative territorial level and unit of the issuing authority, and Latin name of the territorial unit. The provision metadata is enough to to interact with the user to select one provision from a list and to locate the connection details of the corresponding data service in the ESL.

Criteria-based vs evidence-based approach

The approaches to facilitate the mapping between domestic and cross-border evidences are; criteria-based or evidence-based, or both, which can together fulfil the needs of both consuming competent authorities that work with procedural criteria and with evidence type.

Procedure criteria can be seen as procedural requirements either as conditions to satisfy directly by “yes/no” such as “is an adult”, or as information to be obtained, so some evidence type is required to prove such criteria. In the context of administrative procedures, criteria to asses may vary over the time, while evidence types rarely change. The evidence-based approach puts away procedural criteria concerns from the components of the technical system since it is only focused on a common list of evidence types and their canonical forms.

Canonical evidence types provide a common classification of evidence relevant for procedures, so data evaluators and data owners can map their domestic evidence types to canonical evidence types. Moreover, canonical evidence is sent along with the lawfully issued domestic evidence to allow a common understanding and processing of the information provided regardless the format and language of domestic evidences, while domestic evidence provides the legal compliance in case of audits are needed.

Both approaches need agreements on the canonical forms of the evidence types from a country-agnostic perspective to guarantee a common understanding of evidences and to ease their processing. Besides, canonical evidence types are required to comply with the GDPR requirements on analysing datasets that are subject of some data processing, such as the data transfer to cross-border public authorities because they are relevant for their procedures.

In the context of DE4A, the Evidence Broker could be used to extend the IAL with canonical procedural criteria that can be proved by canonical evidence types.