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

From DE4A
Jump to navigation Jump to search
(Include "type" to refer to categories of evidence and not to a particular instance. Editorial improvement of the flows. Clarifications on the adoption of the criteria-based approach.)
Line 4: Line 4:
  
 
# 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 must be provided by other country.
# DC knows which canonical criterion or [[Canonical Evidence|canonical evidence]] corresponds to the evidence to get through the technical system
+
# DC knows which canonical criterion or [[Canonical Evidence|canonical evidence]] type corresponds to the evidence to get through the technical system
# Every issuing authority registered per canonical evidence has a service to provide such an evidence
+
# Every issuing authority registered per canonical evidence type has a service to provide such an evidence
# 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 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
  
There are three possible options and their respective flows:
+
There are several possible options with their respective flows:
  
# '''[[Canonical Evidence]] (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 based on the respective country. IDK will provide two possible outcomes. The first is that [[Information Desk|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.
+
# '''[[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.  
 +
#* Success: the national issuing authority that provides the canonical evidence type in such country, along with the provision metadata.
 +
#* Error Not Found: there is no issuing authority for such canonical evidence type in such country.
 +
# '''[[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:
 +
#* 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.<br />
  
# '''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 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.
  
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).
+
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.
 
 
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.
 
 
 
# '''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:
 
# 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
 
 
 
 
 
 
 
In case of success and listing of the subnational authorities to be selected, NUTS taxonomy (ref) can be used but it needs to be considered that it does not correspond with the levels of public administrations in every MS.
 
 
 
 
 
 
 
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 (ref), 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(ref) and combines it with DCAT(ref) and Core Agent (ref) 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 (ref). 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 (ref). The evidence-based approach (def) 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 (def) 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 (ref).
 
 
 
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 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.
 

Revision as of 11:58, 31 May 2021

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.

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 must be provided by other country.
  2. DC knows which canonical criterion or canonical evidence type corresponds to the evidence to get through the technical system
  3. Every issuing authority registered per canonical evidence type has a service to provide such an evidence
  4. 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

There are several possible options with their respective flows:

  1. Canonical Evidence (Flow A, Main Flow): when DC sends a request to Data Provider (DP), first DC will enquire from IDK about the issuing authority for a specific canonical evidence type based on the respective country. 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.
    • Error Not Found: there is no issuing authority for such canonical evidence type in such country.
  2. 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:
    • 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
  3. 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 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.

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.