hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.4 TE information URI | Description: The TEInformationURI component specifies the URI(s) where users (e.g. relying parties) can obtain TE-specific information. Format: The TEInformationURI component shall be a sequence of multilingual pointers (see clause 6.1.4). Semantics: Profiles making use of this extension should provide requirements reg... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5 TE information extensions | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.0 General | Description: The TEInformationExtensions component may be used by scheme operators to provide specific TE-related information, to be interpreted according to the specific scheme's rules. Format: Sequence of TE extensions whose format is left open. Semantics: Each TE information extension may be selected by the scheme o... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.1 Other associated bodies extension | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.1.0 General | Description: The OtherAssociatedBodies component specifies information about bodies different from the TE identified through the TEName component (see clause 6.5.1) that are associated with the identified TE in a way that is meaningful in the context of the LoTE scheme and with respect to the listed services. Format: T... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.1.1 Associated body | Description: The AssociatedBody component specifies information about a body different from the TE identified through the TEName component (see clause 6.5.1) that is associated with the identified TE in a way that is meaningful in the context of the LoTE scheme and with respect to the listed services. Format: The Assoc... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.1.2 Associated body name | Description: The AssociatedBodyName component specifies the name of the body that is associated with the identified TE in a way that is meaningful in the context of the LoTE scheme and with respect to the listed services. Format: The AssociatedBodyName component shall be a sequence of multilingual character strings (se... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.1.3 Associated Body trade name | Description: The AssociatedBodyTradeName component specifies an official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the body associated to the TE. It may additionally be used to specify an alternative name under which the body iden... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.1.4 Associated body address | 6.5.5.1.4.0 General Description: The AssosciatedBodyAddress component specifies the address of the body identified through the AssocitedBodyName component (clause 6.5.1) for both postal and electronic communications. Format: The AssosciatedBodyAddress component shall contain the below sub-components: • The AssosciatedB... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.1.5 Associated body information URI | Description: The AssociatedBodyInformation component specifies the URI(s) where users (e.g. relying parties) can obtain information specific to that body. Format: The AssociatedBodyInformation shall be a sequence of multilingual pointers (see clause 6.1.4). Semantics: Profiles making use of this extension should provid... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.1.6 Associated body type identifier | Description: The AssociatedBodyTypeIdentifier component specifies the identifier of the type of body associated with the TE. Format: The AssociatedBodyTypeIdentifier component shall be an indicator expressed as a URI. Semantics: LoTE profiles making use of this extension shall specify, when they require the usage of th... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.5.1.7 Associated body information extensions | Description: The AssociatedBodyInformationExtensions component may be used by scheme operators to provide specific Associated Body-related information, to be interpreted according to the specific scheme's rules. Format: Sequence of Associated Body extensions whose format is left open. Semantics: Each Associate Body inf... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6 Service information | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.0 General | Description: The ServiceInformation component provides information about a trusted entity service. Format: This component shall contain the below sub-components: • The ServiceName component (see clause 6.6.2). • The ServiceDigitalIdentity component (see clause 6.6.3). This component may optionally contain the below sub... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.1 Service type identifier | Description: The ServiceTypeIdentifier component specifies the identifier of the service type. Format: The ServiceTypeIdentifier component shall be an indicator expressed as a URI. Semantics: The quoted URI shall be a URI value registered and described by the scheme operator or another entity. LoTE profiles should defi... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.2 Service name | Description: The ServiceName component specifies the name under which the TE identified in 'TE name' (clause 6.5.1) provides the service whose type is identified in 'Service type identifier' (clause 6.6.1). Format: The ServiceName component shall be a sequence of multilingual character strings (see clause 6.1.4). Seman... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.3 Service digital identity | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.3.0 General | Description: The ServiceDigitalIdentity component specifies one or multiple digital identifiers identifying the service with the type they are associated to (as identified in 'Service type identifier', clause 6.6.1). NOTE: In some context, this component can be used to specify one and only one service digital identifie... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.3.1 X509 certificate | Description: The X509Certificate component specifies a public key certificate. Format: The X509Certificate component shall be a Base64 string. Semantics: The value of the string shall be a Base64 encoded X.509 certificate [12]. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.3.2 X509 subject name | Description: The X509SubjectName component specifies a Distinguished Name [12]. Format: The X509SubjectName component shall be a string. Semantics: The value of the X509SubjectName component shall be a Distinguished Name encoded as a string. The Distinguished Name should be encoded according to the encoding rules speci... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.3.3 Public key value | Description: The PublicKeyValue component specifies the value of a public key. Format: The format of the PublicKeyValue component is left open and is syntax-specific. Semantics: The value of the PublicKeyValue component shall be the same public key as the one present within any X509Certificate element listed in the par... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.3.4 Subject key identifier | Description: The SubjectKeyIdentifier component specifies an identifier of the public key. Format: The format of the PublicKeyValue component is left open and is syntax-specific. Semantics: The value of the PublicKeyValue component shall be the same public key as the one present within any X509Certificate element liste... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.3.5 OtherId | Description: The OtherId component specifies an identifier whose format is left open. Format: The format of the OtherId component is left open. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.4 Service current status | Description: The ServiceStatus component specifies the identifier of the current status of the service. Format: The ServiceStatus component shall be an identifier expressed as a URI. Semantics: LoTE profiles should define a set of service current status URI values and their corresponding semantics. LoTESO may define a ... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.5 Current status starting date and time | Description: The StatusStartingTime component specifies the date and time on which the current approval status became effective. Format: The StatusStartingTime component shall be a Date-time value (see clause 6.1.3). Semantics: Coordinated Universal Time (UTC) at which the current approval status became effective. LoTE... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.6 Scheme service definition URI | Description: The SchemeServiceDefinitionURI component specifies the URI(s) where relying parties can obtain service- specific information provided by the LoTE scheme operator. Format: The SchemeServiceDefinitionURI component shall be a sequence of multilingual pointers (see clause 6.1.4). Semantics: The referenced URI(... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.7 Service supply points | Description: The ServiceSupplyPoints component specifies one or more URIs where relying parties can access the service, or component services or other types of services related with the service. Optionally, for each URI it specifies the type of service that can be accessed at this URI. Format: The ServiceSupplyPoints c... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.8 TE service definition URI | Description: The TEServiceDefinitionURI component specifies the URI(s) where relying parties can obtain service-specific information provided by the TE. Format: The TEServiceDefinitionURI component shall be a sequence of multilingual pointers (see clause 6.1.4). Semantics: The referenced URI(s) shall provide a path to ... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.9 Service information extensions | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.9.0 General | Description: The ServiceInformationExtensions component specifies specific service-related information. Format: The ServiceInformationExtensions component shall be a sequence of ServiceInformationExtension components whose format is left open. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 37 Semantics: LoTE profiles may define... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.6.9.1 Service unique identifier extension | Description: The ServiceUniqueIdentifier component specifies a scheme-specific unique identifier of service. Format: The ServiceUniqueIdentifier component shall be a URI. Semantics: The value of the URI shall identify uniquely and unambiguously the associated service. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.7 Service history instance | Description: The ServiceHistoryInstance component provides historical information about a trusted entity service. Format: The ServiceHistoryInstance component shall contain the below sub-components: • The ServiceName element (see clause 6.6.2). • The ServiceDigitalIdentity element (see clause 6.6.3). • The ServiceStatu... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.8 Digital signature | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.8.0 General | Lists of trusted entities shall be signed by means of an AdES digital signature at conformance level baseline B. The AdES digital signature may either be present within the LoTE itself, when the signature format provides for such a relationship between the signed data and the signature, or the signature itself encapsul... |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.8.1 Signature component | Description: The Signature component shall encapsulate an AdES digital signature authenticating the LoTE. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 39 Annex A (normative): Bindings A.1 JSON bindings A JSON binding for a scheme-explicit LoTE is provided in the following repository: • https://forge.etsi.org/rep/esi/x19_60201... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 1 Scope | The present document: 1) Specifies three (3) realizations for Presentations of Electronic Attestation of Attributes (EAAP hereinafter) built on the realizations of Electronic Attestation of Attributes (EAA hereinafter), specified in ETSI TS 119 472-1 [5] namely: - SD-JWT VC EAAP (clause 4.1); - ISO/IEC-mdoc EAAP (claus... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 2 References | |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 3 Definition of terms, symbols and abbreviations | |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 119 471 [i.1], ETSI TS 119 472-1 [5], ETSI TR 119 462 [i.2], Architecture and Reference Framework (ARF) version 2.4.0 [i.3] and the following apply: Electronic Attestation of Attributes Presentation (EAAP): data derived from an EAA that is presented t... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 3.2 Symbols | Void. |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BLE Bluetooth® Low Energy CBOR Concise Binary Object Representation COSE CBOR Object Signing and Encryption DCQL Digital Credentials Query Language EAA Electronic Attestation of Attributes EAAP Electronic Attestation of Attributes Presentation... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 3.4 Notation | The present document assigns one identifier for each requirement. These identifiers result from the concatenation of the following two components: 1) A topic identifier, for signalling the topic targeted by the requirement. 2) A number of 2 digits. For each topic the number will start in 01 and it will increase in one ... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 4.1 EAAP implementation based on SD-JWT VC | The present clause specifies a realization of EAAP for the SD-JWT VC EAA defined in clause 5 of ETSI TS 119 472-1 [5]. The EAAPs implemented according to the present clause will be designated as SD-JWT VC EAAP hereinafter. EAAP-SD-JWT VC-01: If the SD-JWT VC EAA contains the cnf claim, the corresponding SD-JWT VC EAAP ... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 4.2 EAAP implementation based on ISO/IEC-mdoc | The present clause specifies a realization of EAAPs for the ISO/IEC-mdoc EAAs defined in clause 6 of ETSI TS 119 472-1 [5]. NOTE 1: Clause 6 of ETSI TS 119 472-1 [5] defines different requirements for ISO/IEC-mdoc EAAs that are mobile Driving Licenses (mDL) and ISO/IEC-mdoc EAAs that are NOT mDLs in terms of data eleme... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 5 ISO/IEC-mdoc profile | |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 5.1 Introduction | Clause 5 and its subclauses define a profile for a protocol allowing a RP to request EAAPs or PIDs to the EUDI Wallet, and the EUDI Wallet to send the requested EAAPs/PIDs to the RP using a non-API mediated transmission mechanism, built on ISO/IEC 18013-5 [10]. The rest of clause 5 is organized as follows: • Clause 5.2... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 5.2 Requirements on EUDI Wallet and RP support | ISO/IEC 18013-SUPPORT-01: Wallet Units, PID Providers, Attestation Providers, Wallet Providers, and Relying Parties shall not support server retrieval as specified in ISO/IEC 18013-5 [10] for requesting and presenting PID or attestation attributes. ISO/IEC 18013-SUPPORT-02: The EUDI Wallet shall meet the requirements d... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 5.3 Protocol requirements | |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 5.3.1 General requirements | ISO/IEC 18013-GEN-01: All the mandatory requirements for device retrieval data structures defined in [10] shall apply. ISO/IEC 18013-GEN-02: All the optional requirements for device retrieval data structures defined in [10] shall remain optional unless stated otherwise in the present document. ISO/IEC 18013-GEN-03: If ... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 5.3.2 ISO/IEC-mdoc EAAP Request contents | The present clause defines requirements for the content of the EAAP Request that have to be sent from the RP to the EUDI Wallet. ISO/IEC 18013-REQ-01: All the elements of the docRequests array shall contain the readerAuth member. NOTE 1: ISO/IEC 18013-5 [10] defines readerAuth member as an instance of ReaderAuth type, ... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 5.3.3 ISO/IEC-mdoc EAAP Response profile | The present clause defines requirements for the DeviceResponse message type. ISO/IEC 18013-RESP-01: In response to a DeviceRequest message sent by the RP, the WU shall generate a DeviceResponse message as specified in ISO/IEC 18013-5 [10]. |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6 Profile built on OpenID4VC-HAIP | |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.1 Introduction | Clause 5 and its subclauses define a profile for a protocol allowing a RP to request EAAPs or PIDs to the EUDI Wallet, and the EUDI Wallet to send the requested EAAPs/PIDs to the RP using two mechanisms of transmission for requests and responses, namely: 1) A non-API mediated transmission mechanism, built on OpenID4VC-... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.2 Requirements on EUDI Wallet and RP support | OIDFVP-HAIP-SUPPORT-01: The EUDI Wallet shall meet the requirements defined in clauses 6.3 and 6.4 of the present document. NOTE 1: The former requirement implies that the EUDI Wallet supports the non-API mediated mechanism for presentations flows built on OpenID4VC-HAIP [11]. OIDFVP-HAIP-SUPPORT-02: The EUDI Wallet ma... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.3 Common requirements for all the transmission mechanisms | |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.3.1 General requirements | OIDFVP-HAIP-GEN-01: All the mandatory requirements defined in clauses 5, 5.3, 7 and 8 of HAIP [11] shall apply. OIDFVP-HAIP-GEN-02: All the optional requirements defined in clauses 5, 5.3, 7 and 8 of HAIP [11] shall remain optional unless stated otherwise in the present document. OIDFVP-HAIP-GEN-03: If the present docu... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.3.2 Authorization Request (EAAP request) profile | |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.3.2.1 General requirements | OIDFVP-HAIP-COMMON-REQ-01: The Authorization Request shall use the Client Identifier Prefix x509_hash. |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.3.2.2 Requirements for the Request Object | The present clause defines requirements for the Request Object regardless the transmission mechanism used. NOTE 1: IETF RFC 9101 [6] mandates that the Request Object contains "all the parameters (including extension parameters) used to process the OAuth 2.0 (IETF RFC 6749) authorization request" except the request and ... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.3.3 Authorization Response (EAAP response) profile | OIDFVP-HAIP-COMMON-RESP-01: The EUDI Wallet shall encrypt the authorization response. 6.4 Specific requirements for non-API mediated transmission mechanism |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.4.1 General requirements | OIDFVP-HAIP-REDIRECTS-01: All the mandatory requirements defined in clause 5.1 of HAIP [11] shall apply. OIDFVP-HAIP-REDIRECTS-02: All the optional requirements defined in clause 5.1 of HAIP [11] shall remain optional unless stated otherwise in the present clause. OIDFVP-HAIP-REDIRECTS-03: The EUDI Wallet shall support... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.4.2 Requirements for the Request Object | The present clause defines requirements for the Request Object for the non-API mediated transmission mechanism. OIDFVP-HAIP-REDIRECTS_RO-01: The JWS Protected Header of the JWS signature on the RO shall incorporate the x5c header parameter. OIDFVP-HAIP-REDIRECTS_RO-02: The x5c header parameter in the JWS Protected Head... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.5.1 OpenID4VC-HAIP-related requirements | OIDFVP-HAIP-API-01: All the mandatory requirements defined in clause 5.2 of HAIP [11] shall apply. OIDFVP-HAIP-API-02: All the optional requirements defined in clause 5.2 of HAIP of HAIP [11] shall remain optional unless stated otherwise in the present clause. OIDFVP-HAIP-API-03: The EUDI Wallet shall not support Autho... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.5.2 Additional requirements | OIDFVP-HAIP-ADD-API-01: The EUDI Wallet shall by default disclose the presence of all stored EAAs' type to the mediating API that works in accordance with clause 5.2 of [11], but it shall not disclose the attributes and their values in these EAAs. NOTE 1: The attribute value restriction applies even if such disclosure ... |
c3f07c43da46e48e38c872aeb467d6da | 119 472-2 | 6.6 Security considerations | The security considerations in clause 14 of OpenID4 VP [7] apply. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 19 Annex A (normative): EAAP implementation based on JSON-LD W3C VC A.1 Introduction The present annex specifies requirements for generating EAAPs for the JSON-LD W3C VC EAA specified in clause 7 of ETSI TS 119 472... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 1 Scope | The present document: 1) Specifies a data model (semantics) for Electronic Attestations of Attributes, a new object defined by the Regulation (EU) 2024/1183 [i.2] clause 4. 2) Defines data model (semantics) requirements for two types of Electronic Attestations of Attributes, namely: the Qualified Attestations of Attrib... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 2 References | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 3 Definition of terms, symbols and abbreviations | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 119 471 [i.1] and the following apply: EAA administrative validity period: date(s) from and/or up to which the attributes in the EAA are valid, which are represented as attribute(s) in the attestation NOTE: Definition taken from the ARF [i.5]. EAA tec... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 3.2 Symbols | Void. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC Attribute Certificate API Application Programming Interface ARF EU Architecture and Reference Framework ASN.1 Abstract Syntax Notation 1 CBOR Concise Binary Object Representation CIR Commission Implementing Regulation COSE CBOR Object Signi... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 3.4 Notation | The present document assigns one identifier for each requirement. The present document uses the terms "signature" and "digital signature" as defined in ETSI TR 119 001 [i.4], and therefore, they refer to objects that are able to support electronic signatures, advanced electronic signatures, qualified electronic signatu... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4 Semantics of Electronic Attestation of Attributes | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.1 Introduction. Semantic areas for EAA | The present document specifies the semantics of EAA data as follows: 1) Clause 4.2 EAA metadata defines semantics for EAA metadata. 2) Clause 4.3 Attested attributes defines semantics for EAA data directly related with the incorporation of attested attributes. 3) Clause 4.4 defines semantics for attested attributes met... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2 EAA metadata | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.1 EAA specification | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.1.1 Introduction | The present clause defines requirements for a set of metadata that allow access to the EAA specification details, like the EAA type, all the individual components of the EAA, the inner structure of the EAA, how to handle the EAA, etc. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.1.2 EAA type | EAA-4.2.1.2-01: This component shall indicate the type of the EAA. EAA-4.2.1.4-02: An EAA shall incorporate the EAA type. EAA-4.2.1.2-03: The incorporation, value, and placement of the EAA type data shall depend on the specific EAA implementation. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.1.3 EAA context | EAA-4.2.1.3-01: If the components of the EAA have URLs as names, the EAA shall include one or more context components. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 16 EAA-4.2.1.3-02: The EAA context component shall reference a document defining a map between URLs identifying components of an EAA and short-forms aliases for ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.1.4 EAA schema | EAA-4.2.1.4-01: The EAA schema shall contain details that allow to verify that the contents and the structure of an attribute or an EAA are conformant against a specific schema. EAA-4.2.1.4-02: An EAA may incorporate a sequence of one or more references allowing to retrieve the EAA schema. EAA-4.2.1.4-03: Each referenc... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.2 EAA category | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.2.1 General requirements | EAA-4.2.2-01: The EAA category shall be an explicit signal identifying the category of the EAA in the context where the EAA has been issued. EAA-4.2.2-02: An EAA may include the EAA category. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.2.2 Requirements for EU Qualified EAA (QEAA) | QEAA-4.2.2.2-01: A QEAA shall include the EAA category, signalling its condition of QEAA. QEAA-4.2.2.2-02: For QEAA realizations using URIs as identifiers of the category, the value of the EAA category shall be the following URN: urn:etsi:esi:eaa:eu:qualified. NOTE: These requirements meet the requirement (a) in Annex ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.3 EAA identifier | EAA-4.2.3-01: The EAA identifier shall contain a value that allows to unambiguously identify the EAA itself. EAA-4.2.3-02: An EAA may incorporate the EAA identifier. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 17 EAA-4.2.3-03: The incorporation, value, and placement of the EAA identifier shall depend on the specific EAA im... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.4 EAA issuer identifier | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.4.1 General requirements | EAA-4.2.4.1-01: The EAA issuer identifier shall have a value that unambiguously identifies the EAA Trust Service Provider which issues the EAA. EAA-4.2.4.1-02: An EAA may incorporate the EAA issuer identifier. EAA-4.2.4.1-03: The incorporation, value, and placement of the EAA issuer identifier shall depend on the speci... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.4.2 Requirements for EU Qualified EAA (QEAA) | QEAA-4.2.4.2-01: A QEAA shall incorporate the EAA issuer identifier. QEAA-4.2.4.2-02: A QEAA shall include an identifier of the EU Member State, in which the QEAA issuer is registered. QEAA-4.2.4.2-03: The value of the identifier of an EU Member State shall be as specified in requirement EAA-4.2.4.1-05 of the present d... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.5 EAA issued on behalf | EAA-4.2.5-01: If the EAA is issued on behalf of another entity, the EAA may incorporate an indication of this fact. EAA-4.2.5-02: The incorporation, value, and placement of this indication shall depend on the specific EAA implementation. EAA-4.2.5-03: If the EAA is issued on behalf of another entity, the EAA may incorp... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.6 EAA subject and attribute subject identifiers and pseudonyms | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.6.1 Introduction | The present clause defines requirements on identifiers identifying the EAA subject and the attribute subjects. The present clause also defines requirements on pseudonyms for the EAA subject and the attribute subjects. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.6.2 The EAA subject identifier | EAA-4.2.6.2-01: An EAA may include the EAA subject identifier, or the pseudonym of the EAA subject, or none of them. NOTE 1: The former requirement implies that there can be EAAs that do not include any identifier or pseudonym of the EAA subject. NOTE 2: This presence of the EAA subject can be provided by a component s... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.6.3 The EAA subject pseudonym | EAA-4.2.6.3-01: The presence of the EAA subject pseudonym instead of the EAA subject identifier shall be clearly indicated. EAA-4.2.6.3-02: The mechanism used for incorporating the EAA subject pseudonym within the EAA, shall depend on the specific EAA implementation. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.6.4 The attribute subject identifier | EAA-4.2.6.4-01: The EAA may bind each attribute either to the identifier or to the pseudonym of the entity (attribute subject) that this attribute refers to. NOTE 1: The former requirement implies that there can be EAAs that do not bind any attribute to any identifier or pseudonym of an entity. NOTE 2: In an EAA where ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.6.5 The attribute subject pseudonym | EAA-4.2.6.5-01: An EAA may incorporate pseudonym(s) for attribute subject(s). EAA-4.2.6.5-02: The mechanism used for incorporating the pseudonym(s) for attribute subject(s) within the EAA, shall depend on the specific EAA implementation. EAA-4.2.6.5-03: The mechanism used for binding one attribute or a set of attribute... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.6.6 Additional requirements | EAA-4.2.6.6-01: If the EAA contains several attribute subject identifiers, one of them shall be the EAA subject identifier. EAA-4.2.6.6-02: If the EAA contains attribute subject pseudonyms, does not contain any attribute subject identifier, and does not contain the EAA subject identifier, then the pseudonym of the EAA ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.6.7 Requirements for EU Qualified EAA (QEAA) | QEAA -4.2.6.7-01: A QEAA shall include either the EAA subject identifier or the pseudonym of the EAA subject. QEAA-4.2.6.7-02: All the attributes present within a QEAA shall refer to one entity: the QEAA subject. NOTE: These requirements meet the requirement (c) in Annex V of Regulation (EU) 2024/1183 [i.2] for QEAA, w... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.