Release/1.9.0 (#503)

* Update README.md

* Release/1.8.0 (#447)

* Update README.md

* ARF 1.8.0 prepared for release (#1044)

---------

Co-authored-by: Paolo De Rosa <[email protected]>
Co-authored-by: Stavros Kounis (WSL 22.04) <[email protected]>

* Update Makefile

* Review/topic n first paper (#1051)

Topic N for release

* Update CHANGELOG (#1143)

* Releasing 1.9.0 (#1146)

* Fixing a reference and adding a note back in

* Fixing unclear formulation in DASH requirements noted by Tomasz

* Clarifying chapter 5

* Adding a more complete description of ISO/IEC 18013-5 and -7 to 5.4.

* More complete descriptions of SD-JWT VC and W3C VCDM to be done.

* Finishing re-write of sections 5.3 and 5.4

* Adding reference to ISO 23220-2 in Chapter 9

* Fixing markdown issues

* Introducing section 5.6 on protocols

And moving appropriate content from section 5.3 to 5.6.

* Fixed #1116

* Fixing descriptions of W3C VCDM in PID Rulebook and Annex 2

* Fixing [issue on the public GitHub](#486)

* Solving #1029

...and removing the trust infrastructure from the description of the contents of the PID Rulebook.

* Fixing table formats

* Solving #998

* Solving #999

* Solving #999

* Fixing multiple issues

* Solving last part of #1080

* Solving #1129

* Solving #1081

Also removing brackets in "(non-qualified)" everywhere, as the term was used both with and without brackets, with no difference in meaning.

* Solving several issues

* update section 5

* updated makefile

* Fixing typo

* Solving comment by Paolo

* Update annex-1-definitions.md

* Update architecture-and-reference-framework-main.md

Author: paolo-de-rosa

.vscode/settings.json

@@ -23,6 +23,7 @@
         "EDICG",
         "EHIC",
         "eisvogel",
+        "EKYC",
         "ENISA",
         "EPUB",
         "EUCC",
@@ -54,6 +55,7 @@
         "RPACA",
         "RPRC",
         "Rulebook",
+        "Sakimura",
         "SCAL",
         "Sporny",
         "tdate",

CHANGELOG

@@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semverdoc.org/).
 
+## [1.9.0] - 2025-04-16
+
+Processed comments on ARF 1.8.0. 
+Editorial changes and fixing typos.
+
+
 ## [1.8.0] - 2025-03-26
 
 Added results of "Topic C - Wallet Unit Attestation (WUA) and key attestation"

Makefile

@@ -26,7 +26,7 @@ SOURCE_DOCS    := $(MAIN_DOC) $(ANNEXES_DOCS)
 # Directories and Build Information
 BUILD_DIR      := ./build
 SITE_DIR       := ./site
-VERSION        := 1.8.0
+VERSION        := 1.9.0
 BUILD          := $(shell date +%Y%m%d.%H%M%S)
 
 # Pandoc configuration

docs/annexes/annex-1/annex-1-definitions.md

@@ -111,7 +111,7 @@ standard or a formal publication, that source is mentioned.
 | Notification | The act of transferring information to the European Commission. [Topics 31] |
 | Pseudonym | Data uniquely representing a user which in itself does not allow to infer any user's attribute or person identification data, without the use of additional information that is kept separately by the issuer of the data uniquely representing the user. |
 | Public Key Infrastructure (PKI) | Systems, software, and communication protocols that are used by EUDI Wallet ecosystem components to distribute, manage, and control public keys. A PKI publishes public keys and establishes trust within an environment by validating and verifying the public keys mapping to an entity. |
-| Qualified Electronic Signature Remote Creation Service Provider | A natural or a legal person that offers services related to the remote creation, validation, and management of qualified electronic signatures that meet eIDAS regulation legal requirements and standards to be considered as legally equivalent to handwritten signatures. |
+| Qualified Electronic Signature Remote Creation Provider | A natural or a legal person that offers services related to the remote creation, validation, and management of qualified electronic signatures that meet legal requirements and standards in the [European Digital Identity Regulation] to be considered as legally equivalent to handwritten signatures. |
 | Relying Party Instance | A software and/or hardware module with the capability to interact with a Wallet Unit and to perform Relying Party authentication, that is controlled by a Relying Party. |
 | Selective Disclosure | The capability enabling the User to present a subset of the attributes included in a PID or attestation. |
 | Technical validity period (of a PID or attestation) | The dates (and possibly times) from and up to which the attestation is valid, which are represented as metadata of the attestation. *Note: All PIDs and attestations have a technical validity period, which is typically much shorter than its administrative validity period (if existent). The technical validity period is chosen based on a risk analysis, e.g. with regard to User privacy.* |