Apply suggestions from code review

Co-authored-by: fmarino-ipzs <[email protected]>
italia · Sep 12, 2023 · 39de424 · 39de424
1 parent 897130e
commit 39de424
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 8 deletions.
diff --git a/docs/en/defined-terms.rst b/docs/en/defined-terms.rst
@@ -52,7 +52,9 @@ Below are the description of acronyms and definitions which are useful for furth
    * - Level of Assurance
      - The degree of confidence in the vetting process used to establish the identity of the User and the degree of confidence that the User who presents the credential is the same User to whom the credential was issued.
    * - Holder Key Binding
-     - Ability of the Holder to prove legitimate possession of the private part, related to the public part attested by a Trusted Third Party.
+     - Ability of the Holder to prove legitimate possession of the private key, related to the public key attested by a Trusted Third Party.
+   * - Trusted Third Party
+     - An entity other than the Holder and Verifier that is trusted by the Holder, the Verifier or both to provide certain services ([NIST SP 800-89](https://doi.org/10.6028/NIST.SP.800-89)).
 
 Acronyms
 --------

diff --git a/docs/en/index.rst b/docs/en/index.rst
@@ -19,17 +19,17 @@ To achieve these objectives and enhance the already active and eIDAS-notified di
 
 The purpose of the following technical rules is to define the technical architecture and reference framework to be used as a guideline by all the parties involved in the development of the IT Wallet project.
 
-This documentation defines the national implementation profile of EUDI Wallet, containing the technical details about components of the Wallet ecosystem, as listed below:
+This document provides technical guidelines for the secure implementation of Wallet ecosystem components that include:
 
  - Entities of the ecosystem according to `EIDAS-ARF`_.
  - Infrastructure of trust attesting realiability and eligibility of the participants.
- - PID and EAAs data schemes and attribute sets.
- - PID/EAA in MDL CBOR format.
- - PID/EAA in `SD-JWT`_ format.
+ - PID/(Q)EAAs data schemes and attribute sets.
+ - PID/(Q)EAA in MDL CBOR format.
+ - PID/(Q)EAA in `SD-JWT`_ format.
  - Wallet Solution general architecture.
  - Wallet Instance Attestation.
- - Issuance of PID/EAA according to `OpenID4VCI`_.
- - Presentation of PID/EAA according to `OpenID4VP`_.
+ - Issuance of PID/(Q)EAA according to `OpenID4VCI`_.
+ - Presentation of PID/(Q)EAA according to `OpenID4VP`_.
  - Presentation of pseudonyms according to `SIOPv2`_.
  - PID/EAA backup and restore mechanisms.
  - PID/EAA revocation lists.

diff --git a/docs/en/pid-eaa-data-model.rst b/docs/en/pid-eaa-data-model.rst
@@ -22,7 +22,7 @@ The (Q)EAAs are issued by (Q)EAA Issuers to a Wallet Instance and MUST be provid
 
 The (Q)EAAs are extended according to the `OpenID Identity Assurance Profile [OIDC.IDA] <https://openid.net/specs/openid-connect-4-identity-assurance-1_0-13.html>`_, that allows the recipients to know the Authentic Sources where the data comes from. 
 
-The PID/(Q)EAA data format and the mechanism through which a digital credential is issued to the Wallet Instance and presented to an Relying Party is described in the following sections. 
+The PID/(Q)EAA data format and the mechanism through which a digital credential is issued to the Wallet Instance and presented to a Relying Party are described in the following sections. 
 
 SD-JWT
 ======