Difference between revisions of "Data Dictionary"

From DE4A
Jump to navigation Jump to search
m (Quality review)
 
(9 intermediate revisions by 2 users not shown)
Line 14: Line 14:
 
!Mandatory Field / Label
 
!Mandatory Field / Label
 
!Description
 
!Description
−
|-
 
−
|ResponseLookupRoutingInformation
 
−
|[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseLookupRoutingInformationType ResponseLookupRoutingInformationType]
 
−
|1
 
−
|Y/Y
 
−
|Root element
 
 
|-
 
|-
 
|ResponseItem
 
|ResponseItem
Line 31: Line 25:
 
|1..n
 
|1..n
 
|Y/Y
 
|Y/Y
−
|Contains the response error.
+
|Contains a list with the descriptions of the errors if one or more have occurred.
 
|}
 
|}
  
Line 79: Line 73:
 
|1..n
 
|1..n
 
|Y/Y
 
|Y/Y
−
|
+
|Contains the data of each possible provision.
 
|}
 
|}
  
Line 96: Line 90:
 
| 1
 
| 1
 
|N/Y
 
|N/Y
−
|Level of administration territorial unit.
+
|Level of Administrative Territorial Unit.
 
'''Allowed values:'''
 
'''Allowed values:'''
  
Line 105: Line 99:
 
* lau: Local level  
 
* lau: Local level  
 
* edu: Educational level  
 
* edu: Educational level  
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|AtuCode
 
|AtuCode
Line 111: Line 104:
 
|1
 
|1
 
|N/Y
 
|N/Y
−
| Code of the administrative territory unit.  
+
| Code of the Administrative Territorial Unit.
  
 
'''Allowed values:'''
 
'''Allowed values:'''
  
−
* ISO 3166-1 alfa-2 for nuts0  
+
* "ISO 3166-1 alfa-2" for nuts0
−
* Region for nuts1-3  
+
* "Region" for nuts1-3
−
* Municipality for lau  
+
* "Municipality" for lau
−
* Educational Organization for edu  
+
* "Educational Organization" for edu
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|AtuLatinName
 
|AtuLatinName
Line 131: Line 123:
 
|1
 
|1
 
|N/Y
 
|N/Y
−
|Identifies the Data Owner in iso6523 format<br />Defines Party ID for all participants
+
|Identifies the Data Owner in iso6523 format. It defines Party Id for all participants. It must be unique.
−
MUST be UNIQUE
 
−
 
 
 
'''Format:''' {PEPPOL ParticipantIdentifierScheme}::{Domain Scheme}:{Party Id} → iso6523-actorid-upis::[0-9][0-9][0-9][0-9]:[A-Z0-9]{1,15}  
 
'''Format:''' {PEPPOL ParticipantIdentifierScheme}::{Domain Scheme}:{Party Id} → iso6523-actorid-upis::[0-9][0-9][0-9][0-9]:[A-Z0-9]{1,15}  
  
−
'''{PEPPOL ParticipantIdentifierScheme}:''' Must be a constant “iso6523-actorid-upis”  
+
* '''{PEPPOL ParticipantIdentifierScheme}:''' Must be the constant “iso6523-actorid-upis”  
 +
* '''{Domain Scheme}:''' Identifies ICD value, must be a 4-digit UNIQUE number in PEPPOL
 +
* '''{Party Id}:''' Identifies DE4A Partner, consisting of:
 +
** 2 letters for country
 +
** 2 digits for entity type → 00 if entity is a DE4A partner, 88 if not; for regional or local administrations, the entity type is 99
 +
** 7 digits for DE4A Partner. For regional or local administrations, it is the NUTS/LAU code without country letters and starting with as many zeros on the left as necessary until reaching 7 digits.
  
−
'''{Domain Scheme}:''' Identifies ICD value, must be a 4-digit UNIQUE number in PEPPOL
+
Example of the Spanish Municipality of San Sebastian with LAU code 20069: '''ES990020069'''
  
−
'''{Party Id}:''' Identifies DE4A Partner, consisting of:
+
Example of the Dutch Province of Groningen with NUTS code NL11: '''NL990000011'''
  
−
* 2 letters for country
+
https://docs.peppol.eu/edelivery/policies/PEPPOL-EDN-Policy-for-use-of-identifiers-4.0-2019-01-28.pdf
−
* 2 digits for entity type → 00 if entity is a DE4A partner, 88 if not
 
−
* 7 digits for DE4A Partner
 
−
 
 
−
For regional or local administrations, the entity type is 99 and the 7 digit number is the NUTS/LAU code without country letters and starting with as many zeros on the left as necessary until 7 digits.
 
−
 
 
−
Example Spanish Municipality of San Sebastian with LAU code 20069: '''ES990020069''' 
 
  
−
Example of Dutch Province of Groningen with NUTS code NL11: '''NL990000011''' 
+
For further information on the Domain Scheme values, see the [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
−
 
 
−
https://docs.peppol.eu/edelivery/policies/PEPPOL-EDN-Policy-for-use-of-identifiers-4.0-2019-01-28.pdf
 
 
|-
 
|-
 
|DataOwnerPrefLabel
 
|DataOwnerPrefLabel
Line 183: Line 170:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Name of the required parameter for the requested evidence.
+
|Name of the required set of parameters for the requested evidence.
 
|-
 
|-
 
|Parameter
 
|Parameter
Line 229: Line 216:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Code of the error occurred. See [FIX TABLE/DOCUMENT ERRORS]
+
|Code of the error occurred. See [[DE4A Logs and error messages it2]]
 
|-
 
|-
 
|Text
 
|Text
Line 235: Line 222:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Text defining the above code. See [FIX TABLE/DOCUMENT ERRORS]
+
|Text defining the above code. See [[DE4A Logs and error messages it2]]
 
|}
 
|}
  
Line 247: Line 234:
 
!Mandatory Field / Label
 
!Mandatory Field / Label
 
!Description
 
!Description
−
|-
 
−
|RequestExtractMultiEvidenceIMType
 
−
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceIMType RequestExtractMultiEvidenceIMType]
 
−
|1
 
−
|Y/Y
 
−
|Root element
 
 
|-
 
|-
 
|RequestId
 
|RequestId
Line 258: Line 239:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Request message identifier
+
|Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
 
|-
 
|-
 
|SpecificationId
 
|SpecificationId
Line 264: Line 245:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Version used and it will define the message structure.
+
|IEM version used
 
|-
 
|-
 
|Timestamp
 
|Timestamp
Line 270: Line 251:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Date and time when the message is created. Its value will not be changed when subsequent messages having this timestamp attribute
+
|Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
−
are created.
 
 
|-
 
|-
 
|ProcedureId
 
|ProcedureId
Line 277: Line 257:
 
|1
 
|1
 
|N/Y
 
|N/Y
−
|Metadata about a procedure or public service.  
+
|Metadata about the procedure or public service the justifies the use of the DE4A OOTS.
 
|-
 
|-
 
|DataEvaluator
 
|DataEvaluator
Line 283: Line 263:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifier will be used to address the evidence back from the DataOwner.  
+
|Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
 
|-
 
|-
 
|DataOwner
 
|DataOwner
Line 289: Line 269:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Indentifier indicates the component responsible of issuing the evidence.  
+
|Identifies the Data Owner to whom the request for evidence is sent.
 
|-
 
|-
 
|RequestEvidenceIMItem  
 
|RequestEvidenceIMItem  
Line 295: Line 275:
 
|1..n
 
|1..n
 
|Y/Y
 
|Y/Y
−
|Cardinality 1..∞
+
|List of requested canonical evidence types
 
|}
 
|}
  
Line 315: Line 295:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifies DataOwner in format iso6523.<br />Define Party ID for all participants
+
|Identifies the DE4A participant (Data Evaluator or Data Owner) in iso6523 format. It defines Party Id for all participants. It must be unique.
−
MUST be UNIQUE
 
−
 
 
 
'''Format:''' {PEPPOL ParticipantIdentifierScheme}::{Domain Scheme}:{Party Id} → iso6523-actorid-upis::[0-9][0-9][0-9][0-9]:[A-Z0-9]{1,15}  
 
'''Format:''' {PEPPOL ParticipantIdentifierScheme}::{Domain Scheme}:{Party Id} → iso6523-actorid-upis::[0-9][0-9][0-9][0-9]:[A-Z0-9]{1,15}  
  
