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

From DE4A
Jump to navigation Jump to search
m (reference to EB in OOTS Hub)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Issuing Authority Locator (IAL) component helps the Data Consumer (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|canonical evidence]] type 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 type 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 type is only provided by one competent authority within a certain territorial or administrative scope; if authorities from different administrative level can provide the same canonical evidence type, the authority within the higher level should be registered. For instance, if evidence of a person has some university degree is in the registries of the corresponding university and the Ministry, only this last one is the competence authority to be registered as such evidence type provider in the country
+
# 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:
 
There are several possible options with their respective flows:
  
# '''[[Canonical Evidence]] (Flow A, Main Flow):''' when DC sends a request to Data Provider (DP), first DC will enquire from [[Information Desk|IDK]] about the issuing authority for a specific canonical evidence type based on the respective country. IDK will provide two possible outcomes.  
+
# '''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: the national issuing authority that provides the canonical evidence type in such country, along with the provision metadata.  
+
#* 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 for such canonical evidence type in such country.
+
#* Error Not Found: there is no issuing authority to provide the specified list.
# '''[[Canonical Evidence]] in a competence distribution Scenario (Flow B, subcase of Flow A):''' This flow is similar to Flow A with the difference of there are multiple sub-national issuing authorities for a canonical evidence type. Following are the possible  results from the IDK for DC:
+
# '''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.
#* Success: list of subnational authorities that can issue the canonical evidence type within the country, each one with the corresponding provision metadata. All the listed subnational authorities corresponds to a same administrative level, i.e., list of universities, regions from a NUTS level or municipality from LAU.Then the user is prompted to select the item of the returned list.
 
#* Error Not Found: There is no subnational authorities that can issue the canonical evidence within the country
 
#* Error Cancel: the user has cancelled the selection of an item from the given list
 
# '''Canonical Procedural Criterion (Flow C, Alternate Main Flow):''' In this option, first DC will ask from IDK about the issuing authority for a given canonical criterion. Following are the possible  results from the IDK for DC:
 
#* Success: list of canonical evidence types that can be used to verify the given canonical criterion within such country, along with their particularities if any. Then either the DC by a rule or the user selects the desired evidence type and finally DC can adopt option Flow A or Flow B.
 
#* Error: there is no canonical evidence types associated to the given canonical criterion within the country
 
#* Error Cancel: No canonical evidence type has been selected from the given list.
 
  
The '''''provision metadata''''' is a set of attributes that defines each possible evidence provision registered in the IAL that has an associated ESL entry. These attributes are: identifier of canonical evidence type, identifier of the DP, administrative territorial level and unit of the DP, and type of provision (IP or USI). The provision metadata is enough to locate in the ESL the corresponding data service and its connection details.
+
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.
  
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 criteria and with evidences type. Procedure criteria can be seen as procedural requirements either as conditions to satisfy directly by “yes/no” evidence types such as “is an adult”, or as information to be obtained. For the criteria-based approach, IAL can be extended to included canonical procedural criteria and the mapping to canonical evidence types within each country. The evidence-based approach puts away procedural criteria concerns from the components of the technical system; it is only focused on a list of evidence types and their canonical forms that are instantiated in the lawfully issued evidences. Both approaches need agreements on the canonical forms of the evidence types from a country-agnostic perspective. In the context of DE4A, we proposed to define the canonical forms from domain-specific ontologies based on each pilot requirements in alignment with existing standard vocabularies and data models. Issuing authorities are responsible for providing domestic evidence in the corresponding canonical form.
+
'''<u>Criteria-based vs evidence-based approach</u>'''
  
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 (ref) of the Project Start Architecture [ref]. In the context of DE4A, we will reuse the core component of TOOP (ref), the Evidence Broker (ref), to extend the IAL with canonical procedural criteria according to the requirements of DE4A pilot use cases.
+
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 [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.

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.