Release/1.7.0 (#436)

paolo-de-rosa · web-flow · commit 303a5b1562a3 · 2025-03-17T16:48:12.000+01:00
* Update README.md
* Release ARF version 1.7.0 (#1011)
* ARF 1.7.0 Includes the result in the final discussion papers on:
    - Topic F - Digital Credential API (former known as browser API) 
    - Topic E - Pseudonyms, including User authentication mechanism
* Fixed editorial items
diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -60,6 +60,7 @@
         "UICC",
         "UICCs",
         "unlinkability",
+        "unlinkable",
         "VCDM",
         "WIAM",
         "WSCA",
diff --git a/CHANGELOG b/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.7.0] - 2025-03-17
+
+Added results of "Topic E - Pseudonyms, including User authentication mechanism"
+Added results of "Topic F - Digital Credential API"
+Editorial changes and fixing typos.
+
 ## [1.6.1] - 2025-03-10
 
 Editorial changes and fixing typos.
diff --git a/docs/annexes/annex-2/annex-2-high-level-requirements.md b/docs/annexes/annex-2/annex-2-high-level-requirements.md
diff --git a/docs/annexes/annex-3/annex-3.02-mDL-rulebook.md b/docs/annexes/annex-3/annex-3.02-mDL-rulebook.md
@@ -7,7 +7,7 @@ subtitle: "ARF Annex 3.02 - mDL Rulebook"
 
 *This is a working document that holds no legal value and does not
 reflect any common agreement or position of the co-legislators. It
-presents a state-of-play of ongoing work of the eIDAS Expert Group. This
+presents a state-of-play of ongoing work of the European Digital Identity Cooperation Group. This
 document is being continuously updated and should not be considered
 final.*
 
diff --git a/docs/architecture-and-reference-framework-main.md b/docs/architecture-and-reference-framework-main.md
diff --git a/docs/discussion-topics/b-re-issuance-and-batch-issuance-of-pids-and-attestations.md b/docs/discussion-topics/b-re-issuance-and-batch-issuance-of-pids-and-attestations.md
@@ -6,7 +6,7 @@ Version 0.9, updated 17 February 2025
 
 ### 1.1 Discussion Paper topic description
 
-This document is the Discussion Paper for eIDAS Coordination Group
+This document is the Discussion Paper for the European Digital Identity Cooperation Group
 regarding Topic B: Re-issuance and batch issuance of PIDs and
 Attestations.
 
diff --git a/docs/discussion-topics/d-embedded-disclosure-policies.md b/docs/discussion-topics/d-embedded-disclosure-policies.md
@@ -6,8 +6,7 @@ Version 1.0, updated 24 February 2025
 
 ### 1.1 Discussion Paper topic description
 
-This document is the Discussion Paper for eIDAS Coordination Group regarding
-Topic D: Embedded Disclosure Policies.
+This document is the Discussion Paper for the European Digital Identity Cooperation Group regarding Topic D: Embedded Disclosure Policies.
 
 The ARF Development Plan \[ARF\_DevPlan\] describes this Topic as follows:
 
diff --git a/docs/discussion-topics/e-pseudonyms-including-user-authentication-mechanism.md b/docs/discussion-topics/e-pseudonyms-including-user-authentication-mechanism.md
@@ -333,7 +333,7 @@ The table below summarizes information from the previous sections with regard to
 
 Certain WUA attributes are somewhat sensitive, as they may allow for linkability, and are only intended for PID Providers and Attestation Providers when performing issuance. Other metadata in the WUA is used to prove that the Wallet Unit has not been revoked. This information is less sensitive and is intended for Relying Parties.
 
-When a Wallet Unit and a Relying Party perform registration of a pseudonym, key material will be stored on the Wallet Unit (in its role as Authenticator). During this registration, the WUA may be used in connection with the pseudonym attestation (discussed in [Section 4.2.3](#423-pseudonym-attestation)). Topic C should consider what information can be presented to a Relying Party, when registrering a pseudonym.
+When a Wallet Unit and a Relying Party perform registration of a pseudonym, key material will be stored on the Wallet Unit (in its role as Authenticator). During this registration, the WUA may be used in connection with the pseudonym attestation (discussed in [Section 4.2.3](#423-pseudonym-attestation)). Topic C should consider what information can be presented to a Relying Party, when registering a pseudonym.
 
 There are two main areas of Topic C that are particularly relevant in relation to Pseudonyms:
 
@@ -684,7 +684,7 @@ A Wallet Unit SHOULD enable a User to freely choose a User alias for each Pseudo
 
 A Wallet Unit SHALL enable a User to choose which Pseudonym to authenticate with towards a Relying Party, if multiple Pseudonyms are registered for this Relying Party. The Wallet Unit SHOULD present the User with the aliases of the applicable Pseudonyms, if assigned, when making this choice.
 
-p> Rationale: A User should be able to freely choose which Pseudonym to use if multiple are available.
+> Rationale: A User should be able to freely choose which Pseudonym to use if multiple are available.
 
 ##### Requirement 7
 
@@ -794,7 +794,7 @@ The Commission SHALL create or reference a profile or extension of the WebAuthn
 
 Wallet Providers SHALL ensure that their Wallet Solution supports WebAuthn with additions and changes as documented in this document and future technical specifications created by or on behalf of the Commission.
 
-> Rationale: This ensures that Relying Parties can implement a uniform interface to let any User register and authenticate with Pseudonyms if they have an EUDIW.
+> Rationale: This ensures that Relying Parties can implement a uniform interface to let any User register and authenticate with Pseudonyms if they have an EUDI Wallet.
 
 #### 6.2 HLRs to be Removed
 
diff --git a/docs/discussion-topics/f-digital-credential-api.md b/docs/discussion-topics/f-digital-credential-api.md
@@ -6,8 +6,7 @@ Version 1.1, updated 20 February 2025
 
 ### 1.1 Discussion Paper topic description
 
-This document is the Discussion Paper for eIDAS Coordination Group regarding
-Topic F: Digital Credentials API (formerly known as browser API).
+This document is the Discussion Paper for the European Digital Identity Cooperation Group regarding Topic F: Digital Credentials API (formerly known as 'the browser API').
 
 The ARF Development Plan \[ARF\_DevPlan\] describes this Topic as follows:
 
diff --git a/docs/discussion-topics/g-zero-knowledge-proof.md b/docs/discussion-topics/g-zero-knowledge-proof.md
@@ -535,4 +535,4 @@ additional communication that could be used to track or link User activity.
 | \[Ora2024\] | Orange, “The BBS# protocol”, Technical Report, 2024 |
 | \[Paq2024\] | Christian Paquin, Guru-Vamsi Policharla, and Greg Zaverucha, Crescent: Stronger Privacy for Existing Credentials, Cryptology ePrint Archive, Paper 2024/2013, 2024, available at <https://eprint.iacr.org/2024/2013> |
 | [RiskRegister] | Annex 1 to the Commission Implementing Regulation (EU) 2024/2981 of 28 November 2024 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and the Council as regards the certification of European Digital Identity Wallets |
-| \[Topic\_A\] | Discussion Paper for eIDAS Coordination Group regarding Topic A: Privacy risks and mitigation, version 1.0 |
+| \[Topic\_A\] | Discussion Paper for the European Digital Identity Cooperation Group regarding Topic A: Privacy risks and mitigation, version 1.0 |
diff --git a/docs/index.md b/docs/index.md
@@ -10,7 +10,7 @@ notified electronic identification became mandatory in 2018. Yet, there is no
 requirement for Member States to develop a national electronic identification
 and to make it interoperable with those in other Member States. This has led to
 discrepancies between countries. The new [European Digital Identity Regulation](https://eur-lex.europa.eu/eli/reg/2014/910/2024-10-18)
-addresses shortcomings in eIDAS by improving the effectiveness of the framework
+addresses shortcomings in the eIDAS Regulation by improving the effectiveness of the framework
 and extending its benefits to the private sector. Member States will offer
 citizens and businesses digital wallets that will be able to link various
 aspects of their national digital identities. These may be provided by public
diff --git a/docs/technical-specifications/ts1-eudi-wallet-trust-mark.md b/docs/technical-specifications/ts1-eudi-wallet-trust-mark.md