−
'''{PEPPOL ParticipantIdentifierScheme}:''' Must be a constant “iso6523-actorid-upis”  
+
* '''{PEPPOL ParticipantIdentifierScheme}:''' Must be the constant “iso6523-actorid-upis”  
 +
* '''{Domain Scheme}:''' Identifies ICD value, must be a 4-digit UNIQUE number in PEPPOL
 +
* '''{Party Id}:''' Identifies DE4A Partner, consisting of:
 +
** 2 letters for country
 +
** 2 digits for entity type → 00 if entity is a DE4A partner, 88 if not; for regional or local administrations, the entity type is 99
 +
** 7 digits for DE4A Partner. For regional or local administrations, it is the NUTS/LAU code without country letters and starting with as many zeros on the left as necessary until reaching 7 digits.
  
−
'''{Domain Scheme}:''' Identifies ICD value, must be 4 UNIQUE digits in PEPPOL
+
Example of the Spanish Municipality of San Sebastian with LAU code 20069: '''ES990020069'''
  
−
'''{Party Id}:''' Identifies DE4A Partner, consisting of:
+
Example of the Dutch Province of Groningen with NUTS code NL11: '''NL990000011'''
  
−
* 2 letters country
+
https://docs.peppol.eu/edelivery/policies/PEPPOL-EDN-Policy-for-use-of-identifiers-4.0-2019-01-28.pdf
−
* 2 digits entity type à 00 if entity is a DE4A partner, 88 if not
 
−
* 7 digits DE4A Partner 
 
−
 
 
−
For regional or local administrations, the entity type is 99 and the 7 digit number is the NUTS/LAU code without country letters and starting with as many zeros on the left as necessary until 7 digits.
 
−
 
 
−
Example Spanish Municipality of San Sebastian with LAU code 20069: '''ES990020069''' 
 
−
 
 
−
Example of Dutch Province of Groningen with NUTS code NL11: '''NL990000011''' 
 
  
−
https://docs.peppol.eu/edelivery/policies/PEPPOL-EDN-Policy-for-use-of-identifiers-4.0-2019-01-28.pdf
+
For further information on the Domain Scheme values, see the [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
  
 
|-
 
|-
Line 343: Line 318:
 
|1
 
|1
 
|Y/N
 
|Y/N
−
|Name of the agent Data Owner.  
+
|Name of the DE4A participant (Data Evaluator or Data Owner). Based on the schema "<nowiki>https://data.europe.eu/semanticassets/ns/cv/common/dataTypes-2.0.0#</nowiki>"
 
|-
 
|-
 
|RedirectUrl
 
|RedirectUrl
Line 349: Line 324:
 
|0..1
 
|0..1
 
|N/Y
 
|N/Y
−
|Redirect URL to Data Owner.  
+
|URL of the web page of origin. It is only filled in by the Data Evaluator in the context of the USI pattern, so that the Data Owner knows where to return the User once the preview has been completed in the DO portal.
 
|}
 
|}
  
Line 366: Line 341:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Unique evidence request ID
+
|Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
  
 
|-
 
|-
Line 373: Line 348:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Contains the identifying details of the person, company or representative to obtain the evidence.  
+
|Contains the identifying details of the person, company or representative to whom the evidence relates.
 
|-
 
|-
 
|CanonicalEvidenceTypeId
 
|CanonicalEvidenceTypeId
Line 379: Line 354:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifier of the canonical evidence type.<br />'''Format:'''  
+
|Identifier of the canonical evidence type.<br />'''Format:'''
−
 
+
* <nowiki>urn:de4a-eu:CanonicalEvidenceType</nowiki>::''evidenceID''
−
<nowiki>urn:dea4-eu:CanonicalEvidenceType</nowiki>::<canonical-evidence-type-idtoken>
 
−
 
 
−
'''Allowed values for <canonical-evidence-type-idtoken>:'''
 
  
−
* HigherEducationDiploma
+
The complete set of values for ''evidenceID'' is available at [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
−
* DomicileRegistrationEvidence
 
−
* BirthCertificate
 
−
* MarriageCertificate
 
−
* CompanyRegistration
 
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|RequestGrounds
 
|RequestGrounds
Line 396: Line 363:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Request grounds to request evidence.  
+
|Legal grounds justifying the request for evidence and supporting the applicant.
 
|-
 
|-
 
|AdditionalParameter  
 
|AdditionalParameter  
Line 419: Line 386:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Contains the identifying details of the person to obtain the evidence.  
+
|Contains the identifying details of the person to whom the evidence relates. Based on the schema "<nowiki>http://eidas.europa.eu/attributes/naturalperson</nowiki>".
  
 
|-
 
|-
Line 426: Line 393:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Contains the identifying details of the company to obtain the evidence.  
+
|Contains the identifying details of the company to which the evidence or event relates. Based on the schema "<nowiki>http://eidas.europa.eu/attributes/legalperson</nowiki>".
 
|-
 
|-
 
|DataSubjectRepresentative  
 
|DataSubjectRepresentative  
Line 432: Line 399:
 
|0..1
 
|0..1
 
|N/Y
 
|N/Y
−
|Contains the identifying details of the representative to obtain the evidence.  
+
|Contains the identifying details of the company representative to which the evidence or event relates. Based on the schema "<nowiki>http://eidas.europa.eu/attributes/naturalperson</nowiki>".
 
|}
 
|}
  
Line 468: Line 435:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Date of birth for the natural person.  
+
|Date of birth of the natural person.  
  
−
Format: '''YYYY-MM-DD'''  
+
Format: '''YYYY-MM-DD'''
 
|-
 
|-
 
|Gender
 
|Gender
Line 483: Line 450:
 
* Female  
 
* Female  
 
* Unspecified  
 
* Unspecified  
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|BitrhName
 
|BitrhName
Line 495: Line 461:
 
|0..1
 
|0..1
 
|N/N
 
|N/N
−
|Place of birth for a natural person.  
+
|Place of birth of the natural person.
 
|-
 
|-
 
|CurrentAddress
 
|CurrentAddress
Line 539: Line 505:
 
|0..1
 
|0..1
 
|N/N
 
|N/N
−
|VAT - VAT registration number.
+
|Value Addex Tax registration number
 
|-
 
|-
 
|TaxReference
 
|TaxReference
Line 545: Line 511:
 
|0..1
 
|0..1
 
|N/N
 
|N/N
−
|TAX-Ref - tax reference number.
+
|Tax reference number
 
|-
 
|-
 
|D-2012-17-EUIdentifier
 
|D-2012-17-EUIdentifier
Line 551: Line 517:
 
|0..1
 
|0..1
 
|N/N
 
|N/N
−
|D-2012/17/EU - the identifier used under directive 2012/17/EU  
+
|The identifier used under directive 2012/17/EU
 
|-
 
|-
 
|LEI
 
|LEI
Line 557: Line 523:
 
|0..1
 
|0..1
 
|N/N
 
|N/N
−
|Legal Entity Identifier.
+
|Legal Entity Identifier
 
|-
 
|-
 
|EORI
 
|EORI
Line 563: Line 529:
 
|0..1
 
|0..1
 
|N/N
 
|N/N
−
|Economic Operator Registration and Identification.
+
|Economic Operator Registration and Identification
 
|-
 
|-
 
|SEED
 
|SEED
Line 569: Line 535:
 
|0..1
 
|0..1
 
|N/N
 
|N/N
−
|System for Exchange of Excise Data.
+
|System for Exchange of Excise Data
 
|-
 
|-
 
|SIC
 
|SIC
Line 575: Line 541:
 
|0..1
 
|0..1
 
|N/N
 
|N/N
−
|Standard Industrial Classification.
+
|Standard Industrial Classification
 
|}
 
|}
  
Line 592: Line 558:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Permanent link allowing access to the system.  
+
|Permanent link to the european law that allows a DE to request the corresponding evidence, identified by the European Legislation Identifier (ELI).
  
 
|-
 
|-
Line 599: Line 565:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Consent allowing access to the system.  
+
|Explicit consent made by the User to allow the DE to request the appropriate evidence through the DE4A system. Requirement imposed by article 14 of the SDG Regulation.
−
 
 
−
Allowed values:
 
−
 
 
−
'''SDGR14'''
 
−
 
 
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|}
 
|}
  
Line 631: Line 591:
  
 
'''Allowed values:'''
 
'''Allowed values:'''
−
* Date → Date tye
+
* Date → Date type
 
* InputText → Input Text type
 
* InputText → Input Text type
 
