hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.2 EAA category | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.2.1 General requirements | EAA-6.2.2.1-01: ISO/IEC-mdoc EAAs issued by EAAs issuers registered in the European Union, which are neither ISO/IEC-mdoc QEAAs nor ISO/IEC-mdoc PuB-EAAs, shall not include the category data element. NOTE: As the category data element is defined in the present document its namespace is "org.etsi.01947201.010101". EAA-6.2.2.1-02: The category data element shall implement the semantics specified in clause 4.2.2 of the present document. EAA-6.2.2.1-03: The category data element shall be of type tstr (specified in IETF RFC 8610 [22]). |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.2.2 Requirements for EU Qualified EAA (QEAA) | QEAA-6.2.2.2-01: An ISO/IEC-mdoc QEAA shall include the category data element, which shall implement the semantics specified in clause 4.2.2 of the present document. QEAA-6.2.2.2-02: The value of the category data element in an ISO/IEC-mdoc QEAA shall be the URN defined in requirement QEAA-4.2.2.2-02 (urn:etsi:esi:eaa:eu:qualified). 6.2.2.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-6.2.2.3-01: An ISO/IEC-mdoc PuB-EAA shall include the category data element, which shall implement the semantics specified in clause 4.2.2 of the present document. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 37 PuB-EAA-6.2.2.3-02: The value of the category data element in an ISO/IEC-mdoc PuB-EAA shall be the URN defined in requirement PuB-EAA-4.2.2.3-02 (urn:etsi:esi:eaa:eu:pub). |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.3 EAA identifier | EAA-6.2.3-01: An ISO/IEC-mdoc EAA shall incorporate the document_number data element. EAA-6.2.3-02: The document_number data element shall implement the semantics of clause 4.2.3 of the present document. EAA-6.2.3-03: If the ISO/IEC-mdoc EAA is a mDL, then the document_number data element shall be as specified in Table 5 of clause 7.2.1 of ISO/IEC 18013-5 [12]. EAA-6.2.3-04: If the ISO/IEC-mdoc EAA is NOT a mDL the document_number data element shall be as specified in clause 6.3 of ISO/IEC 23220-2 [13]. NOTE: In both cases, the value of the document_number data is a number (e.g. a unique serial number). |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.4 EAA issuer identifier | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.4.1 General requirements | Common requirements to both types of EAA Issuer (natural or legal person) EAA-6.2.4.1-01: If an ISO/IEC-mdoc EAA is a mDL it shall include the issuing_authority component, specified in Table 5 of clause 7.2.1 of ISO/IEC 18013-5 [12]. EAA-6.2.4.1-02: The issuing_authority data element shall implement the semantics of clause 4.2.4 of the present document. EAA-6.2.4.1-03: If an ISO/IEC-mdoc EAA is NOT a mDL it shall include the issuing_authority_unicode component, specified in clause 6.3 of ISO/IEC 23220-2 [13]. EAA-6.2.4.1-04: The issuing_authority_unicode data element shall implement the semantics of clause 4.2.4 of the present document. NOTE 1: ISO/IEC 23220-2 [13] defines two data elements (each one with its own identifier) with different character sets, namely: latin1 (the character set mandated for issuing_authority in ISO/IEC 18013-5 [12]), and Unicode. EAA-6.2.4.1-05: An ISO/IEC-mdoc EAA may incorporate the issuing_country, identifying the EU Member where the ISO/IEC-mdoc EAA issuer is registered. EAA-6.2.4.1-06: If the ISO/IEC-mdoc EAA is a mDL, then the issuing_country data element shall be as specified in Table 5 of clause 7.2.1 of ISO/IEC 18013-5 [12]. EAA-6.2.4.1-07: If the ISO/IEC-mdoc EAA is NOT a mDL the issuing_country data element shall be as specified in clause 6.3 of ISO/IEC 23220-2 [13]. EAA-6.2.4.1-08: The value of the optional issuing_country data element shall be as specified in requirement EAA-4.2.4.1-05 of the present document. Requirements when the EAA is a legal person EAA-6.2.4.1-09: Where a registration identifier is applicable, an ISO/IEC-mdoc EAA may include the iss_reg_id data element. NOTE 2: As the iss_reg_id data element is defined in the present document its namespace is "org.etsi.01947201.010101". EAA-6.2.4.1-10: The iss_reg_id data element shall be an element of the type tstr (specified in IETF RFC 8610 [22]). ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 38 EAA-6.2.4.1-11: The value of the iss_reg_id data element shall be a registration identifier. EAA-6.2.4.1-12: The value of the iss_reg_id data element may be built applying the rules specified in requirements LEG-5.1.4-02 to LEG-5.1.4-08 (both included) in clause 5.1.4 of ETSI EN 319 412-1 [16]. EAA-6.2.4.1-13: An ISO/IEC-mdoc EAA shall not incorporate the iss_reg_id claim if it incorporates the qualified certificate supporting the ISO/IEC-mdoc EAA signature. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.4.2 Requirements for EU Qualified EAA (QEAA) | QEAA-6.2.4.2-01: If the issuer of the ISO/IEC-mdoc QEAA is a legal person and if a registration identifier is applicable, an ISO/IEC-mdoc QEAA shall include the registration identifier either in the iss_reg_id data element or within the qualified certificate supporting its signature. QEAA-6.2.4.2-02: The value of the iss_reg_id data element shall be built according to the rules defined in clause 5.1.4 of ETSI EN 319 412-1 [16] to build the value of the organizationIdentifier attribute in the subject field of an X.509 certificate. 6.2.4.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-6.2.4.3-01: Where a registration identifier is applicable, an ISO/IEC 18013-5 [12] PuB-EAA shall include the registration identifier either in the iss_reg_id data element or within the qualified certificate supporting its signature. PuB-EAA-6.2.4.3-02: The value of the iss_reg_id data element shall be built according to the rules defined in clause 5.1.4 of ETSI EN 319 412-1 [16] to build the value of the organizationIdentifier attribute in the subject field of an X.509 certificate. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5 EAA subject and attribute subject identifiers and pseudonyms | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.1 EAA subject identifier | EAA-6.2.5.1-01: If an ISO/IEC-mdoc EAA requires that the EAA subject (the holder of the mDL) is identified, the ISO/IEC-mdoc EAA shall include the following data elements, specified in Table 5 of clause 7.2.1 of ISO/IEC 18013-5 [12]: given_name and family_name, and document_number. EAA-6.2.5.1-02: An ISO/IEC-mdoc EAA that is a mDL shall include either the complete set of data elements mentioned in the previous requirement identifying the EAA subject, or the also_known_as data element. NOTE 1: As the also_known_as data element is defined in the present document its namespace is "org.etsi.01947201.010101". EAA-6.2.5.1-03: The also_known_as data element shall be an element of the type tstr (specified in IETF RFC 8610 [22]). EAA-6.2.5.1-04: If the ISO/IEC-mdoc EAA is NOT a mDL, and requires that the EAA subject (the holder of the mDoc) is identified, the ISO/IEC-mdoc EAA shall include the following data elements, specified in clause 6.3 of ISO/IEC 23220-2 [13]: given_name, family_name, and document_number. NOTE 2: Although the identifiers of the data elements are the same in both ISO/IEC 18013-5 [12] and ISO/IEC 23220-2 [13], their namespaces differ, and in addition, given_name and family_name are encoded in Unicode in ISO/IEC 23220-2 [13], and in latin1 in ISO/IEC 18013-5 [12]. EAA-6.2.5.1-05: An ISO/IEC-mdoc EAA that is NOT a mDL shall include either the complete set of data elements mentioned in the previous requirement identifying the EAA subject, or the also_known_as data element. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 39 |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.2 EAA subject pseudonym | EAA-6.2.5.2-01: An ISO/IEC-mdoc EAA may contain the also_known_as data element, which shall contain the pseudonym of the EAA, and therefore shall implement the semantics specified in clause 4.2.6.3 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.3 Attribute subject identifier | EAA-6.2.5.3-01: An ISO/IEC-mdoc EAA may include attributes that refer to entities that are not the EAA subject: the attribute subjects. EAA-6.2.5.3-02: For each attribute subject, an ISO/IEC-mdoc EAA may include the attribute subject identifier or the attribute subject pseudonym. EAA-6.2.5.3-03: In an ISO/IEC-mdoc EAA the identifiers of the attribute subjects shall be associated to their corresponding attributes as specified in clause 6.3 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.4 Attribute subject pseudonym | EAA-6.2.5.4-01: An ISO/IEC-mdoc EAA may include pseudonyms of attribute subjects. EAA-6.2.5.4-02: In an ISO/IEC-mdoc EAA, the pseudonyms of the attribute subjects shall be associated with their corresponding attributes as specified in clause 6.3 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.5 Requirements for EU Qualified EAA (QEAA) | QEAA-6.2.5.5-01: In an ISO/IEC-mdoc QEAA all the attributes shall refer to the EAA subject. 6.2.5.6 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-6.2.5.6-01: In an ISO/IEC-mdoc PuB-EAA all the attributes shall refer to the EAA subject. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.6 EAA issuance | EAA-6.2.6-01: An ISO/IEC-mdoc EAA shall incorporate the issue_date data element. EAA-6.2.6-02: The issue_date data element shall indicate the issuance date according to the semantics of clause 4.2.7 of the present document. EAA-6.2.6-03: If the ISO/IEC-mdoc EAA is a mDL, then the issue_date data element shall be as specified in Table 5 of clause 7.2.1 of ISO/IEC 18013-5 [12]. EAA-6.2.6-04: If the ISO/IEC-mdoc EAA is NOT a mDL the issue_date data element shall be as specified in clause 6.3 of ISO/IEC 23220-2 [13]. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.7 EAA validity periods | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.7.1 Specific requirements for the EAA technical validity period | EAA-6.2.7.1-01: The validFrom member of the validityInfo member of the instance of MobileSecurityObject type specified in clause 9.1.2.4 of ISO/IEC 18013-5 [12], shall implement the semantics of the start time of the ISO/IEC-mdoc EAA technical validity period. EAA-6.2.7.1-02: The validUntil member of the validityInfo member of the instance of MobileSecurityObject type specified in clause 9.1.2.4 of ISO/IEC 18013-5 [12], shall implement the semantics of the end type instant of the ISO/IEC-mdoc EAA technical validity period. EAA-6.2.7.1-03: The validFrom and the validUntil members shall indicate the UTC time for date and time. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 40 EAA-6.2.7.1-04: The validFrom and the validUntil members shall have seconds precision. EAA-6.2.7.1-05: The validFrom and the validUntil members shall not contain fractions of seconds. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.7.2 Specific requirements for the EAA administrative validity period | EAA-6.2.7.2-01: If the ISO/IEC-mdoc EAA is a mDL, then the expiry_date element specified in table 5 of clause 7.1 of ISO/IEC 18013-5 [12], shall implement the semantics of the end date of the ISO/IEC-mdoc EAA administrative validity period. EAA-6.2.7.2-02: If the ISO/IEC-mdoc EAA is NOT a mDL, then the expiry_date element specified in clause 6.3 of ISO/IEC 23220-2 [13], shall implement the semantics of the end date of the ISO/IEC-mdoc EAA administrative validity period. EAA-6.2.7.2-03: The issue_date data element, as specified in clause 6.2.6 of the present document, may be considered, wherever appropriate, to implement the semantics of the start date of the ISO/IEC-mdoc EAA Administrative validity period. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.8 Components constraining the usage of EAA | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.8.1 EAA audience | EAA-6.2.8.1-01: An ISO/IEC-mdoc EAA shall not incorporate any data element implementing the semantics specified in clause 4.2.9.2 of the present document. NOTE: The restrictions mentioned in clause 4.2.9.2 of the present document can be imposed by Embedded Disclosure Policy existing for the EAA and the restrictions established for the Relying Parties during their registration. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.8.2 Signal of one-time use | EAA-6.2.8.2-01: An ISO/IEC-mdoc EAA may incorporate the oneTime data element. EAA-6.2.8.2-02: The oneTime data element shall implement the semantics specified in clause 4.2.9.3 of the present document. NOTE: As the oneTime data element is defined in the present document its namespace is "org.etsi.01947201.010101". EAA-6.2.8.2-03: The oneTime data element shall have the bool CBOR type. EAA-6.2.8.2-04: If the oneTime data element is present and set to true, it shall indicate that the EAA shall be used only once, and that it shall not be retained for future use. EAA-6.2.8.2-05: If the oneTime data element is present and set to false or it is absent, the aforementioned constraint shall not apply to the EAA. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.9 Attributes evidence | EAA-6.2.9-01: An ISO/IEC-mdoc EAA shall not incorporate any data element implementing the semantics specified in clause 4.2.10 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.10 EAA status service | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.10.1 General requirements | EAA-6.2.10.1-01: An ISO/IEC-mdoc may contain the status member within the instance of MobileSecurityObject. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 41 EAA-6.2.10.1-02: The status member shall implement the semantics specified in clause 4.2.11 of the present document. EAA-6.2.10.1-03: The status member may contain the status_list member as specified in clause 6.3 of IETF draft-ietf-oauth-status-list-13 [25]. NOTE: At the moment of writing the present document, ISO/IEC 18013-5 [12] is under revision taking into account the status member specified in clause 6 of IETF draft-ietf-oauth-status-list-13 [25]. Clause 6.2.10 of the present document can be updated for referencing the revised ISO/IEC 18013-5 [12]. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.10.2 Requirements for EU Qualified EAA (QEAA) | QEAA-6.2.10.2-01: If an ISO/IEC-mdoc QEAA does not contain the shortLived data element, it shall contain the status member within the instance of MobileSecurityObject as specified in clause 6.2.10.1. 6.2.10.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-6.2.10.3-01: If an ISO/IEC-mdoc PuB-EAA does not contain the shortLived data element, it shall contain the status member within the instance of MobileSecurityObject as specified in clause 6.2.10.1. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.11 EAA renewal service | EAA-6.2.11-01: An ISO/IEC-mdoc EAA shall not incorporate any component implementing the semantics specified in clause 4.2.12 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.12 EAA short-lived | EAA-6.2.12-01: An ISO/IEC-mdoc EAA may incorporate the shortLived data element. EAA-6.2.12-02: The shortLived data element shall implement the semantics specified in clause 4.2.13 of the present document. NOTE: As the shortLived data element is defined in the present document its namespace is "org.etsi.01947201.010101". EAA-6.2.12-03: The shortLived data element shall have the bool CBOR type. EAA-6.2.12-04: If the shortLived data element is present and set to true, it shall indicate that the validity period of the EAA is so short that it shall not be necessary to check its revocation status. EAA-6.2.12-05: If the shortLived data element is present and set to false or it is absent, the aforementioned constraint shall not apply to the EAA and it shall be necessary to check its revocation status. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.3 Attested attributes | EAA-6.3-01: An ISO/IEC-mdoc EAA shall include each attested attribute, regardless it is disclosable or not, in one or more IssuerSignedItem component, and shall be incorporated to the ISO/IEC-mdoc EAA as specified in clause 8.3.2.1.2.2 of ISO/IEC 18013-5 [12]. EAA-6.3-02: For associating one attribute to one entity different than the EAA subject, the ISO/IEC-mdoc EAA shall include an instance of the SubAttr type (which is defined below) in the elementValue member of IssuerSignedItem. SubAttr = { ("subId" : SubId ; the subject attribute identifier // ?"subAka" : tstr); the subject attribute pseudonym }, SubId = { ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 42 "family_name" : tstr, ; The family name of the attribute subject "given_name" : tstr, ; The given name of the attribute subject "document_number": tstr ; The number of the personal identification data assigned to ;the attribute subject } EAA-6.3-03: An instance of SubAttr type shall have either the subId member or the subAka member. EAA-6.3-04: The subId member shall be a CBOR map whose members shall univocally identify the attribute subject. EAA-6.3-05: The subAka member shall be a CBOR String whose value shall be the pseudonym of an attribute subject which shall associate the attributes to this attribute subject. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.4 Attested Attributes metadata | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.4.1 Support to selective disclosure of attested attributes | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.4.1.1 Introduction | NOTE: ISO/IEC 18013-5 [12] imposes the presence of one instance of the MobileSecurityObjectType. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.4.1.2 Disclosure schema identifier | EAA-6.4.1.2-01: An ISO/IEC-mdoc EAA shall include the version component within its MobileSecurityObject. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.4.1.3 Disclosure | EAA-6.4.1.3-01: An ISO/IEC-mdoc EAA containing disclosable attributes, shall include each disclosure in one IssuerSignedItem component, and shall be incorporated to the ISO/IEC-mdoc EAA as specified in clause 8.3.2.1.2.2 of ISO/IEC 18013-5 [12]. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.4.1.4 Disclosure reference | EAA-6.4.1.4-01: For an ISO/IEC-mdoc EAA, the valueDigests component shall implement the semantics specified in clause 4.4.2.3 of the present document. EAA-6.4.1.4-02: If an ISO/IEC-mdoc includes selectively disclosable attested attributes, it shall include the valueDigests component within its MobileSecurityObject, as specified in clause 9.1.2.4 of ISO/IEC 18013-5 [12] for supporting the semantics specified in clause 4.4.2.3 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.4.1.5 Disclosure algorithm identifier | EAA-6.4.1.5-01: An ISO/IEC-mdoc EAA containing disclosable attributes, shall include the digestAlgorithm component within its MobileSecurityObject. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.5 EAA data for Key Binding | EAA-6.5-01: An ISO/IEC-mdoc EAA shall incorporate the deviceKey member within the deviceKeyInfo member of the instance of MobileSecurityObject type, to implement the semantics specified in clause 4.5 of the present document. EAA-6.5-02: The deviceKey member within the deviceKeyInfo member of the instance of MobileSecurityObject type, shall contain a public key whose private key is in possession of the EAA subject. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 43 |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.6 EAA digital signature | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.6.1 General requirements | EAA-6.6.1-01: An ISO/IEC-mdoc EAA shall be signed by a CB-AdES digital signature. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.6.2 Requirements for EU Qualified EAA (QEAA) | QEAA-6.6.2-01: The CB-AdES digital signature signing an ISO/IEC-mdoc QEAA shall be a qualified electronic signature or a qualified electronic seal. QEAA-6.6.2-02: The Protected Header of the CB-AdES digital signature signing an ISO/IEC-mdoc QEAA shall contain the x5u and the x5t header parameters, both specified in IETF RFC 9360 [20]. QEAA-6.6.2-03: The digest algorithm used in the x5t header parameter, shall be SHA-256. NOTE 1: This requirement meets requirement (h) in Annex V of Regulation (EU) 2024/1183 [i.2] for QEAA, which requires the presence of "(h) the location where the certificate supporting the qualified electronic signature or qualified electronic seal referred to in point (g) is available free of charge". NOTE 2: The presence of the x5t header parameter is required for security reasons. QEAA-6.6.2-04: The Protected Header of the CB-AdES digital signature signing an ISO/IEC-mdoc QEAA should contain the x5chain header parameter, specified in IETF RFC 9360 [20]. 6.6.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-6.6.3-01: The CB-AdES digital signature signing an ISO/IEC-mdocPuB-EAA shall be a qualified electronic signature or a qualified electronic seal. PuB-EAA-6.6.3-02: The Protected Header of the CB-AdES digital signature signing an ISO/IEC-mdoc PuB-EAA shall contain the x5u and the x5t header parameters, both specified in IETF RFC 9360 [20]. NOTE 1: This requirement meets requirement (h) in Annex VII of Regulation (EU) 2024/1183 [i.2] for PuB-EAA, which requires the presence of "(h) the location where the certificate supporting the qualified electronic signature or qualified electronic seal referred to in point (g) is available free of charge". NOTE 2: The presence of the x5t header parameter is required for security reasons. PuB-EAA-6.6.3-03: The digest algorithm used in the x5t header parameter, shall be SHA-256. PuB-EAA-6.6.3-04: The Protected Header of the CB-AdES digital signature signing an ISO/IEC-mdoc PuB-EAA should contain the x5chain header parameter, specified in IETF RFC 9360 [20]. 7 Implementation of EAA based on W3C Verifiable Credentials (JSON-LD W3C-VC) 7.1 General requirements Clause 7 of the present document specifies a realization of EAA based on the JSON-LD (specified in W3C Recommendation: "JSON-LD 1.1. A JSON-based Serialization for Linked Data" [29]) serialization of W3C Recommendation (15 May 2025): "Verifiable Credentials Data Model v2.0" [1]. Clauses from 7.1 to 7.5 specify the contents of an EAA that has not yet been signed by the EAA issuer. These not-yet- signed EAAs will be designated as JSON-LD W3C-VC EAA hereinafter. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 44 Clause 7.6 specifies different mechanisms for signing JSON-LD W3C-VC EAAs and defines a set of acronyms for designating the different resulting formats of signed JSON-LD W3C-VC EAAs. EAA-7.1-01: A JSON-LD W3C-VC EAA shall use the JSON-LD syntax for its serialization. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2 EAA metadata | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.1 EAA specification | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.1.1 EAA type | EAA-7.2.1.1-01: A JSON-LD W3C-VC EAA shall incorporate the credential object's type property, as specified in "Verifiable Credentials Data Model v2.0" [1], implementing the semantics specified in clause 4.2.1.2 of the present document. EAA-7.2.1.1-02: In a JSON-LD W3C-VC EAA the type property shall be an array of at least two strings. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.1.2 EAA context | EAA-7.2.1.2-01: A JSON-LD W3C-VC EAA shall incorporate the @context property, as specified in "Verifiable Credentials Data Model v2.0" [1], implementing the semantics specified in clause 4.2.1.3 of the present document. EAA-7.2.1.2-02: In a JSON-LD W3C-VC EAA the @context property shall be an array of URI values. EAA-7.2.1.2-03: In a JSON-LD W3C-VC EAA the @context shall contain the URI specified in "Verifiable Credentials Data Model v2.0" [1] (https://www.w3.org/ns/credentials/v2), and any other URI referencing a document that maps URLs to short-form aliases required for the EAA. EAA-7.2.1.2-04: The URL associated to each new property defined in the present document shall be the result of concatenating https://uri.etsi.org/019472010101# and the term used in the definition of the property in the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.1.3 EAA schema | EAA-7.2.1.3-01: A JSON-LD W3C-VC EAA may incorporate the credentialSchema property, as specified in "Verifiable Credentials Data Model v2.0" [1], implementing the semantics of clause 4.2.1.4 of the present document. NOTE 1: The Verifiable Credentials JSON schema specification can be found at https://www.w3.org/ns/credentials/v2. NOTE 2: [i.6] offers an alternative to the presence of this property within the JSON-LD W3C-VC EAA, as it specifies among other things "a data model for catalogue of attributes, guidance on Attestation Rulebooks, attestation type data models and applicable Application Programming Interface (API) for management of machine-readable attestation schemas". EAA-7.2.1.3-02: In a JSON-LD W3C-VC EAA the credentialSchema property shall be an array of at least one member. EAA-7.2.1.3-03: In a JSON-LD W3C-VC EAA each member of the credentialSchema property shall have two properties, namely: id, specified in clause 4.5 of [1], which will point to the document containing the schema, and type, which will indicate the type of schema contained in the mentioned document. The following string values are defined for the type child property of credentialSchema: 1) "JsonSchemaCredential": for schemas defined using JSON schema syntax as specified in JSON Schema Core [21]. 2) "CddlSchemaCredential": for schemas defined using Concise Data Definition Language as specified in IETF RFC 8610 [22]. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 45 3) "ShaclSchemaCredential": for schemas defined using SHACL as specified in W3C Recommendation: "Shapes Constraint Language (SHACL)" [23]. NOTE 2: SHACL is able to define schemas for RDF graphs, but it is not able to define schemas for RDF Data Sets. As a VC with embedded proofs a RDF Data set, SHACL will be able to define the schema of the EAA secured with the embedded proofs. Instead, it will be able to define the schema of the EAA without any embedded proof. EAA-7.2.1.3-04: Additional string values may be defined for the type child property of credentialSchema, each one identifying a different syntax for defining the JSON-LD W3C-VC EAA schema. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.2 EAA category | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.2.1 General requirements | EAA-7.2.2.1-01: If an indication of the category of the EAA (implementing the semantics specified in clause 4.2.2 of the present document) is required, this category shall be indicated in one of the strings in the credential object's type array property, specified in "Verifiable Credentials Data Model v2.0" [1]. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.2.2 Requirements for EU Qualified EAA (QEAA) | QEAA-7.2.2.2-01: In a JSON-LD W3C-VC QEAA one of the elements of the credential object's type array property shall be the URI defined in requirement QEAA-4.2.2.2-02 (urn:etsi:esi:eaa:eu:qualified). 7.2.2.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EA-7.2.2.3-01: In a JSON-LD W3C-VC PuB-EAA one of the elements of the credential object's type array property shall be the URI defined in requirement PuB-EAA-4.2.2.3-02 (urn:etsi:esi:eaa:eu:pub). |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.3 EAA identifier | EAA-7.2.3-01: The id property shall implement the semantics specified in clause 4.2.3 of the present document. EAA-7.2.3-02: A W3C-VC EAA may incorporate the credential object's id property. EAA-7.2.3-03: In a JSON-LD W3C-VC EAA the contents of the id property shall be as specified in "Verifiable Credentials Data Model v2.0" [1], clause 4.2. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.4 EAA issuer identifier | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.4.1 General requirements | Common requirements regardless whether the EAA issuer is a natural or a legal person EAA-7.2.4.1-01: The issuer property, specified in Verifiable Credentials Data Model v2.0 [1], shall implement the semantics specified in clause 4.2.4.1 of the present document. EAA-7.2.4.1-02: A W3C-VC EAA shall incorporate the issuer property. EAA-7.2.4.1-03: In a W3C-VC EAA the issuer property shall be an object. EAA-7.2.4.1-04: In a W3C-VC EAA the issuer property shall have the id child property, whose value shall be a URI, as specified in "Verifiable Credentials Data Model v2.0" [1]. NOTE: This means that a DID is a valid value for this id child property. EAA-7.2.4.1-05: In a W3C-VC EAA the issuer property may include the issuing_authority child property. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 46 EAA-7.2.4.1-06: In a W3C-VC EAA the issuing_authority child property of the issuer property shall be either a JSON String or a JSON Object. EAA-7.2.4.1-07: If the issuing_authority child property of the issuer property in a W3C-VC EAA is a JSON String, then it shall contain the name of the W3C-VC EAA issuer. EAA-7.2.4.1-08: If the issuing_authority child property of the issuer property in a W3C-VC EAA is a JSON Object, then it shall contain the name of the W3C-VC EAA issuer in several languages. EAA-7.2.4.1-09: If the issuing_authority child property of the issuer property in a W3C-VC EAA is a JSON Object, then every key of the map shall be a language code as specified in IETF RFC 5646 [27], and the value mapped to the key shall be the name of W3C-VC EAA issuer in that language. EAA-7.2.4.1-10: In a W3C-VC EAA the issuer property may include the issuing_country child property identifying the EU Member where the SD-JWT VC EAA issuer is registered. EAA-7.2.4.1-11: In a W3C-VC EAA the value of the issuing_country property shall be as specified in the requirement EAA-4.2.4.1-05 of the present document. Requirements when the EAA issuer is a legal person EAA-7.2.4.1-12: Where a registration identifier is applicable, the issuer property may include the reg_id child property. EAA-7.2.4.1-13: The value of the reg_id child property shall be built according to the rules defined in clause 5.1.4 of ETSI EN 319 412-1 [16] to build the value of the organizationIdentifier attribute in the subject field of an X.509 certificate. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.4.2 Requirements for EU Qualified EAA (QEAA) | QEAA-7.2.4.2-01: The W3C-VC QEAA issuer property shall include the issuing_authority child property. QEAA-7.2.4.2-02: The W3C-VC QEAA issuer property shall include the issuing_country child property. QEAA-7.2.4.2-03: If the issuer of the W3C-VC QEAA is a legal person and if a registration identifier is applicable, the issuer property shall include the reg_id child property. QEAA-7.2.4.2-04: The value of the reg_id child property shall be built according to the rules defined in clause 5.1.4 of ETSI EN 319 412-1 [16] to build the value of the organizationIdentifier attribute in the subject field of an X.509 certificate. 7.2.4.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-7.2.4.3-01: The W3C-VC PuB-EAA issuer property shall include the issuing_authority child property. PuB-EAA-7.2.4.3-02: The W3C-VC PuB-EAA issuer property shall include the issuing_country child property. PuB-EAA-7.2.4.3-03: Where a registration identifier is applicable, the W3C-VC PuB-EAA issuer property shall include the reg_id child property. PuB-EAA-7.2.4.3-04: The value of the reg_id child property shall be built according to the rules defined in clause 5.1.4 of ETSI EN 319 412-1 [16] to build the value of the organizationIdentifier attribute in the subject field of an X.509 certificate. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.5 EAA issued on behalf | EAA-7.2.5-01: If the W3C-VC EAA is issued on behalf of another entity, the EAA may incorporate the onBehalf child property of the issuer property, as specified in the present clause. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 47 EAA-7.2.5-02: The onBehalf child property shall be a JSON Array of zero or more JSON Objects. EAA-7.2.5-03: Each JSON Object within the onBehalf child property shall have a member id, whose value shall be a URI identifying an entity on whose behalf the EAA has been issued. EAA-7.2.5-04: Each JSON Object within the onBehalf child property may have a member name, whose value shall be the name of an entity on whose behalf the EAA has been issued. EAA-7.2.5-05: If the entity on whose behalf the EAA has been issued is a legal person, each JSON Object within the onBehalf child property may have a member reg_id, whose value shall be as specified in the requirement EAA-4.2.4.1-07. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.6 EAA and attribute subject identifiers and pseudonyms | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.6.1 General requirements | EAA-7.2.6.1-01: In a W3C-VC EAA each element of the credentialSubject array shall contain either the id child property or the pseudonym child property specified in the present clause. NOTE 1: If the credentialSubject array contains one element, this entity is the EAA subject. EAA-7.2.6.1-02: In a W3C-VC EAA the pseudonym child property of an element of the credentialSubject array shall contain a string whose value is the pseudonym of the entity associated to the attributes present in this array element. NOTE 2: The id child property can also be used for keeping the EAA subject anonymous. This can be achieved, for instance, using DIDs or other identifiers that introduce a level of indirection. EAA-7.2.6.1-03: If a W3C-VC EAA includes a credentialSubject array with more than one element, one of these elements shall contain attributes associated only to one specific entity (attribute subject), and one of these entities shall be the EAA subject. NOTE 3: Note that as it is required that each element of the credentialSubject array contains either the identifier or the pseudonym of the entity associated to the attributes within the element, and as one of these entities is the EAA subject, the EAA subject identifier or the EAA subject pseudonym is always present. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.6.2 The EAA subject identifier | EAA-7.2.6.2-01: If the credentialSubject array of a W3C-VC EAA has one element, and this element has the id child property, this id child property shall identify the EAA subject. NOTE: The id child property can have a value that is associated to the real-world identity of the EAA subject, or can have a value that does not reveal their real-world identity. This can be achieved, for instance, using DIDs or other identifiers that introduce a level of indirection, allowing the EAA subject to remain anonymous. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.6.3 The EAA subject pseudonym | EAA-7.2.6.3-01: If the credentialSubject array of a W3C-VC EAA has one element, and this element includes the pseudonym child property, then the value of this element shall be the pseudonym of the EAA subject. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.6.4 The attribute subject identifier | EAA-7.2.6.4-01: If the W3C-VC EAA includes a credentialSubject array that has more than one element, and this element has the id child property, this id child property shall identify the entity associated to the attributes in this element. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 48 NOTE: The id child property can have a value that is associated to the real-world identity of the attribute subject, or can have a value that does not reveal their real-world identity. This can be achieved, for instance using DIDs or other identifiers that introduce a level of indirection, allowing the EAA subject to remain anonymous. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.6.5 The attribute subject pseudonym | EAA-7.2.6.5-01: If the W3C-VC EAA includes a credentialSubject array that has more than one element, if one of these elements includes the pseudonym child property, then this child property shall contain the pseudonym of the entity associated to these attributes (the attribute subject). |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.6.6 Requirements for subject(s) names | EAA-7.2.6.6-01: The elements in the credentialSubject array of a JSON-LD W3C-VC EAA may contain the child property name. EAA-7.2.6.6-02: The child property name in one element of the credentialSubject array of a JSON-LD W3C-VC EAA may be either a JSON String or a JSON Object. EAA-7.2.6.6-03: If the child property name in one element of the credentialSubject array of a JSON-LD W3C-VC EAA is a JSON Object, then it shall contain the name of the entity associated with the corresponding attributes in several languages. EAA-7.2.6.6-04: If the child property name in one element of the credentialSubject array of a JSON-LD W3C-VC EAA is a JSON Object, then every key of the map shall be a language code as specified in IETF RFC 5646 [27], and the value mapped to the key shall be the name of the entity associated with the corresponding attributes in that language. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.6.7 Requirements for EU Qualified EAA (QEAA) | QEAA-7.2.6.7-01: The credentialSubject array of a JSON-LD W3C-VC QEAA shall contain only one element. QEAA-7.2.6.7-02: The element of the credentialSubject array of a JSON-LD W3C-VC QEAA shall contain either the id child property or the pseudonym child property. 7.2.6.8 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-7.2.6.8-01: The credentialSubject array of a JSON-LD W3C-VC PuB-EAA shall contain only one element. PuB-EAA-7.2.6.8-02: The element of the credentialSubject array of a JSON-LD W3C-VC PuB-EAA shall contain either the id child property or the pseudonym child property. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.7 EAA issuance | EAA-7.2.7-01: The issuedAt property shall implement the semantics specified in clause 4.2.7 of the present document. EAA-7.2.7-02: A JSON-LD W3C-VC EAA may incorporate the issuedAt property specified in the present clause. EAA-7.2.7-03: The content of the issuedAt property shall be a dateTimeStamp string as specified in W3C Recommendation: "W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes" [10], clause 3.3.7. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 49 |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.8 EAA validity periods | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.8.1 Specific requirements for technical validity period | EAA-7.2.8.1-01: A W3C-VC EAA shall incorporate the validFrom and validUntil properties, specified in "Verifiable Credentials Data Model v2.0" [1]. EAA-7.2.8.1-02: The validFrom property shall implement the semantics of the first instant time of the W3C-VC EAA technical validity period. EAA-7.2.8.1-03: The validUntil property shall implement the semantics of the second instant time of the W3C-VC EAA technical validity period. EAA-7.2.8.1-04: The contents of validFrom and validUntil shall be dateTimeStamp strings as specified in W3C Recommendation: "W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes" [10], clause 3.3.7. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.8.2 Specific requirements for administrative validity period | EAA-7.2.8.2-01: A W3C-VC EAA may incorporate the admValidFrom and admValidUntil properties specified in the present clause. EAA-7.2.8.2-02: The admValidFrom property shall implement the semantics of the first instant time of the W3C-VC EAA administrative validity period. EAA-7.2.8.2-03: The admValidUntil property shall implement the semantics of the second instant time of the W3C-VC EAA administrative validity period. EAA-7.2.8.2-04: The content of admValidFrom and admValidUntil shall be a dateTimeStamp string as specified in W3C Recommendation: "W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes" [10], clause 3.3.7. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.9 Components constraining the usage of EAA | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.9.1 EAA audience | EAA-7.2.9.1-01: A JSON-LD W3C-VC EAA shall not incorporate any data element implementing the semantics specified in clause 4.2.9.2 of the present document. NOTE: The restrictions mentioned in clause 4.2.9.2 of the present document can be imposed by Embedded Disclosure Policy existing for the EAA and the restrictions established for the Relying Parties during their registration. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.9.2 Signal of one-time use | EAA-7.2.9.2-01: The oneTime property, specified in the present clause, shall implement the semantics specified in clause 4.2.9.3 of the present document. EAA-7.2.9.2-02: A JSON-LD W3C-VC EAA may incorporate the oneTime property. EAA-7.2.9.2-03: The oneTime property shall have a boolean value. EAA-7.2.9.2-04: If the oneTime property is absent, it shall be considered that its value is false. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.9.3 Terms of use | EAA-7.2.9.3-01: A JSON-LD W3C-VC EAA may incorporate the termsOfUse property specified in "Verifiable Credentials Data Model v2.0" [1], clause 5.5. EAA-7.2.9.3-02: The termsOfUse property shall be either a JSON Object or a JSON Array of JSON Objects. In both cases, each JSON Object shall contain the details of one set of terms of use. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 50 EAA-7.2.9.3-03: Each JSON Object mentioned in requirement EAA-7.2.9.3-02 shall have the type child property identifying its type. The following string value is defined for the type child property of termsOfUse: 1) "embSDPolicy": for indicating that the termsOfUse property contains details on the embedded selective disclosure policy associated to the JSON-LD W3C-VC EAA. EAA-7.2.9.3-04: If the value of the type child property of the JSON Object mentioned in requirement EAA-7.2.9.3-02 is "embSDPolicy" then the mentioned JSON Object shall have the embSDPolicyId child property whose value shall be a URI identifying the embedded selective disclosure policy associated to the JSON-LD W3C-VC EAA. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.10 Attributes evidence | EAA-7.2.10-01: A JSON-LD W3C-VC EAA may incorporate the evidence property. EAA-7.2.10-02: The evidence property, specified in "Verifiable Credentials Data Model v2.0" [1], clause 5.7, shall implement the semantics specified in clause 4.2.10 of the present document. EAA-7.2.10-03: The evidence property shall be a JSON Array whose elements shall be JSON Objects. EAA-7.2.10-04: Each JSON Object within the JSON Array evidence property shall have the type child property. The value of the type child property shall be a JSON array of one or more elements whose values shall be URIs. EAA-7.2.10-05: Each JSON Object within the JSON Array evidence property may have the id child property indicating the type of the evidence. EAA-7.2.10-04: Each JSON Object within the JSON Array evidence property may have other members, whose specification is out of the scope of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.11 EAA status service | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.11.1 General requirements | EAA-7.2.11.1-01: The credentialStatus property, specified in "Verifiable Credentials Data Model v2.0" [1], clause 5.6, shall implement the semantics specified in clause 4.2.11 of the present document. EAA-7.2.11.1-02: A JSON-LD W3C-VC EAA may incorporate the credentialStatus object property. The following string values are defined for the type child property of credentialStatus: 1) "BitstringStatusListEntry": for Bitstring Status List as specified in W3C Recommendation: "Bitstring Status List v1.0" [24]. 2) "TokenStatusList": for Token Status List as specified in IETF draft-ietf-oauth-status-list-13 [25]. 3) "CRL": for CRL as specified in IETF RFC 5280 [9]. 4) "OCSP": for OCSP responses served by an OCSP Server as specified in IETF RFC 6960 [28]. EAA-7.2.11.1-03: If the value of the type child property of credentialStatus property is "CRL" or "OCSP" the value of the statusPurpose child property shall be present and set to value "revocation". EAA-7.2.11.1-04: If the value of the type child property of credentialStatus property is "CRL" or "OCSP" the value of the statusListCredential child property shall be present and its value shall be an URL pointing to the revocation status service. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.11.2 Requirements for EU Qualified EAA (QEAA) | QEAA-7.2.11.2-01: If a JSON-LD W3C-VC QEAA does not contain the shortLived property, it shall contain the credentialStatus property. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 51 7.2.11.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-7.2.11.3-01: If a JSON-LD W3C-VC PuB-EAA does not contain the shortLived property, it shall contain the credentialStatus property. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.12 EAA renewal service | EAA-7.2.12-01: A JSON-LD W3C-VC EAA may incorporate the refreshService property. EAA-7.2.12-02: The refreshService property, specified in "Verifiable Credentials Data Model v2.0" [1], clause 5.4, shall implement the semantics specified in clause 4.2.12 of the present document. EAA-7.2.12-03: The refreshService property shall be either a JSON Object or a JSON Array of JSON Objects. In both cases, each JSON Object shall contain the details of one renewal service. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.2.13 EAA short-lived | EAA-7.2.13-01: The shortLived property, specified in the present clause, shall implement the semantics specified in clause 4.2.13 of the present document. EAA-7.2.13-02: A JSON-LD W3C-VC EAA may incorporate the shortLived property. EAA-7.2.13-03: The shortLived property shall have a boolean value. EAA-7.2.13-04: If the shortLived property is absent, it shall be considered that its value is false. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.3 Attested Attributes | EAA-7.3-01: Each element in the credentialSubject array property shall contain attested attributes associated to one entity. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.4 Attested Attributes metadata | EAA-7.4-01: If a JSON-LD W3C-VC EAA has to incorporate selective disclosure of attributes using enveloping proofs, it shall use SD-JWT as specified in W3C Recommendation (15 May 2025): "Securing Verifiable Credentials using JOSE and COSE" [2], clause 3.2.1. EAA-7.4-02: If a JSON-LD W3C-VC EAA has to incorporate selective disclosure of attributes and it uses embedded proofs, it shall use crypto suites that allow this feature, as the one specified in W3C Recommendation (15 May 2025): "Data Integrity ECDSA Cryptosuites v1.0" [18], clause 3.5, or the one specified in W3C Candidate Recommendation (3 April 2025): "Data Integrity BBS Cryptosuites v1.0" [19], for securing the JSON-LD W3C-VC EAA. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.5 EAA data for key binding | EAA-7.5-01: A JSON-LD W3C-VC EAA secured with SD-JWT should incorporate, in the VC Payload, the cnf property as specified in clause 4.1.3 of W3C VC_JOSE_COSE [2], implementing the semantics specified in clause 4.5 of the present document. EAA-7.5-02: A JSON-LD W3C-VC EAA not secured by using SD-JWT should incorporate, in the VC Payload, the cnf property implementing the semantics specified in clause 4.5 of the present document. EAA-7.5-03: In both cases the cnf property may only contain either a representation of the EAA subject public key or a representation of the EAA subject certificate as specified in IETF RFC 7800 [14]. EAA-7.5-04: For representing the EAA subject certificate, the cnf property may contain the x5c child property containing only the certificate itself, or the x5t#S256 child property, or the x5u child property as specified in IETF RFC 7517 [30]. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 52 EAA-7.5-05: If the EAA subject certificate is represented by the x5u child property, the x5t#S256 child property shall also be present. EAA-7.5-06: If the EAA subject certificate is represented by the x5c child property, neither the x5u child property nor the x5t#S256 child property shall be present. EAA-7.5-07: The cnf property should contain a representation of the EAA subject public key. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.6 EAA digital signature | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.6.1 General requirements | EAA-7.6.1-01: A JSON-LD W3C-VC EAA shall be secured either with embedded proofs or with enveloping proofs. EAA-7.6.1-02: A JSON-LD W3C-VC EAA that does not have selective disclosures shall be signed by a JWS signature that shall meet the requirements defined in clause 3.1.1 of W3C Recommendation (15 May 2025): "Securing Verifiable Credentials using JOSE and COSE" [2], and the requirements defined in clause 7.6.4.2 of the present document. NOTE 1: These signed EAAs will be designated JSON-LD W3C VC JOSE EAA hereinafter. NOTE 2: Notice that [2] uses the term JOSE for referring to generate a JWS on the JSON-LD W3C-VC EAA. EAA-7.6.1-03: A JSON-LD W3C-VC EAA that has selective disclosures shall be signed using SD-JWT, and shall meet the requirements defined in clause 3.2.1 of W3C Recommendation (15 May 2025): "Securing Verifiable Credentials using JOSE and COSE" [2], and the requirements defined in clause 7.6.4.3 of the present document. NOTE 3: These signed EAAs will be designated JSON-LD W3C VC SD-JWT EAA hereinafter. The expression "signed-with-enveloping-proof JSON-LD W3C-VC" will be used to indistinctly designate both JSON- LD W3C VC JOSE EAA and JSON-LD W3C VC SD-JWT EAA in requirements that are common to both formats. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.6.2 Requirements for EU Qualified EAA (QEAA) | EAA-7.6.2-01: If the JSON-LD W3C-VC QEAA is secured using embedded proofs, the digital signature shall meet the requirements specified in clause 4.6.2 of the present document. EAA-7.6.2-02: The digital signature of a signed-with-enveloping-proof JSON-LD W3C-VC QEAA shall be a qualified electronic signature or a qualified electronic seal. EAA-7.6.2-03: The Protected Header of the digital signature of a signed-with-enveloping-proof JSON-LD W3C-VC QEAA shall contain the x5u and the x5t#S256 header parameters, specified in IETF RFC 7515 [8]. NOTE 1: This requirement meets requirement (h) in Annex VII of Regulation (EU) 2024/1183 [i.2] for PuB-EAA, which requires the presence of "(h) the location where the certificate supporting the qualified electronic signature or qualified electronic seal referred to in point (g) is available free of charge". NOTE 2: The presence of the x5t#S256 header parameter is required for security reasons. EAA-7.6.2-04: The Protected Header of the digital signature of a signed-with-enveloping-proof JSON-LD W3C-VC QEAA should contain the x5c header parameter, specified in IETF RFC 7515 [8]. 7.6.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) EAA-7.6.3-01: If the JSON-LD W3C-VC PuB-EAA is secured using embedded proofs, the digital signature shall meet the requirements specified in clause 4.6.2 of the present document. EAA-7.6.3-02: The digital signature of a signed-with-enveloping-proof JSON-LD W3C-VC PuB-EAA shall be a qualified electronic signature or a qualified electronic seal. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 53 EAA-7.6.3-03: The Protected Header of the digital signature of a signed-with-enveloping-proof JSON-LD W3C-VC PuB-EAA shall contain the x5u and the x5t#S256 header parameters, specified in IETF RFC 7515 [8]. NOTE 1: This requirement meets requirement (h) in Annex VII of Regulation (EU) 2024/1183 [i.2] for PuB-EAA, which requires the presence of "(h) the location where the certificate supporting the qualified electronic signature or qualified electronic seal referred to in point (g) is available free of charge". NOTE 2: The presence of the x5t#S256 header parameter is required for security reasons. EAA-7.6.3-04: The Protected Header of the digital signature of a signed-with-enveloping-proof JSON-LD W3C-VC PuB-EAA should contain the x5c header parameter, specified in IETF RFC 7515 [8]. 7.6.4 Requirements the JSON-LD W3C-VC EAA secured with enveloping proofs |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.6.4.1 General requirements | EAA-7.6.4.1-01: If a signed-with-enveloping-proof JSON-LD W3C-VC contains both the iat claim in the JOSE headers, and the issuedAt property, the time indicated in both components shall be the same. EAA-7.6.4.1-02: If a signed-with-enveloping-proof JSON-LD W3C-VC contains both the nbf claim in the JOSE headers, and the validFrom property, the time indicated in both components shall be the same. EAA-7.6.4.1-03: If a signed-with-enveloping-proof JSON-LD W3C-VC contains both the exp claim in the JOSE headers, and the validUntil property, the time indicated in both components shall be the same. EAA-7.6.4.1-04: If a signed-with-enveloping-proof JSON-LD W3C-VC contains both the jti claim in the JOSE headers, and the id property containing the identifier of the EAA, their values shall be the same. EAA-7.6.4.1-05: A signed-with-enveloping-proof JSON-LD W3C-VC shall not contain the status claim in the JOSE headers. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.6.4.2 Additional requirements for JSON-LD W3C VC JOSE EAAs | The present clause defines requirements for JSON-LD W3C VC JOSE EAAs in addition to the requirements defined in clause 3.1.1 of W3C Recommendation (15 May 2025): "Securing Verifiable Credentials using JOSE and COSE" [2]. EAA-7.6.4.2-01: A JSON-LD W3C VC JOSE EAA shall be serialized using Compact Serialization. EAA-7.6.4.2-02: The digital signature generated by the EAA issuer shall be a JAdES-B-B. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.6.4.3 Requirements for JSON-LD W3C VC SD-JWT EAAs | The present clause defines requirements for JSON-LD W3C VC SD-JWT EAAs in addition to the requirements defined in clause 3.2.1 of W3C Recommendation (15 May 2025): "Securing Verifiable Credentials using JOSE and COSE" [2]. EAA-7.6.4.2-01: A JSON-LD W3C VC SD-JWT EAA shall be serialized using either Compact Serialization or Flattened JSON Serialization, as specified in IETF SD-JWT [5]. EAA-7.6.4.2-02: If a JSON-LD W3C VC SD-JWT EAA is serialized using Flattened JSON Serialization, the digital signature shall be a JAdES-B-B signature as specified in ETSI TS 119 182-1 [11]. NOTE: IETF SD-JWT [5] Compact Serialization defines a structure that goes beyond JWS Compact Serialization, adding to the JWS Compact Serialization the disclosures separated by '~'. EAA-7.6.4.2-03: If a JSON-LD W3C VC SD-JWT EAA is serialized using Compact Serialization, the resulting structure shall consist in the Compact Serialization of a JAdES-B-B signature, as specified in ETSI TS 119 182-1 [11], followed by the sequence of disclosures appended as specified in IETF SD-JWT [5]. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 54 |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.6.4.4 Requirements for EU Qualified EAA (QEAA) | QEAA-7.6.4.4-01: If the digital signature is a JAdES-B-B as specified in ETSI TS 119 182-1 [11], then the requirements specified in clause 5.6.2 shall also apply. 7.6.4.5 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) QEAA-7.6.4.5-01: If the digital signature is a JAdES-B-B as specified in ETSI TS 119 182-1 [11] then the requirements specified in clause 5.6.3 shall also apply. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.6.5 Requirements for JSON-LD W3C-VC EAA with embedded proofs | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.6.5.1 General requirements | EAA-7.6.5.1-01: A JSON-LD W3C-VC EAA secured using embedded proofs shall include the proof property, as specified in "Verifiable Credentials Data Model v2.0" [1] clause 4.12. EAA-7.6.5.1-02: The contents of the proof property should be as specified in W3C Recommendation: "Verifiable Credential Data Integrity v1.0" [26]. 8 Implementation of EAA based on X.509 Attribute Certificates (X.509-AC) |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.1 General requirements | Clause 8 of the present document defines a realization of EAA based on X.509 Attribute certificates as specified in IETF RFC 5755 [6]. The EAAs implemented according to clause 8 of the present document, will be designated as X.509-AC EAA hereinafter. The informative Annex B of the present document contains the details of how to reach the file that contains the ASN.1 definitions for X.509-AC EAAs. This separate file is a convenience tool and its content is informative. In case of any discrepancy between the definitions of the types and data elements given in the present document and the ones given in the separate file, the definitions given in the present document shall take precedence. NOTE: The file containing the ASN.1 definitions includes a preamble with, among other parts, import and export sentences, so that its contents can be processed by software. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2 EAA metadata | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.1 EAA specification | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.1.1 EAA type | EAA-8.2.1.1-01: The etsi-eaaType extension specified in the present clause shall implement the semantics specified in clause 4.2.1.2 of the present document. EAA-8.2.1.1-02: An X.509-AC EAA may incorporate the extension etsi-eaaType, which is defined below. -- Arc for all the identifiers of the extensions of X.509-AC EAAs ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 55 id-etsi-eaa-x509AC-ext-root OBJECT IDENTIFIER ::= { itu-t(0) identified-organization(4) etsi(0) id- qeaas-profile(194721) } -- Subarc for identifiers of extensions applicable to all EAAs id-etsi-eaa-x509AC-nqext OBJECT IDENTIFIER ::= { id-etsi-eaa-x509AC-ext-root 2 } -- EAA Type attestation extension id-etsi-eaa-x509AC-ext-type OBJECT IDENTIFIER ::= { id-etsi-eaa-x509AC-nqext 1 } etsi-eaaType EXTENSION ::= { SYNTAX EAAType IDENTIFIED BY id-etsi-eaa-x509AC-ext-type} EAAType ::= UTF8String EAA-8.2.1.1-03: The value of the etsi-eaaType extension shall be a URI identifying the type of the X.509-AC EAA. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.1.2 EAA context | EAA-8.2.1.2-01: An X.509-AC EAA shall have its version field set to v2. This will explicitly set the EAA context as follows: • All the information about the issuer shall be derived from the values of the following members: issuer field, issuerUniqueID field, authorityKeyIdentifier extension, authorityInfoAccess extension, crlDistributionPoints extension, and EAAType extension. NOTE: IETF RFC 5755 [6] specifies extensions as optional components in an Attribute Certificate. • All the information required about the subject shall be derived from the values of the following members: holder field. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.1.3 EAA schema | EAA-8.2.1.3-01: An X.509-AC EAA shall not have any component implementing the semantics specified in clause 4.2.1.4 of the present document. NOTE: See [i.6], which specifies among other things "a data model for catalogue of attributes, guidance on Attestation Rulebooks, attestation type data models and applicable Application Programming Interface (API) for management of machine-readable attestation schemas". |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.2 EAA category | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.2.1 General requirements | EAA-8.2.2.1-01: X.509-AC EAAs issued by EAA Providers registered in the European Union, which are neither X.509-AC QEAAs nor X.509-AC PuB-EAAs, shall not include any extension for signalling a specific category. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.2.2 Requirements for EU Qualified EAA (QEAA) | QEAA-8.2.2.2-01: An X.509-AC QEAA shall incorporate the extension etsi-qeaaStatements, which is defined below. -- Subarc for extensions applicable only to QEAA and PuB-EAA id-etsi-qeaas-x509AC-prof-identifiers OBJECT IDENTIFIER ::= { id-etsi-eaa-x509AC-ext-root 1 } -- QEAA-STATEMENT class definition QEAA-STATEMENT ::= CLASS { &statementId OBJECT IDENTIFIER UNIQUE, &Type OPTIONAL } WITH SYNTAX { IDENTIFIED BY &statementId ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 56 [SYNTAX &Type] } -- QEAAStatements definition id-qeaas-qeaaStatements OBJECT IDENTIFIER ::= { id-etsi-qeaas-x509AC-prof-identifiers 1 } etsi-qeaaStatements EXTENSION ::= { SYNTAX QEAAStatements IDENTIFIED BY id-qeaas-qeaaStatements } QEAAStatements ::= SEQUENCE OF QEAAStatement QEAAStatement ::= SEQUENCE { statementId QEAA-STATEMENT.&statementId({SupportedStatements}), statementInfo QEAA-STATEMENT.&Type ({SupportedStatements}{@statementId}) OPTIONAL } SupportedStatements QEAA-STATEMENT ::= { etsi-qeaaStatement-1 | etsi-eaaPubAStatement-1} QEAA-8.2.2.2-02: The etsi-qeaaStatements extension shall not be marked as critical. QEAA-8.2.2.2-03: An X.509-AC QEAA shall incorporate the QEAA-Statement that is defined below. -- EUqeaaCompliance QEAAStatement definition id-etsi-qeaas-EUqeaaCompliance OBJECT IDENTIFIER ::= { id-qeaas-qeaaStatements 1} etsi-qeaaStatement-1 QEAA-STATEMENT ::= { IDENTIFIED BY id-etsi-qeaas-EUqeaaCompliance } 8.2.2.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-8.2.2.3-01: An X.509-AC PuB-EAA shall incorporate the extension etsi-qeaaStatements specified in clause 8.2.2.2 of the present document. PuB-EAA-8.2.2.3-02: The etsi-qeaaStatements extension shall not be marked as critical. PuB-EAA-8.2.2.3-03: An X.509-AC PuB-EAA shall incorporate the QEAA-Statement that is defined below. -- eaaPubA-EUeaaPubACompliance QEAAStatement definition id-etsi-eaaPubA-EUeaaPubACompliance OBJECT IDENTIFIER ::= { id-qeaas-qeaaStatements 2} etsi-eaaPubAStatement-1 QEAA-STATEMENT ::= { IDENTIFIED BY id-etsi-eaaPubA-EUeaaPubACompliance } |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.3 EAA identifier | EAA-8.2.3-01: An X.509-AC EAA shall contain the serialNumber field, whose value, with the value of the issuer field, shall identify the EAA itself. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.4 EAA issuer identifier | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.4.1 General requirements | EAA-8.2.4.1-01: An X.509-AC EAA shall contain the issuer field as specified in IETF RFC 5755 [6]. EAA-8.2.4.1-02: Its value shall be a distinguished name (dNSName choice of GeneralNames type as specified in IETF RFC 5280 [9]) within v2Form choice of AttCertIssuer type. EAA-8.2.4.1-03: An X.509-AC EAA may contain the issuerUniqueID field, as specified in IETF RFC 5755 [6], clause 4.2.8. Requirements when the EAA issuer is a legal person EAA-8.2.4.1-04: If the X.509-AC EAA issuer is a legal person, the issuer field shall not contain any of the X.509 attributes providing details of natural persons. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 57 EAA-8.2.4.1-05: Where a registration identifier is applicable, the issuer field may contain the attribute organizationIdentifier attribute. EAA-8.2.4.1-06: The value of the organizationIdentifier attribute may be built according to the rules defined in clause 5.1.4 of ETSI EN 319 412-1 [16] to build the value of the organizationIdentifier attribute in the subject field of an X.509 certificate. Requirements when the EAA issuer is a natural person EAA-8.2.4.1-07: If the X.509-AC EAA issuer is a natural person, the issuer field shall not contain any of the X.509 attributes providing details of legal persons. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.4.2 Requirements for EU Qualified EAA (QEAA) | QEAA-8.2.4.2-01: In an X.509-AC QEAA the issuer field shall contain, at least the following X.509 attributes: country (C), and organizationName (O). QEAA-8.2.4.2-02: If the issuer of the X.509-AC QEAA is a legal person and if a registration identifier is applicable, the issuer field shall contain the attribute organizationIdentifier attribute. QEAA-8.2.4.2-03: The value of one instance of the organizationIdentifier attribute shall be built according to the rules defined in clause 5.1.4 of ETSI EN 319 412-1 [16] to build the value of the organizationIdentifier attribute in the subject field of an X.509 certificate. QEAA-8.2.4.2-04: In an X.509-AC QEAA the extension identified by the OID id-pe-authorityInfoAccess shall contain one instance of type AccessDescription as with its accessMethod field set to id-ad- caIssuers, and its accessLocation field shall point to the certificate of the X.509-AC QEAA issuer for supporting the validation of the signature of the X.509-AC QEAA. NOTE: The requirement on the value of accessMethod field is included for meeting the requirements defined in eIDAS 2.0 annex V. 8.2.4.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-8.2.4.3-01: In an X.509-AC PuB-EAA the issuer field shall contain, at least the following X.509 attributes: country (C), and organizationName (O). PuB-EAA-8.2.4.3-02: Where a registration identifier is applicable, one instance of the organizationIdentifier attribute shall be present and built according to the rules defined in clause 5.1.4 of ETSI EN 319 412-1 [16] to build the value of the organizationIdentifier attribute in the subject field of an X.509 certificate. PuB-EAA-8.2.4.3-03: In an X.509-AC PuB-EAA the extension identified by the OID id-pe- authorityInfoAccess shall contain one instance of type AccessDescription as with its accessMethod field set to id-ad-caIssuers, and its accessLocation field shall point to the certificate of the X.509-AC PuB-EAA issuer for supporting the validation of the signature of the X.509-AC PuB-EAA. NOTE: The requirement on the value of accessMethod field is included for meeting the requirements defined in eIDAS 2.0 annex VII. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.5 EAA and attribute subject identifiers and pseudonyms | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.5.1 EAA subject identifier | EAA-8.2.5.1-02: In an X.509-AC EAA the EAA subject identifier shall be present in the holder field. EAA-8.2.5.1-03: In an X.509-AC EAA the holder field shall include the objectDigestInfo field, which in turn, shall have the publickeycert value as specified in IETF RFC 5755 [6], clause 7.3. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 58 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.