High-Level Requirements — tabular export (CSV)

Verified on 2026-10-29

Official

Reference
ARF 3.0.0 HLR CSV
Type
ARF (architecture framework)
Folder
EUDI Wallet
Version
v3.0.0
Date
2026-07-23
Status
Final
Languages
English
Official source
https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/blob/v3.0.0/hltr/high-level-requirements.csv

Note

Tabular export (CSV) of the high-level requirements of ARF 3.0.0, allowing them to be sorted and filtered by topic, actor or category.

The full text is not reproduced here (copyright): see the official source.

Summary

Purpose

This file is the tabular export (CSV) of the High-Level Requirements (HLR) of the Architecture and Reference Framework (ARF) of the European Digital Identity Wallet, in its version 3.0.0 of 23 July 2026 ARF 3.0.0 HLR CSV. The ARF serves as a common reference for the harmonised implementation of the European Digital Identity Regulation § 1.3 Purpose, scope and audience.

Since ARF 2.7.0, all the HLRs of Annex 2 are in this file, which allows them to be sorted and filtered. The two readable files of Annex 2 (by topic and by category) are generated from it; in the event of a discrepancy, the CSV prevails ANNEX 2.01 - High-Level Requirements <!-- omit from toc -->.

An informative document, not law

HLRs are not legal rules. The ARF presents itself as informative: it does not replace the European Digital Identity Regulation or its implementing and delegated acts, which are the only mandatory requirements § 1.3 Purpose, scope and audience. It recalls this in connection with discussion papers:

Official text · ARF 3.0.0 ch. 1, § 1.8 Drafting Process and Discussion Papers

the ARF itself is informative and not legally binding

Who it is addressed to

Each HLR designates the actor that must implement it; no requirement targets users A.2.1.1 Overview. Annex 2.01 divides the HLRs into two parts and six categories ANNEX 2.01 - High-Level Requirements <!-- omit from toc -->:

  • requirements specific to an actor: wallet providers; Member States and registrars; attestation and PID providers; relying parties;
  • rules common to the ecosystem: protocols and interoperability; data models and rules for attestations.

Key points

  • Content: 725 rows and ten columns, including the harmonised identifier, the part, the category, the topic (Topic), the former identifier (Index), the text of the requirement and a note ARF 3.0.0 HLR CSV.
  • Two identifiers: the former one, by topic (for example ISSU_10), and the new one, in the format PART-CATEGORY-TOPIC-NUMBER ANNEX 2.01 - High-Level Requirements <!-- omit from toc --> A.2.2 Structure and order of presentation of the HLRs.
  • Breakdown (Asphalia count on the file): according to the part column, 570 rows belong to the requirements specific to an actor and 155 to the common rules; 34 topics; 103 rows carry only the word Empty ARF 3.0.0 HLR CSV.
  • Key words: SHALL, SHOULD and MAY follow RFC 2119 (requirement, recommendation, option); lower-case must signals an external constraint, imposed for example by a standard, and not by the ARF A.2.1.2 Key words. Of the non-empty rows, 595 contain SHALL, 21 SHOULD without SHALL and 6 only MAY (Asphalia count) ARF 3.0.0 HLR CSV.
  • Consistency: for 14 rows, the prefix of the harmonised identifier (AS or EW) does not match the part column (Asphalia count) ARF 3.0.0 HLR CSV.

Written by Asphalia.