* YesNo → Selector Yes/No type
 
* YesNo → Selector Yes/No type
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|Value
 
|Value
Line 652: Line 611:
 
!Mandatory Field / Label
 
!Mandatory Field / Label
 
!Description
 
!Description
−
|-
 
−
|RequestExtractMultiEvidenceIMType
 
−
|ResponseExtractMultiEvidenceType
 
−
|1
 
−
|Y/Y
 
−
|Root element
 
 
|-
 
|-
 
|RequestId
 
|RequestId
Line 663: Line 616:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Request message identifier
+
|Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
 
|-
 
|-
 
|Timestamp
 
|Timestamp
Line 669: Line 622:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Date and time when the message is created. Its value will not be changed when subsequent messages having this timestamp attribute are created.
+
|Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
 
|-
 
|-
 
|DataEvaluator
 
|DataEvaluator
Line 675: Line 628:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifier will be used to address the evidence back from the DataOwner.
+
|Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
 
|-
 
|-
 
|DataOwner
 
|DataOwner
Line 681: Line 634:
 
|1
 
|1
 
|N/Y
 
|N/Y
−
|Indentifier indicates the component responsible of issuing the evidence.
+
|Identifies the Data Owner to whom the request for evidence is sent.
 
|-
 
|-
 
|ResponseExtractEvidenceItem
 
|ResponseExtractEvidenceItem
Line 687: Line 640:
 
|1..n
 
|1..n
 
|Y/Y
 
|Y/Y
−
|Evidence requested  
+
|List of requested canonical evidence types
 
|}
 
|}
  
Line 707: Line 660:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Unique evidence request ID
+
|Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
  
 
|-
 
|-
Line 714: Line 667:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Contains the identifying details of the person, company or representative to obtain the evidence.
+
|Contains the identifying details of the person, company or representative to whom the evidence relates.
 
|-
 
|-
 
|CanonicalEvidenceTypeId
 
|CanonicalEvidenceTypeId
Line 720: Line 673:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifier of the canonical evidence type.  
+
|Identifier of the canonical evidence type.<br />'''Format:'''
 +
* <nowiki>urn:de4a-eu:CanonicalEvidenceType</nowiki>::''evidenceID''
  
−
'''Format:''' 
+
The complete set of values for ''evidenceID'' is available at [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
−
 
 
−
<nowiki>urn:dea4-eu:CanonicalEvidenceType</nowiki>::<canonical-evidence-type-idtoken> 
 
−
 
 
−
'''Allowed values for <canonical-evidence-type-idtoken>:'''  
 
−
 
 
−
* HigherEducationDiploma
 
−
* DomicileRegistrationEvidence
 
−
* BirthCertificate
 
−
* MarriageCertificate
 
−
* CompanyRegistration
 
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|CanonicalEvidence
 
|CanonicalEvidence
Line 739: Line 682:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Canonical Evidence obtained.  
+
|Evidence retrieved from the DO in its corresponding canonical format.
 
|-
 
|-
 
|DomesticEvidence
 
|DomesticEvidence
Line 745: Line 688:
 
|0..n
 
|0..n
 
|Y/Y
 
|Y/Y
−
|Contains the data of each domestic evidences obtained.  
+
|Contains the data for each piece of national evidence retrieved from the DO in the original format in which they are issued.
 
|-
 
|-
 
|Error
 
|Error
Line 751: Line 694:
 
|1..n
 
|1..n
 
|N/Y
 
|N/Y
−
|Contains the data for each error that occurred.  
+
|Contains a list with the descriptions of the errors if one or more have occurred.
 
|}
 
|}
  
Line 771: Line 714:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Indicates what type of evidence it is:  
+
|Indicates the format of the evidence:
−
 
 
−
'''OriginalIssuing:''' Original Evidence
 
  
−
'''MultinlingualFormIssuing:''' Multilingual evidence
+
* '''OriginalIssuing:''' Original format
 +
* '''MultinlingualFormIssuing:''' Multilingual format
  
 
|-
 
|-
Line 788: Line 730:
 
|1
 
|1
 
|Y/N
 
|Y/N
−
|Contains the language of the canonical evidence.<br />'''Values conform to <nowiki>RFC 3066</nowiki>, allowed values:'''<br />Conformity to ISO 639
+
|Contains the language of the canonical evidence.
−
Conformity to ISO 3166
+
'''Values conform to <nowiki>RFC 3066</nowiki>, allowed values:'''
  
−
Languages registered by the Internet Assigned Numbers Authority (IANA)  
+
* Conformity to ISO 639
 +
* Conformity to ISO 3166
 +
* Languages registered by the Internet Assigned Numbers Authority (IANA)  
  
 
Expression pattern: [a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})*  
 
Expression pattern: [a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})*  
−
 
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|EvidenceData
 
|EvidenceData
Line 801: Line 743:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Contains the domestic that the Data Owner system returns (in formats like XML, PDF, etc.) codified in B64.  
+
|Contains the domestic evidence that the Data Owner system returns (in formats like XML, PDF, etc.) codified in B64.
 
|-
 
|-
 
|AdditionalInfo
 
|AdditionalInfo
Line 807: Line 749:
 
|0..1
 
|0..1
 
|N/N
 
|N/N
−
|Contains additional information about domestic evidence.  
+
|Contains additional information about the domestic evidence.
 
|}
 
|}
  
Line 842: Line 784:
 
!Mandatory Field / Label
 
!Mandatory Field / Label
 
!Description
 
!Description
−
|-
 
−
|RequestExtractMultiEvidenceUSIType
 
−
|RequestExtractMultiEvidenceType
 
−
|1
 
−
|Y/Y
 
−
|Root element
 
 
|-
 
|-
 
|RequestId
 
|RequestId
Line 853: Line 789:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Request message identifier
+
|Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
 
|-
 
|-
 
|SpecificationId
 
|SpecificationId
Line 859: Line 795:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Version used and it will define the message structure.
+
|IEM version used.
 
|-
 
|-
 
|Timestamp
 
|Timestamp
Line 865: Line 801:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Date and time when the message is created. Its value will not be changed when subsequent messages having this timestamp attribute are created.
+
|Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
 
|-
 
|-
 
|ProcedureId
 
|ProcedureId
Line 871: Line 807:
 
|0..1
 
|0..1
 
|N/Y
 
|N/Y
−
|Metadata about a procedure or public service.
+
|Metadata about the procedure or public service the justifies the use of the DE4A OOTS.
 
|-
 
|-
 
|DataEvaluator
 
|DataEvaluator
Line 877: Line 813:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifier will be used to address the evidence back from the DataOwner.
+
|Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
 
|-
 
|-
 
|DataOwner
 
|DataOwner
Line 883: Line 819:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Indentifier indicates the component responsible of issuing the evidence.
+
|Identifies the Data Owner to whom the request for evidence is sent.
 
|-
 
|-
 
|RequestEvidenceUSIItem
 
|RequestEvidenceUSIItem
Line 889: Line 825:
 
|1..n
 
|1..n
 
|Y/Y
 
|Y/Y
−
|Evidence requested
+
|List of requested canonical evidence types
 
|}
 
|}
  
Line 909: Line 845:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Unique evidence request ID
+
|Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
  
 
|-
 
|-
Line 916: Line 852:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Contains the identifying details of the person, company or representative to obtain the evidence.
+
|Contains the identifying details of the person, company or representative to whom the evidence relates.
 
|-
 
|-
 
|CanonicalEvidenceTypeId
 
|CanonicalEvidenceTypeId
Line 922: Line 858:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifier of the canonical evidence type.
+
|Identifier of the canonical evidence type.<br />'''Format:'''
−
'''Format:'''  
+
* <nowiki>urn:de4a-eu:CanonicalEvidenceType</nowiki>::''evidenceID''
−
 
 
−
<nowiki>urn:dea4-eu:CanonicalEvidenceType</nowiki>::<canonical-evidence-type-idtoken><br />'''Allowed values for <canonical-evidence-type-idtoken>:'''
 
  
−
* HigherEducationDiploma
+
The complete set of values for ''evidenceID'' is available at [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
−
* DomicileRegistrationEvidence
 
−
* BirthCertificate
 
−
* MarriageCertificate
 
−
* CompanyRegistration
 
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|RequestGrounds
 
|RequestGrounds
Line 938: Line 867:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Request grounds to request evidence.
+
|Legal grounds justifying the request for evidence and supporting the applicant.
 
|-
 
|-
 
|AdditionalParameter
 
|AdditionalParameter
Line 950: Line 879:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Indicates the redirection url to return the user to the e-procedure portal of the data evaluator
+
|Indicates the redirection URL to return the User to the e-procedure portal of the Data Evaluator.
 
|}
 
|}
  
Line 962: Line 891:
 
!Mandatory Field / Label
 
!Mandatory Field / Label
 
!Description
 
!Description
−
|-
 
−
|RedirectUserType
 
−
|RedirectUserType
 
−
|1
 
−
|Y/Y
 
−
|Root element
 
 
|-
 
|-
 
|RequestId
 
|RequestId
Line 973: Line 896:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Request message identifier
+
|Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
 
|-
 
|-
 
|SpecificationId
 
|SpecificationId
Line 979: Line 902:
 
|1
 
|1
 
|Y
 
|Y
−
|Version used and it will define the message structure.
+
|IEM version used
 
|-
 
|-
 
|Timestamp
 
|Timestamp
Line 985: Line 908:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Date and time when the message is created. Its value will not be changed when subsequent messages having this timestamp attribute are created.
+
|Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
 
|-
 
|-
 
|DataEvaluator
 
|DataEvaluator
Line 991: Line 914:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifier will be used to address the evidence back from the DataOwner.
+
|Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
 
|-
 
|-
 
|DataOwner
 
|DataOwner
Line 997: Line 920:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Indentifier indicates the component responsible of issuing the evidence.
+
|Identifies the Data Owner to whom the request for evidence is sent.
 
|-
 
|-
 
|CanonicalEvidenceTypeId
 
|CanonicalEvidenceTypeId
Line 1,003: Line 926:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifier of the canonical evidence type.  
+
|Identifier of the canonical evidence type.<br />'''Format:'''
 +
* <nowiki>urn:de4a-eu:CanonicalEvidenceType</nowiki>::''evidenceID''
  
−
'''Format:''' 
+
The complete set of values for ''evidenceID'' is available at [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
−
 
 
−
<nowiki>urn:dea4-eu:CanonicalEvidenceType</nowiki>::<canonical-evidence-type-idtoken> 
 
−
 
 
−
'''Allowed values for <canonical-evidence-type-idtoken>:'''  
 
−
 
 
−
* HigherEducationDiploma
 
−
* DomicileRegistrationEvidence
 
−
* BirthCertificate
 
−
* MarriageCertificate
 
−
* CompanyRegistration
 
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|RedirectURL
 
|RedirectURL
Line 1,022: Line 935:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Indicates the redirection url for the user to choose and preview the evidence.
+
|Indicates the URL of the DO portal where to send the User to choose and preview the evidence.
 
|-
 
|-
 
|Error
 
|Error
Line 1,028: Line 941:
 
|0..n
 
|0..n
 
|N/Y
 
|N/Y
−
|Contains the response error.
+
|Contains the description of the error if one has occurred.
 
|}
 
|}
  
Line 1,043: Line 956:
 
!Mandatory Field / Label
 
!Mandatory Field / Label
 
!Description
 
!Description
−
|-
 
−
|RequestEventSubscriptionType
 
−
|RequestEventSubscriptionType
 
−
|1
 
−
|Y/Y
 
−
|Root element
 
 
|-
 
|-
 
|RequestId
 
|RequestId
Line 1,054: Line 961:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Request message identifier
+
|Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
 
|-
 
|-
 
|SpecificationId
 
|SpecificationId
Line 1,060: Line 967:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Version used and it will define the message structure.
+
|IEM version used
 
|-
 
|-
 
|Timestamp
 
|Timestamp
Line 1,066: Line 973:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Date and time when the message is created. Its value will not be changed when subsequent messages having this timestamp attribute are created.
+
|Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
 
|-
 
|-
 
|ProcedureId
 
|ProcedureId
Line 1,072: Line 979:
 
|0..1
 
|0..1
 
|N/Y
 
|N/Y
−
|Metadata about a procedure or public service.
+
|Metadata about the procedure or public service the justifies the use of the DE4A OOTS.
 
|-
 
|-
 
|DataEvaluator
 
|DataEvaluator
Line 1,078: Line 985:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Identifier will be used to address the evidence back from the DataOwner.
+
|Identifies the Data Evaluator who is making the request for subscription. This information is also used to route the responses from the Data Owner to the Data Evaluator.
 
|-
 
|-
 
|DataOwner
 
|DataOwner
Line 1,084: Line 991:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Indentifier indicates the component responsible of issuing the evidence.
+
|Identifies the Data Owner to whom the request for subscription is sent.
 
|-
 
|-
 
|EventSubscripRequestItem
 
|EventSubscripRequestItem
Line 1,090: Line 997:
 
|1..n
 
|1..n
 
|Y/Y
 
|Y/Y
−
|Evidence requested
+
|List of subscriptions requested
 
|}
 
|}
  
Line 1,110: Line 1,017:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Unique evidence request ID
+
|Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
 
|-
 
|-
 
|DataRequestSubject
 
|DataRequestSubject
Line 1,116: Line 1,023:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Contains the identifying details of the person, company or representative to obtain the evidence.
+
|Contains the identifying details of the person, company or representative to whom the evidence relates.
 
|-
 
|-
 
|CanonicalEventCatalogUri
 
|CanonicalEventCatalogUri
Line 1,122: Line 1,029:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|
+
|Identifier of the canonical event catalogue.<br />'''Format:'''
 +
 
 +
* <nowiki>urn:de4a-eu:CanonicalEventCatalogueType</nowiki>::''catalogueID''
 +
 
 +
The complete set of values for ''catalogueID'' is available at [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
 
|-
 
|-
 
|SubscriptionPeriod
 
|SubscriptionPeriod
Line 1,128: Line 1,039:
 
|0..1
 
|0..1
 
|Y/Y
 
|Y/Y
−
|Period dates of the subscription
+
|Period of time for which the subscription will last.
 
|}
 
|}
  
Line 1,145: Line 1,056:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|Subscription Start Date
+
|Subscription start date
 
|-
 
|-
 
|EndDate
 
|EndDate
Line 1,151: Line 1,062:
 
|0..1
 
|0..1
 
|N/Y
 
|N/Y
−
|Subscription End Date
+
|Subscription end date
 
|}
 
|}
  
Line 1,163: Line 1,074:
 
!Mandatory Field / Label
 
!Mandatory Field / Label
 
!Description
 
!Description
−
|-
 
−
|ResponseEventSubscriptionType
 
−
|ResponseEventSubscriptionType
 
−
|1
 
−
|Y
 
−
|Root element
 
 
|-
 
|-
 
|RequestId
 
|RequestId
Line 1,174: Line 1,079:
 
|1
 
|1
 
|Y
 
|Y
−
|Request message identifier
+
|Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
 
|-
 
|-
 
|Timestamp
 
|Timestamp
Line 1,180: Line 1,085:
 
|1
 
|1
 
|Y
 
|Y
−
|Date and time when the message is created. Its value will not be changed when subsequent messages having this timestamp attribute are created.
+
|Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
 
|-
 
|-
 
|DataEvaluator
 
|DataEvaluator
Line 1,186: Line 1,091:
 
|1
 
|1
 
|Y
 
|Y
−
|Identifier will be used to address the evidence back from the DataOwner.
+
|Identifies the Data Evaluator who is making the request for subscription . This information is also used to route the responses from the Data Owner to the Data Evaluator.
 
|-
 
|-
 
|DataOwner
 
|DataOwner
Line 1,192: Line 1,097:
 
|1
 
|1
 
|Y
 
|Y
−
|Indentifier indicates the component responsible of issuing the evidence.
+
|Identifies the Data Owner to whom the request for subscription is sent.
 
|-
 
|-
 
|ResponseEventSubscriptionItem
 
|ResponseEventSubscriptionItem
Line 1,198: Line 1,103:
 
|1..n
 
|1..n
 
|Y
 
|Y
−
|Evidence requested
+
|List of subscriptions requested
 
|}
 
|}
  
Line 1,218: Line 1,123:
 
|1
 
|1
 
|Y
 
|Y
−
|Unique evidence request ID
+
|Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
 
|-
 
|-
 
|CanonicalEventCatalogUri
 
|CanonicalEventCatalogUri
Line 1,224: Line 1,129:
 
|1
 
|1
 
|Y
 
|Y
−
|
+
|Identifier of the canonical event catalogue.<br />'''Format:'''
 +
 
 +
* <nowiki>urn:de4a-eu:CanonicalEventCatalogueType</nowiki>::''catalogueID''
 +
 
 +
The complete set of values for ''catalogueID'' is available at [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
 
|-
 
|-
 
|SubscriptionPeriod
 
|SubscriptionPeriod
Line 1,230: Line 1,139:
 
|1
 
|1
 
|Y
 
|Y
−
|Period dates of the subscription
+
|Confirmation of the period of time for which the subscription will last.
 
|}
 
|}
  
Line 1,242: Line 1,151:
 
!Mandatory Field / Label
 
!Mandatory Field / Label
 
!Description
 
!Description
−
|-
 
−
|EventNotificationType
 
−
|EventNotificationType
 
−
|1
 
−
|Y
 
−
|Root element
 
 
|-
 
|-
 
|NotificationId
 
|NotificationId
Line 1,253: Line 1,156:
 
|1
 
|1
 
|Y
 
|Y
−
|Request notification identifier
+
|Event notification identifier (UUID format)
 
|-
 
|-
 
|Timestamp
 
|Timestamp
Line 1,259: Line 1,162:
 
|1
 
|1
 
|Y
 
|Y
−
|Date and time when the message is created. Its value will not be changed when subsequent messages having this timestamp attribute are created.
+
|Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
 
|-
 
|-
 
|DataEvaluator
 
|DataEvaluator
Line 1,265: Line 1,168:
 
|1
 
|1
 
|Y
 
|Y
−
|Identifier will be used to address the evidence back from the DataOwner.
+
|Identifies the Data Evaluator to whom the event notification is sent.
 
|-
 
|-
 
|DataOwner
 
|DataOwner
Line 1,271: Line 1,174:
 
|1
 
|1
 
|Y
 
|Y
−
|Indentifier indicates the component responsible of issuing the evidence.
+
|Identifies the Data Owner that sends the event notification message.
 
|-
 
|-
 
|EventNotificationItem
 
|EventNotificationItem
Line 1,277: Line 1,180:
 
|1..n
 
|1..n
 
|Y
 
|Y
−
|Evidence requested
+
|List of event notifications
 
|}
 
|}
  
Line 1,297: Line 1,200:
 
|1
 
|1
 
|Y
 
|Y
−
|Unique notification ID
+
|Identifier of each item of the notification (UUID format)
 
|-
 
|-
 
|EventId
 
|EventId
Line 1,303: Line 1,206:
 
|1
 
|1
 
|Y
 
|Y
−
|Unique event ID
+
|Identifier of the event that triggered the notification in the DO system.
 
|-
 
|-
 
|EventSubject
 
|EventSubject
Line 1,309: Line 1,212:
 
|1
 
|1
 
|Y
 
|Y
−
|Contains the identifying details of the person, company or representative to obtain the evidence.
+
|Contains the identifying details of the company or representative to whom the event notification relates.
 
|-
 
|-
 
|CanonicalEventCatalogUri
 
|CanonicalEventCatalogUri
Line 1,315: Line 1,218:
 
|1
 
|1
 
|Y
 
|Y
−
|
+
|Identifier of the canonical event catalogue.<br />'''Format:'''
 +
 
 +
* <nowiki>urn:de4a-eu:CanonicalEventCatalogueType</nowiki>::''catalogueID''
 +
 
 +
The complete set of values for ''catalogueID'' is available at [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
 
|-
 
|-
 
|EventDate
 
|EventDate
Line 1,321: Line 1,228:
 
|1
 
|1
 
|Y
 
|Y
−
|Date of the event notification
+
|Date when the event occurred.
 
|-
 
|-
 
|RelatedEventSubject
 
|RelatedEventSubject
Line 1,327: Line 1,234:
 
|0..n
 
|0..n
 
|Y
 
|Y
−
|
+
|Contains the identification data of possible subjects also related to or afected by this event.
 
|}
 
|}
  
Line 1,339: Line 1,246:
 
!Mandatory Field / Label
 
!Mandatory Field / Label
 
!Description
 
!Description
−
|-
 
−
|RequestExtractMultiEvidenceLUType
 
−
|RequestExtractMultiEvidenceLUType
 
−
|1
 
−
|Y
 
−
|Root element
 
 
|-
 
|-
 
|RequestId
 
|RequestId
Line 1,350: Line 1,251:
 
|1
 
|1
 
|Y
 
|Y
−
|Request message identifier
+
|Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
 
|-
 
|-
 
|SpecificationId
 
|SpecificationId
Line 1,356: Line 1,257:
 
|1
 
|1
 
|Y
 
|Y
−
|Version used and it will define the message structure.
+
|IEM version used
 
|-
 
|-
 
|Timestamp
 
|Timestamp
Line 1,362: Line 1,263:
 
|1
 
|1
 
|Y
 
|Y
−
|Date and time when the message is created. Its value will not be changed when subsequent messages having this timestamp attribute are created.
+
|Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
 
|-
 
|-
 
|ProcedureId
 
|ProcedureId
Line 1,368: Line 1,269:
 
|0..1
 
|0..1
 
|N
 
|N
−
|Metadata about a procedure or public service.
+
|Metadata about the procedure or public service the justifies the use of the DE4A OOTS.
 
|-
 
|-
 
|DataEvaluator
 
|DataEvaluator
Line 1,374: Line 1,275:
 
|1
 
|1
 
|Y
 
|Y
−
|Identifier will be used to address the evidence back from the DataOwner.
+
|Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
 
|-
 
|-
 
|DataOwner
 
|DataOwner
Line 1,380: Line 1,281:
 
|1
 
|1
 
|Y
 
|Y
−
|Indentifier indicates the component responsible of issuing the evidence.
+
|Identifies the Data Owner to whom the request for evidence is sent.
 
|-
 
|-
 
|RequestEvidenceLUItem
 
|RequestEvidenceLUItem
Line 1,386: Line 1,287:
 
|1..n
 
|1..n
 
|Y
 
|Y
−
|Evidence requested
+
|List of requested canonical evidence types
 
|}
 
|}
  
Line 1,406: Line 1,307:
 
|1
 
|1
 
|Y
 
|Y
−
|Unique evidence request ID
+
|Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
  
 
|-
 
|-
Line 1,413: Line 1,314:
 
|1
 
|1
 
|Y
 
|Y
−
|Contains the identifying details of the person, company or representative to obtain the evidence.
+
|Contains the identifying details of the person, company or representative to whom the evidence relates.
 
|-
 
|-
 
|CanonicalEvidenceTypeId
 
|CanonicalEvidenceTypeId
Line 1,419: Line 1,320:
 
|1
 
|1
 
|Y
 
|Y
−
|Identifier of the canonical evidence type.
+
|Identifier of the canonical evidence type.<br />'''Format:'''
−
'''Format:'''  
+
* <nowiki>urn:de4a-eu:CanonicalEvidenceType</nowiki>::''evidenceID''
  
−
<nowiki>urn:dea4-eu:CanonicalEvidenceType</nowiki>::<canonical-evidence-type-idtoken><br />'''Allowed values for <canonical-evidence-type-idtoken>:'''
+
The complete set of values for ''evidenceID'' is available at [https://github.com/de4a-wp5/de4a-codelists codelists] on the WP5 GitHub.
−
* HigherEducationDiploma
 
−
* DomicileRegistrationEvidence
 
−
* BirthCertificate
 
−
* MarriageCertificate
 
−
* CompanyRegistration
 
−
See [https://github.com/de4a-wp5/de4a-codelists codelists] in github for additional information.
 
 
|-
 
|-
 
|RequestGrounds
 
|RequestGrounds
Line 1,434: Line 1,329:
 
|1
 
|1
 
|Y
 
|Y
−
|Request grounds to request evidence.
+
|Legal grounds justifying the request for evidence and supporting the applicant.
 
|-
 
|-
 
|AdditionalParameter
 
|AdditionalParameter
Line 1,446: Line 1,341:
 
|1
 
|1
 
|Y
 
|Y
−
|Reference of the notification event
+
|NotificationId of the event notification this Lookup request is based on.
 
|}
 
|}
  
Line 1,463: Line 1,358:
 
|1
 
|1
 
|Y/Y
 
|Y/Y
−
|
+
|Value returned in case no error occurred.
 
|-
 
|-
 
|Error
 
|Error
Line 1,469: Line 1,364:
 
|0..n
 
|0..n
 
|N/Y
 
|N/Y
−
|Error
+
|Data type returned in case of error.
 
|}
 
|}
 
=== Schema XSD ===
 
=== Schema XSD ===
 
[https://github.com/de4a-wp5/xml-schemas/blob/master/XSD/de4a/common-types.xsd#L366 common-types.xsd]
 
[https://github.com/de4a-wp5/xml-schemas/blob/master/XSD/de4a/common-types.xsd#L366 common-types.xsd]

Latest revision as of 12:49, 5 January 2023

This document contains a basic detail about the messages exchanged in every step of the patterns for this iteration. More detailed information is available in the schema definition files.

RequestLookupRoutingInformationType

All the necessary parameters will be in the URL. It will be a comma-separated canonical evidence identifier collection (up to 20) followed by the AtuCode.

Detailed information is available in ‘IAL Technical Design’ Document.

ResponseLookupRoutingInformationType

Name Type Cardinality Mandatory Field / Label Description
ResponseItem ResponseItemType 1..n Y/Y Contains a list of available sources obtained.
Error ErrorType 1..n Y/Y Contains a list with the descriptions of the errors if one or more have occurred.

Schema XSD

IAL.xsd

ResponseItemType

Location: //ResponseLookupRoutingInformation/ResponseItemType
Name Type Cardinality Mandatory Field / Label Description
ResponsePerCountry ResponsePerCountryType 1..n Y/Y Contains the data for each source obtained.

ResponsePerCountryType

Location: //ResponseLookupRoutingInformation/ResponseItemType/ResponsePerCountryType
Name Type Cardinality Mandatory Field / Label Description
CountryCode String 1 Y/Y The two-letter code of the DP country.

Format: ISO 3166-1 alfa-2

https://www.iso.org/obp/ui/

Provision ProvisionType 1..n Y/Y Contains the data of each possible provision.

ProvisionType

Location: //ResponseLookupRoutingInformation/ResponseItemType/ResponsePerCountryType/Provision
ComplexType ProvisionType.jpg
Name Type Cardinality Mandatory Field / Label Description
AtuLevel String 1 N/Y Level of Administrative Territorial Unit.

Allowed values:

  • nuts0: National level
  • nuts1: Regional/Province level
  • nuts2: Regional/Province level
  • nuts3: Regional/Province level
  • lau: Local level
  • edu: Educational level
AtuCode String 1 N/Y Code of the Administrative Territorial Unit.

Allowed values:

  • "ISO 3166-1 alfa-2" for nuts0
  • "Region" for nuts1-3
  • "Municipality" for lau
  • "Educational Organization" for edu
AtuLatinName String 1 N/Y Name of the Administrative Territorial Unit.
DataOwnerId anyURI 1 N/Y Identifies the Data Owner in iso6523 format. It defines Party Id for all participants. It must be unique.

Format: {PEPPOL ParticipantIdentifierScheme}::{Domain Scheme}:{Party Id} → iso6523-actorid-upis::[0-9][0-9][0-9][0-9]:[A-Z0-9]{1,15}

  • {PEPPOL ParticipantIdentifierScheme}: Must be the constant “iso6523-actorid-upis”
  • {Domain Scheme}: Identifies ICD value, must be a 4-digit UNIQUE number in PEPPOL
  • {Party Id}: Identifies DE4A Partner, consisting of:
    • 2 letters for country
    • 2 digits for entity type → 00 if entity is a DE4A partner, 88 if not; for regional or local administrations, the entity type is 99
    • 7 digits for DE4A Partner. For regional or local administrations, it is the NUTS/LAU code without country letters and starting with as many zeros on the left as necessary until reaching 7 digits.

Example of the Spanish Municipality of San Sebastian with LAU code 20069: ES990020069

Example of the Dutch Province of Groningen with NUTS code NL11: NL990000011

https://docs.peppol.eu/edelivery/policies/PEPPOL-EDN-Policy-for-use-of-identifiers-4.0-2019-01-28.pdf

For further information on the Domain Scheme values, see the codelists on the WP5 GitHub.

DataOwnerPrefLabel String 1 N/Y Name of the issuing DO from which the evidence is obtained.
ParameterSet ParameterSetType 0..n Y/Y Contains a list of necessary parameters for the requested evidence.

ParameterSetType

Location: //ResponseLookupRoutingInformation/ResponseItemType/ResponsePerCountryType/Provision/ProvisionType
Name Type Cardinality Mandatory Field / Label Description
Title String 1 Y/Y Name of the required set of parameters for the requested evidence.
Parameter ParameterType 1..n Y/Y Contains the data for each necessary parameter of the requested evidence.

ParameterType

Location: //ResponseLookupRoutingInformation/AvailableSources/Source/ProvisionItems/ProvisionItem/ParameterSet
ComplexType ParameterType.jpg
Name Type Cardinality Mandatory Field / Label Description
Name String 1 Y/Y Name of the parameter
Optional Boolean 1 Y/Y Indicates whether the parameter is optional or not

ErrorType

Location: //ResponseLookupRoutingInformation
ComplexType ErrorType.jpg
Name Type Cardinality Mandatory Field / Label Description
Code String 1 Y/Y Code of the error occurred. See DE4A Logs and error messages it2
Text String 1 Y/Y Text defining the above code. See DE4A Logs and error messages it2

RequestExtractMultiEvidenceIMType

ComplexType RequestExtractMultiEvidenceIMType.jpg 
Location: //RequestExtractMultiEvidenceIMType
Name Type Cardinality Mandatory Field / Label Description
RequestId String 1 Y/Y Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
SpecificationId String 1 Y/Y IEM version used
Timestamp Date 1 Y/Y Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
ProcedureId String 1 N/Y Metadata about the procedure or public service the justifies the use of the DE4A OOTS.
DataEvaluator AgentType 1 Y/Y Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
DataOwner AgentType 1 Y/Y Identifies the Data Owner to whom the request for evidence is sent.
RequestEvidenceIMItem RequestEvidenceItemType 1..n Y/Y List of requested canonical evidence types

Schema XSD

common-types.xsd

AgentType

ComplexType AgentType.jpg 
Location: //RequestExtractMultiEvidenceIMType/AgentType
Name Type Cardinality Mandatory Field / Label Description
AgentUrn anyURI 1 Y/Y Identifies the DE4A participant (Data Evaluator or Data Owner) in iso6523 format. It defines Party Id for all participants. It must be unique.

Format: {PEPPOL ParticipantIdentifierScheme}::{Domain Scheme}:{Party Id} → iso6523-actorid-upis::[0-9][0-9][0-9][0-9]:[A-Z0-9]{1,15}

  • {PEPPOL ParticipantIdentifierScheme}: Must be the constant “iso6523-actorid-upis”
  • {Domain Scheme}: Identifies ICD value, must be a 4-digit UNIQUE number in PEPPOL
  • {Party Id}: Identifies DE4A Partner, consisting of:
    • 2 letters for country
    • 2 digits for entity type → 00 if entity is a DE4A partner, 88 if not; for regional or local administrations, the entity type is 99
    • 7 digits for DE4A Partner. For regional or local administrations, it is the NUTS/LAU code without country letters and starting with as many zeros on the left as necessary until reaching 7 digits.

Example of the Spanish Municipality of San Sebastian with LAU code 20069: ES990020069

Example of the Dutch Province of Groningen with NUTS code NL11: NL990000011

https://docs.peppol.eu/edelivery/policies/PEPPOL-EDN-Policy-for-use-of-identifiers-4.0-2019-01-28.pdf

For further information on the Domain Scheme values, see the codelists on the WP5 GitHub.

AgentName String 1 Y/N Name of the DE4A participant (Data Evaluator or Data Owner). Based on the schema "https://data.europe.eu/semanticassets/ns/cv/common/dataTypes-2.0.0#"
RedirectUrl String 0..1 N/Y URL of the web page of origin. It is only filled in by the Data Evaluator in the context of the USI pattern, so that the Data Owner knows where to return the User once the preview has been completed in the DO portal.

RequestEvidenceItemType

Location: //RequestExtractMultiEvidenceIMType/RequestEvidenceItemType
ComplexType RequestEvidenceItemType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestItemId String 1 Y/Y Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
DataRequestSubject DataRequestSubjectCVType 1 Y/Y Contains the identifying details of the person, company or representative to whom the evidence relates.
CanonicalEvidenceTypeId String 1 Y/Y Identifier of the canonical evidence type.
Format:
  • urn:de4a-eu:CanonicalEvidenceType::evidenceID

The complete set of values for evidenceID is available at codelists on the WP5 GitHub.

RequestGrounds RequestGroundsType 1 Y/Y Legal grounds justifying the request for evidence and supporting the applicant.
AdditionalParameter AdditionalParameterType 0..n N/Y Contains each additional parameter necessary to request the evidence.

DataRequestSubjectCVType

Location: //RequestExtractMultiEvidenceIMType/RequestEvidenceItemType/DataRequestSubject
ComplexType DataRequestSubjectCVType.jpg
Name Type Cardinality Mandatory Field / Label Description
DataSubjectPerson NaturalPersonIdentifierType 1 Y/Y Contains the identifying details of the person to whom the evidence relates. Based on the schema "http://eidas.europa.eu/attributes/naturalperson".
DataSubjectCompany LegalPersonIdentifierType 1 Y/Y Contains the identifying details of the company to which the evidence or event relates. Based on the schema "http://eidas.europa.eu/attributes/legalperson".
DataSubjectRepresentative NaturalPersonIdentifierType 0..1 N/Y Contains the identifying details of the company representative to which the evidence or event relates. Based on the schema "http://eidas.europa.eu/attributes/naturalperson".

NaturalPersonIdentifierType

Location: //RequestExtractMultiEvidenceIMType/RequestEvidenceItemType/DataRequestSubject/NaturalPersonIdentifierType
ComplexType NaturalPersonIdentifierType.jpg
Name Type Cardinality Mandatory Field / Label Description
PersonIdentifier String 1 Y/N Unique identifier for the natural person as defined by the eIDAS Regulation.
FirstName String 1 Y/N Current given names of the natural person.
FamilyName String 1 Y/N Current family name of the natural person.
DateOfBirth Date 1 Y/Y Date of birth of the natural person.

Format: YYYY-MM-DD

Gender String 0..1 N/Y Gender of the natural person.

Allowed values:

  • Male
  • Female
  • Unspecified
BitrhName String 0..1 N/N First name(s) and family name(s) of the natural person at birth.
PlaceOfBirth String 0..1 N/N Place of birth of the natural person.
CurrentAddress String 0..1 N/N Current address of the natural person as a base64 encoded string.

LegalPersonIdentifierType

Location: //RequestExtractMultiEvidenceIMType/RequestEvidenceItemType/DataRequestSubject/LegalPersonIdentifierType
ComplexType LegalPersonIdentifierType.jpg
Name Type Cardinality Mandatory Field / Label Description
LegalPersonIdentifier String 1 Y/N Unique identifier for the legal person as defined by the eIDAS Regulation.
LegalName String 1 Y/N Current legal name for the legal person or organisation.
LegalAddress String 0..1 N/N The address the legal person has registered with the MS authority or operating address if not registered.  

For a company this should be the registered address within the MS issuing the eID as a base64 encoded string.

VATRegistration String 0..1 N/N Value Addex Tax registration number
TaxReference String 0..1 N/N Tax reference number
D-2012-17-EUIdentifier String 0..1 N/N The identifier used under directive 2012/17/EU
LEI String 0..1 N/N Legal Entity Identifier
EORI String 0..1 N/N Economic Operator Registration and Identification
SEED String 0..1 N/N System for Exchange of Excise Data
SIC String 0..1 N/N Standard Industrial Classification

RequestGroundsType

Location: //RequestExtractMultiEvidenceIMType/RequestEvidenceItemType/RequestGrounds
ComplexType RequestGroundsType.jpg
Name Type Cardinality Mandatory Field / Label Description
LawELIPermanentLink anyURI 1 Y/Y Permanent link to the european law that allows a DE to request the corresponding evidence, identified by the European Legislation Identifier (ELI).
ExplicitRequest token 1 Y/Y Explicit consent made by the User to allow the DE to request the appropriate evidence through the DE4A system. Requirement imposed by article 14 of the SDG Regulation.

AdditionalParameterType

Location: //RequestExtractMultiEvidenceIMType/RequestEvidenceItemType/AdditionalPatameter
Name Type Cardinality Mandatory Field / Label Description
Label String 1 Y/Y Label identifying the required parameter.
Type String 1 Y/Y Type of the required parameter.

Allowed values:

  • Date → Date type
  • InputText → Input Text type
  • YesNo → Selector Yes/No type
Value String 1 Y/Y Value of the required parameter.

ResponseExtractMultiEvidenceType

ComplexType ResponseExtractMultiEvidenceType.jpg 
Location: //ResponseExtractMultiEvidenceType
Name Type Cardinality Mandatory Field / Label Description
RequestId String 1 Y/Y Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
Timestamp Date 1 Y/Y Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
DataEvaluator AgentType 1 Y/Y Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
DataOwner AgentType 1 N/Y Identifies the Data Owner to whom the request for evidence is sent.
ResponseExtractEvidenceItem ResponseExtractEvidenceItemType 1..n Y/Y List of requested canonical evidence types

Schema XSD

common-types.xsd

ResponseExtractEvidenceItemType

Location: //ResponseExtractMultiEvidenceType/ResponseExtractEvidenceItem
ComplexType ResponseExtractEvidenceItemType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestItemId String 1 Y/Y Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
DataRequestSubject DataRequestSubjectCVType 1 Y/Y Contains the identifying details of the person, company or representative to whom the evidence relates.
CanonicalEvidenceTypeId String 1 Y/Y Identifier of the canonical evidence type.
Format:
  • urn:de4a-eu:CanonicalEvidenceType::evidenceID

The complete set of values for evidenceID is available at codelists on the WP5 GitHub.

CanonicalEvidence CanonicalEvidenceType 1 Y/Y Evidence retrieved from the DO in its corresponding canonical format.
DomesticEvidence DomesticEvidenceType 0..n Y/Y Contains the data for each piece of national evidence retrieved from the DO in the original format in which they are issued.
Error ErrorType 1..n N/Y Contains a list with the descriptions of the errors if one or more have occurred.

CanonicalEvidenceType

Location: //ResponseExtractMultiEvidenceType/ResponseExtractEvidenceItem/CanonicalEvidence
ComplexType CanonicalEvidenceType.jpg

DomesticEvidenceType

Location: //ResponseExtractMultiEvidenceType/ResponseExtractEvidenceItem/DomesticEvidence
Name Type Cardinality Mandatory Field / Label Description
IssuingType Token 1 Y/Y Indicates the format of the evidence:
  • OriginalIssuing: Original format
  • MultinlingualFormIssuing: Multilingual format
MimeType normalizedString 1 Y/Y Contains the MIME Type of the canonical evidence.
https://docs.oasis-open.org/ubl/os-UBL-2.1/cva/UBL-DefaultDTQ-2.1.html#d4e1
DataLanguage language 1 Y/N Contains the language of the canonical evidence.

Values conform to RFC 3066, allowed values:

  • Conformity to ISO 639
  • Conformity to ISO 3166
  • Languages registered by the Internet Assigned Numbers Authority (IANA)

Expression pattern: [a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})*

EvidenceData base64Binary 1 Y/Y Contains the domestic evidence that the Data Owner system returns (in formats like XML, PDF, etc.) codified in B64.
AdditionalInfo TextType 0..1 N/N Contains additional information about the domestic evidence.

TextType

Location: //ResponseExtractMultiEvidenceType/ResponseExtractEvidenceItem/DomesticEvidence/AdditionalInfo
Name Type Cardinality Mandatory Field / Label Description
languageID language 0..1 N/Y The identifier of the language used in the content.
languageLocaleID normalizedString 0..1 N/Y The identification of the locale of the language.

RequestExtractMultiEvidenceUSIType

Location: //ResponseExtractMultiEvidenceUSIType
ComplexType RequestExtractMultiEvidenceUSIType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestId String 1 Y/Y Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
SpecificationId String 1 Y/Y IEM version used.
Timestamp Date 1 Y/Y Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
ProcedureId String 0..1 N/Y Metadata about the procedure or public service the justifies the use of the DE4A OOTS.
DataEvaluator AgentType 1 Y/Y Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
DataOwner AgentType 1 Y/Y Identifies the Data Owner to whom the request for evidence is sent.
RequestEvidenceUSIItem RequestEvidenceUSIItemType 1..n Y/Y List of requested canonical evidence types

Schema XSD

common-types.xsd

RequestExtractMultiEvidenceType

Location: //ResponseExtractMultiEvidenceUSIType/RequestEvidenceUSIItem
ComplexType RequestEvidenceUSIItemType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestItemId String 1 Y/Y Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
DataRequestSubject DataRequestSubjectCVType 1 Y/Y Contains the identifying details of the person, company or representative to whom the evidence relates.
CanonicalEvidenceTypeId String 1 Y/Y Identifier of the canonical evidence type.
Format:
  • urn:de4a-eu:CanonicalEvidenceType::evidenceID

The complete set of values for evidenceID is available at codelists on the WP5 GitHub.

RequestGrounds RequestGrounds 1 Y/Y Legal grounds justifying the request for evidence and supporting the applicant.
AdditionalParameter AdditionalParameterType 0..n N/Y Contains each additional parameter necessary to request the evidence.
DataEvaluatorURL anyUri 1 Y/Y Indicates the redirection URL to return the User to the e-procedure portal of the Data Evaluator.

RedirectUserType

Location: //RedirectUserType
ComplexType RedirectUserType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestId String 1 Y/Y Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
SpecificationId String 1 Y IEM version used
Timestamp Date 1 Y/Y Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
DataEvaluator AgentType 1 Y/Y Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
DataOwner AgentType 1 Y/Y Identifies the Data Owner to whom the request for evidence is sent.
CanonicalEvidenceTypeId String 1 Y/Y Identifier of the canonical evidence type.
Format:
  • urn:de4a-eu:CanonicalEvidenceType::evidenceID

The complete set of values for evidenceID is available at codelists on the WP5 GitHub.

RedirectURL anyURI 1 Y/Y Indicates the URL of the DO portal where to send the User to choose and preview the evidence.
Error ErrorType 0..n N/Y Contains the description of the error if one has occurred.

Schema XSD

common-types.xsd

RequestEventSubscriptionType

Location: //RequestEventSubscriptionType
ComplexType RequestEventSubscriptionType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestId String 1 Y/Y Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
SpecificationId String 1 Y/Y IEM version used
Timestamp Date 1 Y/Y Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
ProcedureId String 0..1 N/Y Metadata about the procedure or public service the justifies the use of the DE4A OOTS.
DataEvaluator AgentType 1 Y/Y Identifies the Data Evaluator who is making the request for subscription. This information is also used to route the responses from the Data Owner to the Data Evaluator.
DataOwner AgentType 1 Y/Y Identifies the Data Owner to whom the request for subscription is sent.
EventSubscripRequestItem EventSubscripRequestItemType 1..n Y/Y List of subscriptions requested

Schema XSD

common-types.xsd

EventSubscripRequestItemType

Location: //RequestEventSubscriptionType/EventSubscripRequestItem
ComplexType EventSubscripRequestItemType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestItemId string 1 Y/Y Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
DataRequestSubject DataRequestSubjectCVType 1 Y/Y Contains the identifying details of the person, company or representative to whom the evidence relates.
CanonicalEventCatalogUri anyUri 1 Y/Y Identifier of the canonical event catalogue.
Format:
  • urn:de4a-eu:CanonicalEventCatalogueType::catalogueID

The complete set of values for catalogueID is available at codelists on the WP5 GitHub.

SubscriptionPeriod TimePeriodType 0..1 Y/Y Period of time for which the subscription will last.

TimePeriodType

Location: //RequestEventSubscriptionType/EventSubscripRequestItem/SubscriptionPeriod
ComplexType TimePeriodType.jpg
Name Type Cardinality Mandatory Field / Label Description
StartDate dateTime 1 Y/Y Subscription start date
EndDate dateTime 0..1 N/Y Subscription end date

ResponseEventSubscriptionType

Location: //ResponseEventSubscriptionType
ComplexType ResponseEventSubscriptionType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestId String 1 Y Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
Timestamp Date 1 Y Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
DataEvaluator AgentType 1 Y Identifies the Data Evaluator who is making the request for subscription . This information is also used to route the responses from the Data Owner to the Data Evaluator.
DataOwner AgentType 1 Y Identifies the Data Owner to whom the request for subscription is sent.
ResponseEventSubscriptionItem ResponseEventSubscriptionItemType 1..n Y List of subscriptions requested

Schema XSD

common-types.xsd

ResponseEventSubscriptionItemType

Location: //ResponseEventSubscriptionType/ResponseEventSubscriptionItem
ComplexType ResponseEventSubscriptionItemType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestItemId string 1 Y Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
CanonicalEventCatalogUri anyUri 1 Y Identifier of the canonical event catalogue.
Format:
  • urn:de4a-eu:CanonicalEventCatalogueType::catalogueID

The complete set of values for catalogueID is available at codelists on the WP5 GitHub.

SubscriptionPeriod TimePeriodType 1 Y Confirmation of the period of time for which the subscription will last.

EventNotificationType

Location: //EventNotificationType
ComplexType EventNotificationType.jpg
Name Type Cardinality Mandatory Field / Label Description
NotificationId String 1 Y Event notification identifier (UUID format)
Timestamp Date 1 Y Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
DataEvaluator AgentType 1 Y Identifies the Data Evaluator to whom the event notification is sent.
DataOwner AgentType 1 Y Identifies the Data Owner that sends the event notification message.
EventNotificationItem EventNotificationItemType 1..n Y List of event notifications

Schema XSD

common-types.xsd

EventNotificationItemType

Location: //EventNotificationType/EventNotificationItem
ComplexType EventNotificationItemType.jpg
Name Type Cardinality Mandatory Field / Label Description
NotificationItemId string 1 Y Identifier of each item of the notification (UUID format)
EventId string 1 Y Identifier of the event that triggered the notification in the DO system.
EventSubject DataRequestSubjectCVType 1 Y Contains the identifying details of the company or representative to whom the event notification relates.
CanonicalEventCatalogUri anyUri 1 Y Identifier of the canonical event catalogue.
Format:
  • urn:de4a-eu:CanonicalEventCatalogueType::catalogueID

The complete set of values for catalogueID is available at codelists on the WP5 GitHub.

EventDate Datetime 1 Y Date when the event occurred.
RelatedEventSubject DataRequestSubjectCVType 0..n Y Contains the identification data of possible subjects also related to or afected by this event.

RequestExtractMultiEvidenceLUType

Location: //RequestExtractMultiEvidenceLUType
ComplexType RequestExtractMultiEvidenceLUType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestId String 1 Y Request identifier (UUID format). It is going to be the same during all interactions of this message exchange.
SpecificationId String 1 Y IEM version used
Timestamp Date 1 Y Date and time of creation of the message. Its value will remain unchanged as it passes through the intermediate components until it reaches its final destination.
ProcedureId String 0..1 N Metadata about the procedure or public service the justifies the use of the DE4A OOTS.
DataEvaluator AgentType 1 Y Identifies the Data Evaluator who is making the request for evidence. This information is also used to route the responses from the Data Owner to the Data Evaluator.
DataOwner AgentType 1 Y Identifies the Data Owner to whom the request for evidence is sent.
RequestEvidenceLUItem RequestEvidenceLUItemType 1..n Y List of requested canonical evidence types

Schema XSD

common-types.xsd

RequestEvidenceLUItemType

Location: //RequestExtractMultiEvidenceLUType/RequestEvidenceLUItem
ComplexType RequestEvidenceLUItemType.jpg
Name Type Cardinality Mandatory Field / Label Description
RequestItemId String 1 Y Identifier of each item of the request (UUID format). It is going to be the same during all interactions of this message exchange.
DataRequestSubject DataRequestSubjectCVType 1 Y Contains the identifying details of the person, company or representative to whom the evidence relates.
CanonicalEvidenceTypeId String 1 Y Identifier of the canonical evidence type.
Format:
  • urn:de4a-eu:CanonicalEvidenceType::evidenceID

The complete set of values for evidenceID is available at codelists on the WP5 GitHub.

RequestGrounds RequestGrounds 1 Y Legal grounds justifying the request for evidence and supporting the applicant.
AdditionalParameter AdditionalParameterType 0..n N/Y Contains each additional parameter necessary to request the evidence.
EventNotificationRef String 1 Y NotificationId of the event notification this Lookup request is based on.

ResponseErrorType

Location: //ResponseErrorType
ComplexType ResponseErrorType.jpg
Name Type Cardinality Mandatory Field / Label Description
Ack boolean 1 Y/Y Value returned in case no error occurred.
Error ErrorType 0..n N/Y Data type returned in case of error.

Schema XSD

common-types.xsd

Retrieved from ‘https://wiki.de4a.eu/index.php?title=Data_Dictionary&oldid=5724’