hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.17 Scheme extensions | Description: The SchemeExtensions component provides specific scheme-related information and enhancements that do not require a change in the version identifier, which can be interpreted by all accessing parties according to the specific scheme's rules. Format: The SchemeExtensions component shall contain a sequence of Scheme extensions whose format is left open. Each extension shall have an indication of its criticality. Semantics: Each extension of the sequence shall be selected by the LoTESO according to the information it wishes to convey within its LoTE. The meaning and value of each extension shall be defined by its source specifications being either the LoTESOs own definition or any other extension definition produced by another entity, such as a community or federation of schemes, a standards body, etc. The criticality indication shall have the same semantics as with extensions in X.509-certificates [12]. A system using LoTEs shall reject the LoTE if it encounters a critical extension it does not recognize, while a non-critical extension may be ignored if it is not recognized. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4 Trusted Entities List | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.0 General | Presence: If no trusted entity is or was approved in the context of the list of trusted entities scheme, this component shall not be present. If one or more trusted entity services are or were approved under the LoTE scheme, this component shall be present. Description: The TrustedEntitiesList component provides a list of trusted entities and their services approved in accordance with the list of trusted entities scheme. Format: This component shall contain a sequence of TrustedEntity components. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 25 Semantics: It shall contain a sequence identifying each trusted entity providing one or more of approved services, with details on the status and status history of each of the trusted entities' services, as illustrated in Figure 1 (see clause 5). |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.1 Trusted entity | Description: The TrustedEntity component provides information about a trusted entity and its corresponding services approved in accordance with the list of trusted entities scheme. Format: This component shall contain the below components: • The TrustedEntityInformation element (see clause 6.5) The TrustedEntityServices element, which shall be a sequence of TrustedEntityService elements. Each of such Service History component, when present, is a sequence of Service History Instance components (see clause 6.7). Semantics: It shall provide information about a trusted entity and one or more of approved services associated to it, with details on the status and status history of each of the services, as illustrated in figure 1 (see clause 5). |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.2 Trusted entity services | Description: The TrustedEntityServices component contains a sequence identifying each of the TE's recognized services and the approval status (and history of that status) of that service. Format: This component shall be a sequence of TrustedEntityService components. Semantics: When historical information is to be retained (see clause 6.3.12), at least one service shall be listed, even if the information held is entirely historical. When the retention of historical information about listed services is required by clause 6.3.12, that historical information shall be retained even if the service's present status would not normally require it to be listed (e.g. the service is not considered as reliable anymore within the context of the LoTE scheme). Thus, a TE shall be included even when its only listed service is in such a state, so as to preserve the history. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.3 Trusted entity service | Description: The TrustedEntityService component provides information about a trusted entity service approved in accordance with the list of trusted entities scheme. Format: • This component shall contain the below components: - The ServiceInformation element (see clause 6.6.0). ETSI ETSI TS 119 602 V1.1.1 (2025-11) 26 • This component may optionally contain the below components: - The ServiceHistory component which shall be a sequence of ServiceHistoryInstance elements (see clause 6.7). The ServiceHistory component shall be present only when historical information is applicable to the related service. In the case the service has no history prior to the current status (i.e. a first recorded status or history information not retained by the scheme operator) this field shall not be present. Semantics: It shall contain information of an approved services, with details on the status and status history of that service. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.4.4 Service history | Description: The ServiceHistory component specifies historical information on listed trusted entity services as a sequence of all previous status entries which the scheme has recorded for the given TE service. Format: The ServiceHistory component shall be a sequence of ServiceHistoryInstance elements (see clause 6.7). Semantics: For each change in TE service approval status which occurred within the historical information period as specified in clause 6.3.12, information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective). |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5 Trusted entity information | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.0 General | Description: The TrustedEntityInformation component provides information about a trusted entity. Format: This component shall contain the below components: • The TEName element (see clause 6.5.1). • The TEAddress element (see clause 6.5.3). • The TEInformationURI element (see clause 6.5.4). This component may optionally contain the below components: • The TETradeName element (see clause 6.5.2). • The TEInformationExtensions element (see clause 6.5.5). Semantics: It shall contain information about the trusted entity. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 27 |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.1 TE name | Description: The TEName component specifies the name of the legal entity, or when applicable the natural person, responsible for the TE's services that are or were recognized by the scheme, in particular for the TE's services that are or were approved under the applicable scheme. Format: The TEName component shall be a sequence of multilingual character strings (see clause 6.1.4). Semantics: The name of the legal entity, or when applicable the natural person, responsible for the TE's services shall be the name which is used in formal legal registrations and official records and to which any formal communication, whether physical or electronic, should be addressed. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.2 TE trade name | Description: The TETradeName component specifies an official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the TE. It may additionally be used to specify an alternative name under which the TE identifies itself in the specific context of the provision of those of its services which are to be found in this LoTE under its 'TE name' (clause 6.5.1) entry. Format: The TETradeName component shall be a sequence of multilingual character strings (see clause 6.1.4). Semantics: It shall include an official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the TE. It may additionally include any name under which the legal entity, or when applicable the natural person, responsible for the TE operates, in the specific context of the delivery of those of its services which are to be found in this LoTE. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.3 TE address | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.3.0 General | Description: The TEAddress component specifies the address of the legal entity or mandated organization, or when applicable the natural person, identified in the 'TE name' field (clause 6.5.1) for both postal and electronic communications. Format: The TEAddress component shall contain the below sub-components: • The TEPostalAddress element (see clause 6.5.3.1). • The TEElectronicAddress element (see clause 6.5.3.2) |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.3.1 TE postal address | Description: The TEPostalAddress component specifies the postal address of the TE identified in clause 6.5.1, with the provision for the inclusion of the address in multiple languages. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 28 Format: As specified in clause 6.3.5.1. Semantics: This shall be a postal address at which the TE provides a customer care or help line service, operated through conventional (physical) mail and processed as would be expected by normal business services. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.5.3.2 TE electronic address | Description: The TEElectronicAddress component specifies an email address, a web-site URI, and an optional telephone number of the TE identified in clause 6.5.1, to be used for electronic communications. Format: As specified in clause 6.3.5.2. Semantics: The e-mail address, and the telephone number when present, shall be an address, and respectively a phone number when present, at which the TE provides a customer care or help line service which is related to the listed services and which are processed as would be expected by normal business services. As regards a web-site URI, this shall lead to a capability whereby the user may communicate with a customer care or help line service which is related to the listed services and which is processed as would be expected by normal business services. |
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 regarding the information available at the listed URI(s). |
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 operator according to the meaning and information it wishes to convey within its LoTE. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 29 The meaning of each extension is hence defined by its source specification, that specification being either the scheme operator's own definition or any other extension definition produced by another entity, such as a community or federation of schemes, a standards body, etc. |
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: The OtherAssociatedBodies component shall be a sequence of AssociatedBody elements which is defined here below. Semantics: Each body identified in the AssociatedBody elements shall be different bodies that are associated in a meaningful way with the TE and its listed services in the context of the LoTE scheme. Specific profiles making use of this extension shall define the requirements applying to the bodies listed through this extension. |
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 AssociatedBody component shall contain the below components: • The AssociatedBodyName element (see clause 6.5.5.1.2). This component may optionally contain the below components: • The AssociatedBodyTradeName element (see clause 6.5.5.1.3). • The AssociatedBodyAddress element (see clause 6.5.5.1.4). • The AssociatedBodyInformationURI element (see clause 6.5.5.1.5). • The AssociatedBodyTypeIdentifier element (see clause 6.5.5.1.6). • The AssociatedBodyInformationExtensions element (see clause 6.5.5.1.7). Semantics: It shall contain information about a body different from the TE identified through the TEName element (see clause 6.5.1) and 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. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 30 |
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 (see clause 6.1.4). Semantics: 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 shall be the name which is used in formal legal registrations and official records and to which any formal communication, whether physical or electronic, should be addressed. |
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 identifies itself in the specific context within which it is associated to the TE. Format: The AssociatedBodyTradeName component shall be a sequence of multilingual character strings (see clause 6.1.4). Semantics: It shall include 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 include any name under which the body operates, in the specific context within which it is associated to the TE. |
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 AssosciatedBodyPostalAddress element (see clause 6.5.5.1.4.1). • The AssosciatedBodyElectronicAddress element (see clause 6.5.5.1.4.2). 6.5.5.1.4.1 Associated body postal address Description: The AssosciatedBodyPostalAddress component specifies the postal of the body identified through the AssocitedBodyName component (clause 6.5.1), with the provision for the inclusion of the address in multiple languages. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 31 Format: As specified in clause 6.3.5.1. Semantics: This shall be a postal address at which the body provides a customer care or help line service, operated through conventional (physical) mail and processed as would be expected by normal business services. 6.5.5.1.4.2 Associated body electronic address Description: The AssosciatedBodyElectronicAddress component specifies an email address, a web-site URI, and an optional telephone number of the body identified through the AssocitedBodyName component (clause 6.5.1), to be used for electronic communications. Format: As specified in clause 6.3.5.2. Semantics: The e-mail address, and the telephone number when present, shall be an address, and respectively a phone number when present, at which the body provides a customer care or help line service which is related to the listed services and which are processed as would be expected by normal business services. As regards a web-site URI, this shall lead to a capability whereby the user may communicate with a customer care or help line service which is related to context within which the body is associated to the TE and which is processed as would be expected by normal business services. |
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 provide requirements regarding the information available at the listed URI(s). |
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 this component, the set of URI values and their semantics that can be used for the AssociatedBodyTypeIdentifier component. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 32 |
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 information extension may be selected by the scheme operator according to the meaning and information it wishes to convey within its LoTE. The meaning of each extension is hence defined by its source specification, that specification being either the scheme operator's own definition or any other extension definition produced by another entity, such as a community or federation of schemes, a standards body, etc. |
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-components: • The ServiceTypeIdentifier component (see clause 6.6.1). • The ServiceStatus component (see clause 6.6.4). • The StatusStartingTime component (see clause 6.6.5). • The SchemeServiceDefinitionURI component (see clause 6.6.6). • The ServiceSupplyPoint component (see clause 6.6.7). • The ServiceDefinitionURI component (see clause 6.6.8). • The ServiceInformationExtensions component (see clause 6.6.9). Semantics: When the HistoricalInformationPeriod component is present with a non-zero value, the ServiceStatus component shall be present. NOTE 1: When the HistoricalInformationPeriod component is absent, or present with a zero value, and the ServiceStatus component is absent, this signifies that all listed trusted entity services have the same approval status in the list of trusted entities scheme. NOTE 2: When the ServiceTypeIdentifier component is absent, this signifies that all listed trusted entity services are of the same type in the list of trusted entities scheme. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 33 NOTE 3: When the StatusStartingTime component is absent, this signifies verification of the approval status of a listed entity service can only be done at current time. LoTE without the StatusStartingTime component are not suitable for verification of approval statuses of entity services in the past. When the listed service relies on PKI technology, the ServiceDigitalIdentity component shall contain at least one X509Certificate element. |
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 define and register the URIs that may be used in accordance with that profile. NOTE: Any organization can request an object identifier under the etsi-identified organization node or a URI root as detailed on https://portal.etsi.org/PNNS.aspx. |
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). Semantics: The name under which the TE provides the service. |
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 identifier uniquely and unambiguously identifying the service with the type it is associated to. In general however, multiple identifiers can be listed, the collection of which identifies the service in a meaningful way in the LoTE scheme. Format: The ServiceDigitalIdentity component may contain: • One or more X509Certificate elements (see clause 6.6.3.1). ETSI ETSI TS 119 602 V1.1.1 (2025-11) 34 • One or more X509SubjectName elements (see clause 6.6.3.2). • One or more PublicKeyValue elements (see clause 6.6.3.3). • One or more X509SKI elements (see clause 6.6.3.4). • One or more OtherId elements. Semantics: When using PKI public-key technology, this component shall contain at least: one X509Certificate element or an X509SKI element. X.509 Certificates present within the X509Certificate element should contain the organizationName attribute in their subjectName field. The value of that organizationName attribute should strictly match the 'TE Name' value (clause 6.4.1). |
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 specified in clause 2 of IETF RFC 4514 [10]. Specific LoTE profiles shall specify how the Distinguished Name shall be encoded. |
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 parent ServiceDigitalIdentity component, if any. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 35 |
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 listed in the parent ServiceDigitalIdentity component, if any. |
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 set of service current status URI values through the 'Scheme information URI' (see clause 6.3.7) together with their corresponding semantics. |
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. LoTESO shall ensure the consistency of the (re)-issuance of a list of trusted entities and the actual date when a service status has been updated (e.g. granted or withdrawn), i.e. the 'List issue date and time' (clause 6.3.14), the time of signing the trusted list and the time of change. The date and time associated to the new current status of a listed service shall not be set before the date of (re)issuance of the list of trusted entities as retroactive status change can have undesired effects to previous validations of listed services and of their outputs. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 36 |
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(s) shall provide a path to information describing the service as specified by the scheme. LoTE profiles may define a set of Scheme service definition URI together with their semantics. |
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 component shall be a non-empty sequence of URIs, each such URI being optionally further specified with a non-empty URI. Semantics: The referenced URI(s) shall specify where and how the service can be accessed. NOTE: Both human processable and machine processable supply points can be provided. |
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 information describing the service as specified by the TE. |
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 ServiceInformationExtension components and their semantics. |
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 ServiceStatus element (see clause 6.6.4). • The StatusStartingTime element (see clause 6.6.5). This component may optionally contain the below sub-components: • The ServiceTypeIdentifier element (see clause 6.6.1). • The ServiceInformationExtensions element (see clause 6.6.9). Semantics: The ServiceDigitalIdentity element in a ServiceHistoryInstance component shall contain a copy of all digital identifier(s) that were applicable from the date and time indicated in the StatusStartingTime element of the history instance to the StatusStartingTime of the current status, or, when using PKI technology, at least the X509SKI element(s) representing the public key(s) that were applicable as digital identifier(s) at that time. NOTE 1: In case multiple X.509 certificates representing the same public key were used as the digital identifier, only one X509SKI element in the history instance can be used to represent that public key. NOTE 2: It is up to each specific scheme to define the rules regarding the semantics of the ServiceDigitalIdentity element of the ServiceHistoryInstance component, in relation to the scheme-specific semantics of the ServiceDigitalIdentity element of the ServiceInformation component which contains that history entry. Such rules can be the presence of all X.509 certificates applicable at a time, or the presence of a unique X509SKI element when the semantics of the ServiceDigitalIdentity element forbid the representations of multiple public keys in a given ServiceDigitalIdentity element. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 38 |
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 encapsulates the LoTE. The "Country code" and "Organization" fields in Subject Distinguished Name of the certificate supporting the AdES digital signature shall match respectively the "Scheme Territory" and one of the "Scheme operator name" values. If the AdES digital signature is present within the LoTE itself, it shall be provided through the Signature component specified in clause 6.8.1. |
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_lists_of_trusted_entities In the event that any part of the module and/or schemas within this electronic attachment are in conflict with the text of the present document, the present document shall prevail as the authoritative source. A.2 XML bindings A.2.1 Explicit scheme An XML binding for a scheme-explicit LoTE is provided in the following repository: • https://forge.etsi.org/rep/esi/x19_60201_lists_of_trusted_entities In the event that any part of the module and/or schemas within this electronic attachment are in conflict with the text of the present document, the present document shall prevail as the authoritative source. A.2.2 ETSI TS 119 612 schema ETSI TS 119 612 [1], Annex C, provides an alternative XML binding for a scheme explicit LoTE. The table below provides a mapping from the components specified in the present document to the fields defined in ETSI TS 119 612 [1]. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 40 Table A.1: Mapping of ETSI TS 119 612 [1] fields to the ETSI TS 119 602 (the present document) components ETSI TS 119 602 LoTE component and clause ETSI TS 119 612 [1] field and clause LoTE version identifier (clause 6.3.1) TSL version identifier (clause 5.3.1) LoTE sequence number (clause 6.3.2) TSL sequence number (clause 5.3.2) LoTE type (clause 6.3.3) TSL type (clause 5.3.3) Scheme operator name (clause 6.3.4) Scheme operator name (clause 5.3.4) Scheme operator address (clause 6.3.5) Scheme operator address (clause 5.3.5) Scheme name (clause 6.3.6) Scheme name (clause 5.3.6) Scheme information URI (clause 6.3.7) Scheme information URI (clause 5.3.7) Status determination approach (clause 6.3.8) Status determination approach (clause 5.3.8) Scheme type/community/rules (clause 6.3.9) Scheme type/community/rules (clause 5.3.9) Scheme territory (clause 6.3.10) Scheme territory (clause 5.3.10) LoTE policy/legal notice (clause 6.3.11) TSL policy/legal notice (clause 5.3.11) Historical information period (clause 6.3.12) Historical information period (clause 5.3.12) Pointers to other LoTEs (clause 6.3.13) Pointers to other TSLs (clause 5.3.13) List issue date and time (clause 6.3.14) List issue date and time (clause 5.3.14) Next update (clause 6.3.15) Next update (clause 5.3.15) Distribution points (clause 6.3.16) Distribution points (clause 5.3.16) Scheme extensions (clause 6.3.17) Scheme extensions (clause 5.3.17) Trusted Entities List (clause 6.4) Trust Service Provider List (clause 5.3.18) TE name (clause 6.5.1) TSP name (clause 5.4.1) TE trade name (clause 6.5.2) TSP trade name (clause 5.4.2) TE address (clause 6.5.3) TSP address (clause 5.4.3) TE information URI (clause 6.5.4) TSP information URI (clause 5.4.4) TE information extensions (clause 6.5.5) TSP information extensions (clause 5.4.5) Trusted Entity Services (list of services) (clause 6.4.2) TSP Services (list of services) (clause 5.4.6) Service type identifier (clause 6.6.1) Service type identifier (clause 5.5.1) Service name (clause 6.6.2) Service name (clause 5.5.2) Service digital identity (clause 6.6.3) Service digital identity (clause 5.5.3) Service current status (clause 6.6.4) Service current status (clause 5.5.4) Current status starting date and time (clause 6.6.5) Current status starting date and time (clause 5.5.5) Scheme service definition URI (clause 6.6.6) Scheme service definition URI (clause 5.5.6) Service supply points (clause 6.6.7) Service supply points (clause 5.5.7) TE service definition URI (clause 6.6.8) TSP service definition URI (clause 5.5.8) Service information extensions (clause 6.6.9) Service information extensions (clause 5.5.9) History information (clause 6.4.4) History information (clause 5.6) ETSI ETSI TS 119 602 V1.1.1 (2025-11) 41 Annex B (normative): Implementation requirements for multilingual support B.1 General rules When establishing their list of trusted entities, LoTESOs shall use: • Language codes in lower case and country codes in upper case. • Language and country codes according to Table B.1 with regards to EU MS. When a Latin script is present (with its proper language code) a transliteration in Latin script with the related language codes specified in Table B.1 is added. Table B.1 NOTE: (*) Latin transliteration: България = Bulgaria; Ελλάδα = Elláda; Κύπρος = Kýpros. Short name Short name Notes (source language) (English) Belgique/België Belgium BE fr, de, nl България (*) Bulgaria BG bg bg-Latn Česká republika Czech Republic CZ cs Danmark Denmark DK da Deutschland Germany DE de Eesti Estonia EE et Éire/Ireland Ireland IE ga, en Ελλάδα (*) Greece EL el Country code recommended by EU el-Latn España Spain ES es also Catalan (ca), Basque (eu), Galician (gl) France France FR fr Hrvatska Croatia HR hr Italia Italy IT it Κύπρος/Kıbrıs (*) Cyprus CY el, tr el-Latn Latvija Latvia LV lv Lietuva Lithuania LT lt Luxembourg Luxembourg LU fr, de, lb Magyarország Hungary HU hu Malta Malta MT mt, en Nederland Netherlands NL nl Österreich Austria AT de Polska Poland PL pl Portugal Portugal PT pt România Romania RO ro Slovenija Slovenia SI sl Slovensko Slovakia SK sk Suomi/Finland Finland FI fi, sv Sverige Sweden SE sv United Kingdom United Kingdom UK en Country code recommended by EU Ísland Iceland IS is Liechtenstein Liechtenstein LI de Norge/Noreg Norway NO no, nb, nn Country Code Language Code Transliteration in Latin script ETSI ETSI TS 119 602 V1.1.1 (2025-11) 42 B.2 Multilingual character string The string contained within a multilingual character string shall fulfil the requirements of Annex N of ISO/IEC 10646 [5] subject to the following restrictions: 1) the content shall be a string of characters from the Universal Character Set (UCS) as defined by ISO/IEC 10646 [5]; 2) the content shall be UTF-8 encoded; 3) the content shall not include any signature to identify the UCS (see Annex H of ISO/IEC 10646 [5]); 4) control functions (ISO/IEC 6429 [6]), escape sequences (ISO/IEC 2022 [7]) and control sequences or strings shall not be used; therefore control characters such as TAB, CR, LF shall not be present; 5) private-use characters (see clause 10 of ISO/IEC 10646 [5]) from the private use zone (code points E000 to F8FF) in the Basic Multilingual Plane (BMP) and from the private-use Planes 0F and 10 in Group 00, shall not be used; 6) Tag Characters (see Annex T of ISO/IEC 10646 [5]) shall not to be used: therefore the characters from the TAGS (3001) collection shall not be used (see Annex A of ISO/IEC 10646 [5] for the list of defined collections); 7) the content shall be plain text without any mark-up elements or tags from languages as SGML, HTML, XML, XHTML, RTF, TeX and others; 8) the content should follow the semantic rules defined by the Unicode Standard [i.5] (available at http://www.unicode.org/standard/standard.html) for the corresponding characters; 9) combining characters should not be used if the content can be expressed without them; if there is the need to use combining characters but it is possible not to use the ones listed in clause B.1 of ISO/IEC 10646 [5], then that latter set shall not be used. NOTE: This helps to keep as low as possible the required implementation level (as defined by clause 14 of ISO/IEC 10646 [5]) for parsing applications. B.3 Multilingual pointer If the content pointed by the multilingual pointer is plain text, it shall meet the following requirements that express the conformity to Annex N of ISO/IEC 10646 [5] and add further restrictions: 1) the pointed content shall be a string of characters from the Universal Character Set (UCS) as defined by ISO/IEC 10646 [5]; 2) the pointed-to content shall be UTF-8 encoded; 3) the pointed-to content may include the signature for UTF-8 (see Annex H of ISO/IEC 10646 [5]) to identify the UCS; 4) control functions (ISO/IEC 6429 [6]), escape sequences (ISO/IEC 2022 [7]) and control sequences or strings may be used; 5) private-use characters (see clause 10 of ISO/IEC 10646 [5]) from the private use zone (code points E000 to F8FF) in the Basic Multilingual Plane (BMP) and from the private-use Planes 0F and 10 in Group 00, shall not be used; 6) tag Characters (see Annex T of ISO/IEC 10646 [5]) shall not to be used: therefore the characters from the TAGS (3001) collection shall not be used (see Annex A of ISO/IEC 10646 [5] for the list of defined collections); 7) if the pointed-to content is expressed by means of mark-up languages as SGML, HTML, XML, XHTML then: a) the requirements described in W3C Technical Report #20 [i.4] should be met; ETSI ETSI TS 119 602 V1.1.1 (2025-11) 43 b) a language indication may be present according to the mechanisms listed in W3C Technical Report #20 [i.4]. 8) the pointed-to content should follow the semantic rules defined by the Unicode Standard [i.5] (available at http://www.unicode.org/standard/standard.html) for the corresponding characters; 9) combining characters should not be used if the pointed-to content can be expressed without them; if there is the need to use combining characters but it is possible not to use the ones listed in clause B.1 of ISO/IEC 10646 [5], then that latter set shall not be used. NOTE: This helps to keep as low as possible the required implementation level (as defined by clause 14 of ISO/IEC 10646 [5] for parsing applications). B.4 Overall requirements The requirements of W3C Technical Report #20 [i.4] should be met. For interoperability purposes, all applications parsing LoTEs shall be able to store and manage all characters defined by ISO/IEC 10646 [5]. This way the digital signature applied to the LoTE can be always verified, whatever UCS characters are used within the LoTE. However the parsing application may not be able to correctly present all characters. NOTE: Developers of LoTE parsing applications are advised that if their application does not support some of these characters, the application should give notice to the user about possible incorrect representation of the content of multilingual fields; the precise behaviour of the application while presenting unsupported characters is left to developers [i.4]. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 44 Annex C (normative): Registered Uniform Resource Identifiers C.1 Scheme registered URIs Any organization operating a scheme might choose to create its own URIs for its own specific purposes or request ETSI to assign a registered URI root under the ETSI Identified Organization Domain (see https://portal.etsi.org/pnns/uri-list), and then define its own URIs under this root. It might be appropriate to register certain of those URIs where they complement URIs required by or which might be used in the context of the publication of a LoTE. The following examples suggest how additional URIs could be created, including showing a second level of rules, after using the applicable Optional URI as shown in Table C.1. Table C.1 Potential URI Related LoTE field (if any) Meaning http://uri.etsi.org/"registered_org"/"schemename" Scheme type/community/rules (at the secondary level) This could mean an assessment scheme called "schemename" being operated by "registered_org", where "registered_org" is replaced by the name of the scheme operator and "schemename" is replaced by the actual scheme name. http://"scheme_op_URI_root"/.../schemerules/"schemename" This URI would be registered under a different root, e.g. the scheme operator's, distinguished by "scheme_op_URI_root", or it could be another organization which maintains a registry of URIs. This URI could mean an assessment scheme called "schemename" being operated by "scheme_op" where "scheme_op" is replaced by the name of the scheme operator and "schemename" is replaced by the actual scheme name. C.2 EU specific LoTE profiles URIs C.2.1 LoTE Type The following URIs are registered under the radix "http://uri.etsi.org/19602/". http://uri.etsi.org/19602/LoTEType/EUPIDProvidersList A LoTE implementation of a list of providers of person identity data, which are notified by Member States in accordance with the applicable European legislation. http://uri.etsi.org/19602/LoTEType/EUWalletProvidersList A LoTE implementation of a list of wallet providers, which are notified by Member States in accordance with the applicable European legislation. http://uri.etsi.org/19602/LoTEType/EUWRPACProvidersList A LoTE implementation of a list of providers of wallet relying party access certificates, which are notified by Member States in accordance with the applicable European legislation. http://uri.etsi.org/19602/LoTEType/EUWRPRCProvidersList A LoTE implementation of a list of providers of wallet relying party registration certificates, which are notified by Member States in accordance with the applicable European legislation. http://uri.etsi.org/19602/LoTEType/EUPubEAAProvidersList A LoTE implementation of a list of public sector bodies issuing electronic attestation of attribute, which are notified by Member States in accordance with the applicable European legislation. http://uri.etsi.org/19602/LoTEType/EURegistrarsAndRegistersList A LoTE implementation of a list of registrars and registers, which are notified by Member States in accordance with the applicable European legislation. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 45 C.2.2 Status determination approach http://uri.etsi.org/19602/PIDProvidersList/StatusDetn/EU Services listed have their status determined by the Member State notifying the provider of person identity data and related services under the applicable European legislation, as further described in the 'Scheme information URI' pointed-to information. http://uri.etsi.org/19602/WalletProvidersList/StatusDetn/EU Services listed have their status determined by the Member State notifying the wallet provider and related services under the applicable European legislation, as further described in the 'Scheme information URI' pointed-to information. http://uri.etsi.org/19602/WRPACProvidersList/StatusDetn/EU Services listed have their status determined by the Member State notifying the provider of wallet relying party access certificates and related services under the applicable European legislation, as further described in the 'Scheme information URI' pointed-to information. http://uri.etsi.org/19602/WRPRCrovidersList/StatusDetn/EU Services listed have their status determined by the Member State notifying the provider of wallet relying party registration certificates and related services under the applicable European legislation, as further described in the 'Scheme information URI' pointed-to information. http://uri.etsi.org/19602/PubEAAProvidersList/StatusDetn/EU Services listed have their status determined by the Member State notifying the public sector bodies issuing electronic attestation of attribute and related services under the applicable European legislation, as further described in the 'Scheme information URI' pointed-to information. http://uri.etsi.org/19602/RegistrarsAndRegistersList/StatusDetn/EU Services listed have their status determined by the Member State notifying the registrars and related register under the applicable European legislation, as further described in the 'Scheme information URI' pointed-to information. C.2.3 Scheme type/community/rules http://uri.etsi.org/19602/PIDProviders/schemerules/EU A URI pointing towards a descriptive text where users can obtain information about: • the specific policy/rules against which providers of person identity data and related services included in the list are approved and assessed, and from which the type of scheme or community may be determined; • the description about how to use and interpret the content of the list of providers of person identity data. http://uri.etsi.org/19602/WalletProvidersList/schemerules/EU A URI pointing towards a descriptive text where users can obtain information about: • the specific policy/rules against which wallet providers and related services included in the list are approved and assessed, and from which the type of scheme or community may be determined; • the description about how to use and interpret the content of the list of wallet providers. http://uri.etsi.org/19602/WRPACProvidersList/schemerules/EU A URI pointing towards a descriptive text where users can obtain information about: • the specific policy/rules against which providers of wallet relying party access certificates and related services included in the list are approved and assessed, and from which the type of scheme or community may be determined; • the description about how to use and interpret the content of the list of providers of wallet relying party access certificates. http://uri.etsi.org/19602/WRPRCProvidersList/schemerules/EU A URI pointing towards a descriptive text where users can obtain information about: • the specific policy/rules against which providers of wallet relying party registration certificates and related services included in the list are approved and assessed, and from which the type of scheme or community may be determined; • the description about how to use and interpret the content of the list of providers of wallet relying party registration certificates. http://uri.etsi.org/19602/PubEAAProvidersList/schemerules/EU A URI pointing towards a descriptive text where users can obtain information about: • the specific policy/rules against which public sector bodies issuing electronic attestation of attribute and related services included in the list are approved and assessed, and from which the type of scheme or community may be determined; • the description about how to use and interpret the content of the list of public sector bodies issuing electronic attestation of attribute. http://uri.etsi.org/19602/RegistrarsAndRegistersList/schemerules/EU A URI pointing towards a descriptive text where users can obtain information about: • the specific policy/rules against which registrars and registers included in the list are approved and assessed, and from which the type of scheme or community may be determined; • the description about how to use and interpret the content of the list of registrars and registers. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 46 Annex D (normative): Profile for a list of providers of person identity data D.0 Introduction The present Annex specifies a LoTE profile aimed at supporting the publication by the European Commission of a list of providers of person identity data according to CIR 2024/2980 [i.2], Article 5(2). In the present annex, this list is referred to as "the PID providers list". D.1 General requirements The PID providers list shall be issued as a list of trusted entities compliant to the present document. The PID providers list shall comply with the scheme explicit JSON schema definition specified in Annex A of the present document. The PID providers list elements shall comply with the additional requirements specified in present annex. D.2 Scheme information The ListAndSchemeInformation component of the PID providers list shall comply with the requirements laid down in Table D.1. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 47 Table D.1: PID providers list scheme information LoTE component Additional requirement LoTE version identifier (clause 6.3.1) The value of the LoTEVersionIdentifier component shall be "1". LoTE sequence number (clause 6.3.2) The first instance of the PID providers list shall be issued with the value of the LoTESequenceNumber component number set to "1". LoTE type (clause 6.3.3) The value of the LoTEType component shall be "http://uri.etsi.org/19602/LoTEType/EUPIDProvidersList". Scheme operator name (clause 6.3.4) No additional requirements. Scheme operator address (clause 6.3.5) No additional requirements. Scheme name (clause 6.3.6) No additional requirements. Scheme information URI (clause 6.3.7) The SchemeInformationURI component shall contain: a) A URI where users can receive information about the PID providers list; and b) A URI where users can retrieve all previous instances of the PID providers list. Status determination approach (clause 6.3.8) The value of the StatusDeterminationApproach shall be "http://uri.etsi.org/19602/PIDProvidersList/StatusDetn/EU". Scheme type/community/rules (clause 6.3.9) The value of the SchemeTypeCommunityRules component shall be "http://uri.etsi.org/19602/PIDProviders/schemerules/EU". Scheme territory (clause 6.3.10) The value of the SchemeTerritory component shall be "EU". LoTE policy/legal notice (clause 6.3.11) No additional requirements. Historical information period (clause 6.3.12) The HistoricalInformationPeriod component shall not be present, meaning in compliance to clause 6.3.12 of the present document that historical information is not kept in the list. Pointers to other LoTEs (clause 6.3.13) The PointersToOtherLoTE component shall contain a pointer to the present PID providers list itself. List issue date and time (clause 6.3.14) No additional requirements. Next update (clause 6.3.15) The maximum value between the list issue date and time and the next update shall be 6 months. Distribution points (clause 6.3.16) No additional requirements. Scheme extensions (clause 6.3.17) No additional requirements. D.3 List of trusted entities Each TrustedEntityInformation component present in a TrustedEntity component listed in the TrustedEntitiesList component of the PID providers list shall comply with the requirements laid down in Table D.2. Table D.2: PID provider information (for each listed PID providers) LoTE component Additional requirement TE name (clause 6.5.1) The value of the TEName component shall be the name of the provider of person identification data. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 48 LoTE component Additional requirement TE trade name (clause 6.5.2) The TETradeName component shall include an official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the PID providers. In case the PID providers is a legal entity, the value of this component shall have the same semantics as the one that is required for the organizationIdentifier attribute in requirement LEG-5.1.4-02, LEG-5.1.4-03 and LEG-5.1.4-04 of ETSI EN 319 412-1 [15]. In case the PID providers is a natural person, the value of this component shall have the same semantics as the one that is required for the serialNumber attribute in requirement NAT-5.1.3-02, NAT- 5.1.3-03 and NAT-5.1.3-04 of ETSI EN 319 412-1 [15]. TE address (clause 6.5.3) The TEAddress component shall contain: a) The postal address of the PID providers; and b) The contact email and contact phone number of the provider of person identification data, for matters related to the person identification data it provides. TE information URI (clause 6.5.4) The TEInformationURI component shall contain: a) The URL of the webpage that contains the policies, terms and conditions of the provider of person identification data that apply to the provision and use of the person identification data it provides. b) Where applicable, the URL of the webpage that contains additional information about the person identification data provider. c) The URI "http://uri.etsi.org/19602/ListOfTrustedEntities /PIDProvider/CC" where "CC" is replaced by the ISO 3166-1 [2] Alpha 2 code of the Member State which is responsible for that PID provider. TE information extensions (clause 6.5.5) Where applicable, the OtherAssociatedBody extension shall be used to provide in an AssociatedBody element the name of the body responsible for ensuring that the person identification data is associated with the wallet unit. Trusted Entity Services (list of services) (clause 6.4.2) See Table D.3. Each ServiceInformation component present in the TrustedEntityServices component of a TrustedEntity component listed in the TrustedEntitiesList component of the PID providers list shall comply with the requirements laid down in Table D.3. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 49 Table D.3: Service information (for each service of a listed PID provider) LoTE component Additional requirement Service type identifier (clause 6.6.1) The following URI may be used as values of the ServiceTypeIdentifier component, to the exclusion of any other: a) "http://uri.etsi.org/19602/SvcType/PID/Issuance" to indicate that the service is service under which person identity data are issued; b) "http://uri.etsi.org/19602/SvcType/PID/Revocation" to indicate that the service is a service providing validity status information on person identity data. Service name (clause 6.6.2) No additional requirements. Service digital identity (clause 6.6.3) The ServiceDigitalIdentity component shall contain one or more X.509 certificates that can be used to verify the signature or seal created by the provider of person identification data on the person identification data it provides, and for which the certified identity data include the name, and where applicable, the registration number of the person identification data provider, as specified in the TEName and TETradeName components respectively. Service current status (clause 6.6.4) The ServiceStatus component shall not be used. As noted in clause 6.6.0 of the present document, when the HistoricalInformationPeriod component is absent, or present with a zero value, and the ServiceStatus component is absent, this signifies that all listed trusted entity services have the same approval status in the list of trusted entities scheme. Under the present profile, the absence of the service status means that all listed providers of person identity data are bodies notified by EU Member States as currently responsible for issuing and revoking the person identification data and ensuring that the person identification data of a user is cryptographically bound to a wallet unit. When a listed body is not responsible for this issuance and revocation process, it shall be removed from the list. Current status starting date and time (clause 6.6.5) The StatusStartingTime component shall not be used. As noted in clause 6.6.0 of the present document, when the StatusStartingTime component is absent, this signifies verification of the approval status of a listed entity service can only be done at current time. LoTE without the StatusStartingTime component are not suitable for verification of approval statuses of entity services in the past. Under the present profile, an HTTP URI leading to historical previous version of the PID providers list is provided through the SchemeInformationURI component. Scheme service definition URI (clause 6.6.6) No additional requirements. Service supply points (clause 6.6.7) No additional requirements. TE service definition URI (clause 6.6.8) No additional requirements. Service information extensions (clause 6.6.9) No additional requirements. History information (clause 6.4.4) No additional requirements. D.4 Signature The PID providers list shall be signed by means of a compact JAdES Baseline B signature as specified in ETSI TS 119 182-1 [3]. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 50 Annex E (normative): Profile for a list of wallet providers E.0 Introduction The present annex specifies a LoTE profile aimed at supporting the publication by the European Commission of a list of wallet providers according to CIR 2024/2980 [i.2] Article 5(2). In the present annex, this list is referred to as "the wallet providers list". E.1 General requirements The wallet providers list shall be issued as a list of trusted entities compliant to the present document. The wallet providers list shall comply with the scheme explicit JSON schema definition specified in Annex A of the present document. The wallet providers list elements shall comply with the additional requirements specified in present annex. E.2 Scheme information The ListAndSchemeInformation component of the wallet providers list shall comply with the requirements laid down in Table E.1. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 51 Table E.1: Wallet providers list scheme information LoTE component Additional requirement LoTE version identifier (clause 6.3.1) The value of the LoTEVersionIdentifier component shall be "1". LoTE sequence number (clause 6.3.2) The first instance of the wallet providers list shall be issued with the value of the LoTESequenceNumber component number set to "1". LoTE type (clause 6.3.3) The value of the LoTEType component shall be "http://uri.etsi.org/19602/LoTEType/EUWalletProvidersList". Scheme operator name (clause 6.3.4) No additional requirements. Scheme operator address (clause 6.3.5) No additional requirements. Scheme name (clause 6.3.6) No additional requirements. Scheme information URI (clause 6.3.7) The SchemeInformationURI component shall contain: a) a URI where users can receive information about the wallet provider list; and b) a URI where users can retrieve all previous instances of the wallet provider list. Status determination approach (clause 6.3.8) The value of the StatusDeterminationApproach component shall be http://uri.etsi.org/19602/WalletProvidersList/StatusDetn/EU. Scheme type/community/rules (clause 6.3.9) The value of the SchemeTypeCommunityRules component shall be "http://uri.etsi.org/19602/WalletProvidersList/schemerules/EU". Scheme territory (clause 6.3.10) The value of the SchemeTerritory component shall be "EU". LoTE policy/legal notice (clause 6.3.11) No additional requirements. Historical information period (clause 6.3.12) The HistoricalInformationPeriod component shall not be present, meaning in compliance to clause 6.3.12 of the present document that historical information is not kept in the list. Pointers to other LoTEs (clause 6.3.13) The PointersToOtherLoTE component shall contain a pointer to the present wallet providers list itself. List issue date and time (clause 6.3.14) No additional requirements. Next update (clause 6.3.15) The maximum value between the list issue date and time and the next update shall be 6 months. Distribution points (clause 6.3.16) No additional requirements. Scheme extensions (clause 6.3.17) No additional requirements. E.3 List of trusted entities Each TrustedEntityInformation component present in a TrustedEntity component listed in the TrustedEntitiesList component of the wallet providers list shall comply with the requirements laid down in Table E.2. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 52 Table E.2: Wallet provider information (for each listed wallet providers) LoTE component Additional requirement TE name (clause 6.5.1) The value of the TEName component shall be the name of the wallet provider. TE trade name (clause 6.5.2) The TETradeName component shall include an official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the wallet provider. In case the wallet provider is a legal entity, the value of this component shall have the same semantics as the one that is required for the organizationIdentifier attribute in requirement LEG-5.1.4-02, LEG-5.1.4-03 and LEG-5.1.4-04 of ETSI EN 319 412-1 [15]. In case the wallet provider is a natural person, the value of this component shall have the same semantics as the one that is required for the serialNumber attribute in requirement NAT-5.1.3-02, NAT-5.1.3-03 and NAT-5.1.3-04 of ETSI EN 319 412-1 [15]. TE address (clause 6.5.3) The TEAddress component shall contain: a) the postal address of the wallet provider; and b) the contact email and contact phone number of the wallet provider, for matters related to the wallet solutions it provides. TE information URI (clause 6.5.4) The TEInformationURI component shall contain: a) The URL of the webpage where the policies, terms and conditions of the wallet provider that apply to the provision and use of the wallet solution it provides are located. b) Where applicable, the URL of the webpage that contains additional information about the wallet provider and the wallet solution. c) The URI "http://uri.etsi.org/19602/ListOfTrustedEntities/ WalletProvider/CC" where "CC" is replaced by the ISO 3166-1 [2] Alpha 2 code of the Member State which is responsible for that Wallet provider. TE information extensions (clause 6.5.5) Where applicable, the OtherAssociatedBody extension shall be used to provide in an AssociatedBody element the name of the body responsible for the provision of the wallet solution. Trusted Entity Services (list of services) (clause 6.4.2) See Table E.3. Each ServiceInformation component present in the TrustedEntityServices component of a TrustedEntity component listed in the TrustedEntitiesList component of the wallet providers list shall comply with the requirements laid down in Table E.3. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 53 Table E.3: Service information (for each service of a listed wallet provider LoTE component Additional requirement Service type identifier (clause 6.6.1) The following URI may be used as values of the ServiceTypeIdentifier component, to the exclusion of any other: a) "http://uri.etsi.org/19602/SvcType/WalletSolution/Issuance" to indicate that the service is service under which a wallet solution is issued; b) "http://uri.etsi.org/19602/SvcType/WalletSolution/Revocation" to indicate that the service is a service providing validity status information on a wallet solution. Service name (clause 6.6.2) The value of the ServiceName component shall be the name of a wallet solution provided by the wallet provider identified through the TEName component, as the Commission shall publish this information in the Official Journal of the European Union pursuant to Article 5d of Regulation (EU) No 910/2014 [i.1]. Service digital identity (clause 6.6.3) The ServiceDigitalIdentity component shall contain one or more X.509 certificates that can be used to authenticate and validate the components of the wallet unit the wallet provider provides under the wallet solution identified through the ServiceName component, and for which the certified identity data includes the name, and where applicable, the registration number of the wallet provider, as specified in the TEName and TETradeName components respectively. Service current status (clause 6.6.4) The ServiceStatus component shall not be used. As noted in clause 6.6.0 of the present document, when the HistoricalInformationPeriod component is absent, or present with a zero value, and the ServiceStatus component is absent, this signifies that all listed trusted entity services have the same approval status in the list of trusted entities scheme. Under the present profile, the absence of the service status means that all listed wallet solution are certified wallet solutions. When the certification of a wallet solution is withdrawn or expired, the corresponding entry in the wallet provider list shall be removed from the TE service entries under the wallet provider. When no more certified wallet solution are listed under a wallet provider, the wallet provider entry itself shall be removed from the list. Current status starting date and time (clause 6.6.5) The StatusStartingTime component shall not be used. As noted in clause 6.6.0 of the present document, when the StatusStartingTime component is absent, this signifies verification of the approval status of a listed entity service can only be done at current time. LoTE without the StatusStartingTime component are not suitable for verification of approval statuses of entity services in the past. Under the present profile, an HTTP URI leading to historical previous version of the wallet providers list is provided through the SchemeInformationURI component. Scheme service definition URI (clause 6.6.6) No additional requirements. Service supply points (clause 6.6.7) No additional requirements. TE service definition URI (clause 6.6.8) No additional requirements. Service information extensions (clause 6.6.9) The ServiceUniqueIdentifier extension shall be used to provide the reference number of the wallet solution identified through the ServiceName component, as the Commission shall publish this information in the Official Journal of the European Union pursuant to Article 5d of Regulation (EU) No 910/2014 [i.1]. History information (clause 6.4.4) No additional requirements. E.4 Signature The wallet providers list shall be signed by means of a compact JAdES Baseline B signature as specified in ETSI TS 119 182-1 [3]. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 54 Annex F (normative): Profile for a list of providers of wallet relying party access certificates F.0 Introduction The present annex specifies a LoTE profile aimed at supporting the publication by the European Commission of a list of wallet relying parties access certificates according to CIR 2024/2980 [i.2] Article 5(2). In the present annex, this list is referred to as "the WRPAC providers list". F.1 General requirements The WRPAC providers list shall be issued as a list of trusted entities compliant to the present document. The WRPAC providers list shall comply with the scheme explicit JSON schema definition specified in Annex A of the present document. The WRPAC providers list components shall comply with the additional requirements specified in present annex. F.2 Scheme information The ListAndSchemeInformation component of the WRPAC providers list shall comply with the requirements laid down in Table F.1. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 55 Table F.1: WRPAC providers list scheme information LoTE component Additional requirement LoTE version identifier (clause 6.3.1) The value of the LoTEVersionIdentifier component shall be "1". LoTE sequence number (clause 6.3.2) The first instance of the WRPAC providers list shall be issued with the value of the LoTESequenceNumber component number set to "1". LoTE type (clause 6.3.3) The value of the LoTEType component shall be "http://uri.etsi.org/19602/LoTEType/EUWRPACProvidersList". Scheme operator name (clause 6.3.4) No additional requirements. Scheme operator address (clause 6.3.5) No additional requirements. Scheme name (clause 6.3.6) No additional requirements. Scheme information URI (clause 6.3.7) The SchemeInformationURI component shall contain: a) a URI where users can receive information about the WRPAC list; and b) a URI where users can retrieve all previous instances of the WRPAC list. Status determination approach (clause 6.3.8) The value of the StatusDeterminationApproach component shall be "http://uri.etsi.org/19602/WRPACProvidersList/StatusDetn/EU". Scheme type/community/rules (clause 6.3.9) The value of the SchemeTypeCommunityRules component shall be "http://uri.etsi.org/19602/WRPACProvidersList/schemerules/EU". Scheme territory (clause 6.3.10) The value of the SchemeTerritory component shall be "EU". LoTE policy/legal notice (clause 6.3.11) No additional requirements. Historical information period (clause 6.3.12) The HistoricalInformationPeriod component shall not be present, meaning in compliance to clause 6.3.12 of the present document that historical information is not kept in the list. Pointers to other LoTEs (clause 6.3.13) The PointersToOtherLoTE component shall contain a pointer to the present WRPAC providers list itself. List issue date and time (clause 6.3.14) No additional requirements. Next update (clause 6.3.15) The maximum value between the list issue date and time and the next update shall be 6 months. Distribution points (clause 6.3.16) No additional requirements. Scheme extensions (clause 6.3.17) No additional requirements. F.3 List of trusted entities Each TrustedEntityInformation component present in a TrustedEntity component listed in the TrustedEntitiesList component of the WRPAC providers list shall comply with the requirements laid down in Table F.2. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 56 Table F.2: WRPAC provider information (for each listed WRPAC providers) LoTE component Additional requirement TE name (clause 6.5.1) The value of the TEName component shall be the name of the provider of wallet relying party access certificate. TE trade name (clause 6.5.2) The TETradeName component shall include an official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the provider of the wallet relying party access certificate. In case the WRPAC provider is a legal entity, the value of this component shall have the same semantics as the one that is required for the organizationIdentifier attribute in requirement LEG-5.1.4-02, LEG-5.1.4-03 and LEG-5.1.4-04 of ETSI EN 319 412-1 [15]. In case the WRPAC provider is a natural person, the value of this component shall have the same semantics as the one that is required for the serialNumber attribute in requirement NAT-5.1.3-02, NAT-5.1.3-03 and NAT-5.1.3-04 of ETSI EN 319 412-1 [15]. TE address (clause 6.5.3) The TEAddress component shall contain: a) The postal address of the WRPAC provider; and b) The contact email and contact phone number of the provider of wallet relying party access certificates, for matters related to the access certificates it provides to wallet-relying parties. TE information URI (clause 6.5.4) The TEInformationURI component shall contain: a) The URL of the webpage that contains the policies, terms and conditions of the provider of wallet relying party access certificates that apply to the provision and use of the access certificates it provides to wallet-relying parties. b) Where applicable, the URL of the webpage that contains additional information about the provider and the access certificates it provides to wallet-relying parties. c) The URI "http://uri.etsi.org/19602/ListOfTrustedEntities/ WRPACProvider/CC" where "CC" is replaced by the ISO 3166-1 [2] Alpha 2 code of the Member State which is responsible for that WRPAC provider. TE information extensions (clause 6.5.5) No additional requirements. Trusted Entity Services (list of services) (clause 6.4.2) See Table F.3. Each ServiceInformation component present in the TrustedEntityServices component of a TrustedEntity component listed in the TrustedEntitiesList component of the WRPAC providers list shall comply with the requirements laid down in Table F.3. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 57 Table F.3: Service information (for each service of a listed WRPAC provider) LoTE component Additional requirement Service type identifier (clause 6.6.1) The following URI may be used as values of the ServiceTypeIdentifier component, to the exclusion of any other: a) "http://uri.etsi.org/19602/SvcType/WRPAC/Issuance to indicate that the service is service under which wallet relying parties access certificates are issued; b) "http://uri.etsi.org/19602/SvcType/WRPAC/Revocation" to indicate that the service is a service providing validity status information on wallet relying party access certificates. Service name (clause 6.6.2) No additional requirements. Service digital identity (clause 6.6.3) The ServiceDigitalIdentity component shall contain one or more X.509 certificates that can be used to verify the signature or seal created by the provider of wallet-relying party access certificates on the access certificate it provides to wallet-relying parties, with, where applicable, the information required to distinguish wallet-relying party access certificates from other certificates. Service current status (clause 6.6.4) The ServiceStatus component shall not be used. As noted in clause 6.6.0 of the present document, when the HistoricalInformationPeriod component is absent, or present with a zero value, and the ServiceStatus component is absent, this signifies that all listed trusted entity services have the same approval status in the list of trusted entities scheme. Under the present profile, the absence of the service status means that all listed WRPAC providers are currently mandated by an EU Member State to issue relying party access certificates to wallet-relying parties registered in that Member State. When a listed WRPAC provider does not have that mandate anymore, it shall be removed from the list. Current status starting date and time (clause 6.6.5) The StatusStartingTime component shall not be used. As noted in clause 6.6.0 of the present document, when the StatusStartingTime component is absent, this signifies verification of the approval status of a listed entity service can only be done at current time. LoTE without the StatusStartingTime component are not suitable for verification of approval statuses of entity services in the past. Under the present profile, an HTTP URI leading to historical previous version of the WRPAC providers list is provided through the SchemeInformationURI component. Scheme service definition URI (clause 6.6.6) No additional requirements. Service supply points (clause 6.6.7) No additional requirements. TE service definition URI (clause 6.6.8) No additional requirements. Service information extensions (clause 6.6.9) No additional requirements. History information (clause 6.4.4) No additional requirements. F.4 Signature The WRPAC providers list shall be signed by means of a compact JAdES Baseline B signature as specified in ETSI TS 119 182-1 [3]. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 58 Annex G (normative): Profile for a list of providers of wallet relying party registration certificates G.0 Introduction The present annex specifies a LoTE profile aimed at supporting the publication by the European Commission of a list of wallet relying parties registration certificates. In the present annex, this list is referred to as "the WRPRC providers list". G.1 General requirements The WRPRC providers list shall be issued as a list of trusted entities compliant to the present document. The WRPRC providers list shall comply with the scheme explicit JSON schema definition specified in Annex A of the present document. The WRPRC providers list components shall comply with the additional requirements specified in present annex. G.2 Scheme information The ListAndSchemeInformation component of the WRPRC providers list shall comply with the requirements laid down in Table G.1. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 59 Table G.1: WRPRC providers list scheme information LoTE component Additional requirement LoTE version identifier (clause 6.3.1) The value of the LoTEVersionIdentifier component shall be "1". LoTE sequence number (clause 6.3.2) The first instance of the WRPRC providers list shall be issued with the value of the LoTESequenceNumber component number set to "1". LoTE type (clause 6.3.3) The value of the LoTEType component shall be "http://uri.etsi.org/19602/LoTEType/EUWRPRCProvidersList". Scheme operator name (clause 6.3.4) No additional requirements. Scheme operator address (clause 6.3.5) No additional requirements. Scheme name (clause 6.3.6) No additional requirements. Scheme information URI (clause 6.3.7) The SchemeInformationURI component shall contain: a) a URI where users can receive information about the WRPRC list; and b) a URI where users can retrieve all previous instances of the WRPRC list. Status determination approach (clause 6.3.8) The value of the StatusDeterminationApproach component shall be "http://uri.etsi.org/19602/WRPRCrovidersList/StatusDetn/EU". Scheme type/community/rules (clause 6.3.9) The value of the SchemeTypeCommunityRules component shall be "http://uri.etsi.org/19602/WRPRCProvidersList/schemerules/EU". Scheme territory (clause 6.3.10) The value of the SchemeTerritory component shall be "EU". LoTE policy/legal notice (clause 6.3.11) No additional requirements. Historical information period (clause 6.3.12) The HistoricalInformationPeriod component shall not be present, meaning in compliance to clause 6.3.12 of the present document that historical information is not kept in the list. Pointers to other LoTEs (clause 6.3.13) The PointersToOtherLoTE component shall contain a pointer to the present WRPRC providers list itself. List issue date and time (clause 6.3.14) No additional requirements. Next update (clause 6.3.15) The maximum value between the list issue date and time and the next update shall be 6 months. Distribution points (clause 6.3.16) No additional requirements. Scheme extensions (clause 6.3.17) No additional requirements. G.3 List of trusted entities Each TrustedEntityInformation component present in a TrustedEntity component listed in the TrustedEntitiesList component of the WRPRC providers list shall comply with the requirements laid down in Table G.2. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 60 Table G.2: WRPRC provider information (for each listed WRPRC providers) LoTE component Additional requirement TE name (clause 6.5.1) The value of the TEName component shall be the name of the provider of wallet relying party registration certificate. TE trade name (clause 6.5.2) The TETradeName component shall include an official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the provider of the wallet relying party registration certificate. a) In case the WRPRC provider is a legal entity, the value of this component shall have the same semantics as the one that is required for the organizationIdentifier attribute in requirement LEG-5.1.4-02, LEG-5.1.4-03 and LEG-5.1.4-04 of ETSI EN 319 412-1 [15]. b) In case the WRPRC provider is a natural person, the value of this component shall have the same semantics as the one that is required for the serialNumber attribute in requirement NAT-5.1.3-02, NAT-5.1.3-03 and NAT-5.1.3-04 of ETSI EN 319 412-1 [15]. TE address (clause 6.5.3) The TEAddress component shall contain: The postal address of the WRPRC provider; and The contact email and contact phone number of the provider of wallet relying party registration certificates, for matters related to the registration certificates it provides to wallet-relying parties. TE information URI (clause 6.5.4) The TEInformationURI component shall contain: a) The URL of the webpage that contains the policies, terms and conditions of the provider of wallet relying party registration certificates that apply to the provision and use of the registration certificates it provides to wallet-relying parties. b) Where applicable, the URL of the webpage that contains additional information about the provider and the registration certificates it provides to wallet-relying parties. c) The URI "http://uri.etsi.org/19602/ListOfTrustedEntities/ WRPRCProvider/CC" where "CC" is replaced by the ISO 3166-1 [2] Alpha 2 code of the Member State which is responsible for that WRPRC provider. TE information extensions (clause 6.5.5) No additional requirements. Trusted Entity Services (list of services) (clause 6.4.2) See Table G.3. Each ServiceInformation component present in the TrustedEntityServices component of a TrustedEntity component listed in the TrustedEntitiesList component of the WRPRC providers list shall comply with the requirements laid down in Table G.3. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 61 Table G.3: Service information (for each service of a listed WRPRC provider) LoTE component Additional requirement Service type identifier (clause 6.6.1) The following URI may be used as values of the ServiceTypeIdentifier component, to the exclusion of any other: a) "http://uri.etsi.org/19602/SvcType/WRPRC/Issuance" to indicate that the service is service under which wallet relying parties access certificates are issued; b) "http://uri.etsi.org/19602/SvcType/WRPRC/Revocation" to indicate that the service is a service providing validity status information on wallet relying party access certificates. Service name (clause 6.6.2) No additional requirements. Service digital identity (clause 6.6.3) The ServiceDigitalIdentity component shall contain one or more X.509 certificates that can be used to verify the signature or seal created by the provider of wallet-relying party registration certificates on the registration certificate it provides to wallet-relying parties, with, where applicable, the information required to distinguish wallet-relying party registration certificates from other certificates. Service current status (clause 6.6.4) The ServiceStatus component shall not be used. As noted in clause 6.6.0 of the present document, when the HistoricalInformationPeriod component is absent, or present with a zero value, and the ServiceStatus component is absent, this signifies that all listed trusted entity services have the same approval status in the list of trusted entities scheme. Under the present profile, the absence of the service status means that all listed WRPRC providers are currently mandated by an EU Member State to issue relying party registration certificates to wallet-relying parties registered in that Member State. When a listed WRPRC provider does not have that mandate anymore, it shall be removed from the list. Current status starting date and time (clause 6.6.5) The StatusStartingTime component shall not be used. As noted in clause 6.6.0 of the present document, when the StatusStartingTime component is absent, this signifies verification of the approval status of a listed entity service can only be done at current time. LoTE without the StatusStartingTime component are not suitable for verification of approval statuses of entity services in the past. Under the present profile, an HTTP URI leading to historical previous version of the WRPRC providers list is provided through the SchemeInformationURI component. Scheme service definition URI (clause 6.6.6) No additional requirements. Service supply points (clause 6.6.7) No additional requirements. TE service definition URI (clause 6.6.8) No additional requirements. Service information extensions (clause 6.6.9) No additional requirements. History information (clause 6.4.4) No additional requirements. G.4 Signature The WRPRC providers list shall be signed by means of a compact JAdES Baseline B signature as specified in ETSI TS 119 182-1 [3]. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 62 Annex H (normative): Profile for a list of public sector bodies issuing electronic attestation of attributes H.0 Introduction The present annex specifies a LoTE profile aimed at supporting the publication by the European Commission of a list of public sector bodies issuing electronic attestation of attribute referred to in Article 3, point (46) of Regulation (EU) 910/2014 [i.1]. issued by CIR 2025/1569 [i.3], Article 6(1). In the present annex, this list is referred to as "the Pub-EAA providers list". H.1 General requirements The Pub-EAA providers list shall be issued as a list of trusted entities compliant to the present document. The Pub-EAA providers list shall comply with either the scheme explicit XML schema definition specified in Annex A of the present document or the scheme explicit JSON schema definition specified in Annex A of the present document. The Pub-EAA providers list components shall comply with the additional requirements specified in present annex. H.2 Scheme information The ListAndSchemeInformation component of the Pub-EAA providers list shall comply with the requirements laid down in Table H.1. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 63 Table H.1: Pub-EAA providers list scheme information LoTE component Additional requirement LoTE version identifier (clause 6.3.1) The value of the LoTEVersionIdentifier component shall be "1". LoTE sequence number (clause 6.3.2) The first instance of the Pub-EAA providers list shall be issued with the value of the LoTESequenceNumber component number set to "1". LoTE type (clause 6.3.3) The value of the LoTEType component shall be "http://uri.etsi.org/19602/LoTEType/EUPubEAAProvidersList". Scheme operator name (clause 6.3.4) No additional requirements. Scheme operator address (clause 6.3.5) No additional requirements. Scheme name (clause 6.3.6) No additional requirements. Scheme information URI (clause 6.3.7) The SchemeInformationURI component shall contain a URI where users can receive information about the Pub-EAA providers list. Status determination approach (clause 6.3.8) The value of the StatusDeterminationApproach component shall be "http://uri.etsi.org/19602/PubEAAProvidersList/StatusDetn/EU". Scheme type/community/rules (clause 6.3.9) The value of the SchemeTypeCommunityRules component shall be "http://uri.etsi.org/19602/PubEAAProvidersList/schemerules/EU". Scheme territory (clause 6.3.10) The value of the SchemeTerritory component shall be "EU". LoTE policy/legal notice (clause 6.3.11) No additional requirements. Historical information period (clause 6.3.12) The HistoricalInformationPeriod component shall be present with value "65535". Pointers to other LoTEs (clause 6.3.13) The PointersToOtherLoTE component shall not be present. List issue date and time (clause 6.3.14) No additional requirements. Next update (clause 6.3.15) The maximum value between the list issue date and time and the next update shall be 6 months. Distribution points (clause 6.3.16) No additional requirements. Scheme extensions (clause 6.3.17) No additional requirements. H.3 List of trusted entities Each TrustedEntityInformation component present in a TrustedEntity component listed in the TrustedEntitiesList component of the Pub-EAA providers list shall comply with the requirements laid down in Table H.2. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 64 Table H.2: Pub-EAA provider information (for each listed Pub-EAA providers) LoTE component Additional requirement TE name (clause 6.5.1) The value of the TEName component shall be the name of the Pub- EAA provider. The name of the Pub-EAA provider shall be the name which is used in formal legal registrations and official records and to which any formal communication, whether physical or electronic, should be addressed. TE trade name (clause 6.5.2) The TETradeName component shall include: a) An official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the Pub-EAA provider. In case the Pub-EAA provider is a legal entity, the value of this component shall have the same semantics as the one that is required for the organizationIdentifier attribute in requirement LEG-5.1.4-02, LEG-5.1.4-03 and LEG-5.1.4-04 of ETSI EN 319 412-1 [15]. In case the Pub-EAA provider is a natural person, the value of this component shall have the same semantics as the one that is required for the serialNumber attribute in requirement NAT-5.1.3-02, NAT-5.1.3-03 and NAT-5.1.3-04 of ETSI EN 319 412-1 [15]. b) The reference to the Union or national law under which the public sector body is established as the responsible for the authentic source on the basis of which the electronic attestation of attributes is issued or is designated to act on behalf of the public sector body that is responsible for the authentic source, formatted as a URI as follows: a. "OJ:" for the scheme part; followed by b. 2 characters: i. "EU" if the reference is a reference to Union law; or ii. The 2 character ISO 3166-1 [2] country code of the EU Member State in which the public sector body is established, if the reference is a reference to national law; and iii. identifier uniquely representing the Union or national law. TE address (clause 6.5.3) The TEAddress component shall contain: a) the postal address of the Pub-EAA provider; and b) the contact email and contact phone number of the Pub-EAA provider, for matters related to the electronic attestation of attributes it issues. c) the URI "http://uri.etsi.org/19602/ListOfTrustedEntities/ PubEAAProvider/CC" where "CC" is replaced by the ISO 3166-1 [2] Alpha 2 code of the Member State which is responsible for that Pub-EAA provider. TE information URI (clause 6.5.4) The TEInformationURI component shall contain the URL of the webpage that contains the policies, terms and conditions of the Pub-EAA provider, and other generic information that apply to the provision and use of the electronic attestation of attributes it provides. TE information extensions (clause 6.5.5) No additional requirements. Trusted Entity Services (list of services) (clause 6.4.2) See Table H.3. Each ServiceInformation component present in the TrustedEntityServices component of a TrustedEntity component listed in the TrustedEntitiesList component of the Pub-EAA providers list shall comply with the requirements laid down in Table H.3. Table H.3: Service information (for each service of a listed Pub-EAA provider) LoTE component Additional requirement Service type identifier (clause 6.6.1) The following URI may be used as values of the ServiceTypeIdentifier component, to the exclusion of any other: ETSI ETSI TS 119 602 V1.1.1 (2025-11) 65 LoTE component Additional requirement a) "http://uri.etsi.org/19602/SvcType/PubEAA/Issuance" to indicate that the service is a service under which electronic attestation of attribute are issued by a notified body on behalf of an authentic source; b) "http://uri.etsi.org/19602/SvcType/PubEAA/Revocation" to indicate that the service is a service providing validity status information on wallet relying party access certificates. Service name (clause 6.6.2) No additional requirements. Service digital identity (clause 6.6.3) The ServiceDigitalIdentity component may contain one or more X.509 certificates that can be used to verify the signature or seal created by the Pub-EAA provider on the electronic attestation of attributes it provides. NOTE: This can be the X.509 certificate corresponding to the private key used to sign or seal the electronic attestation of attributes, or it can be the X.509 certificate corresponding to a CA issuing such X.509 certificates provided the other requirements applying to the present component are met. When multiple X.509 certificates are present in the ServiceDigitalIdentity component, they shall all relate to the same public key. When multiple X.509 certificates are present in the ServiceDigitalIdentity component, they shall have identical subject names identifying the Pub-EAA provider identified through the TEName component. The listed X.509 certificate(s) shall have the organizationName attribute present in its (their) subject name(s). The organizationName attribute present in the subject name shall strictly match the value of the TEName component. Service current status (clause 6.6.4) The ServiceStatus component shall be present. The following values may be used to the exclusion of any other: http://uri.etsi.org/19602/PubEAAProvidersList/SvcStatus/notified to indicate that the listed entity has been notified to the Commission as a providers of electronic attestations of attributes issued by or on behalf of a public sector body responsible for an authentic source by the EU MS in which it is established, and can electronic attestation of attributes through the listed service; or http://uri.etsi.org/19602/PubEAAProvidersList/SvcStatus/withdrawn to indicate that the listed entity may not issue electronic attestation of attributes through the listed service anymore. When the listed entity is not to be considered as a providers of electronic attestations of attributes issued by or on behalf of a public sector body responsible for an authentic source anymore, all services listed under the corresponding trusted entity entry shall have their current status set to http://uri.etsi.org/19602/PubEAAProvidersList/SvcStatus/withdrawn Current status starting date and time (clause 6.6.5) LoTESO shall ensure the consistency of the (re)-issuance of a LoTE and the actual date when a service status has been updated (e.g. notified or withdrawn), i.e. the value of the ListIssueDateTime component the time of signing the LoTE and the time of change. The date and time associated to the new current status of a listed service shall not be set before the date of (re)issuance of the LoTE as retroactive status change can have undesired effects to previous validations of listed services and of their outputs. Scheme service definition URI (clause 6.6.6) No additional requirements. Service supply points (clause 6.6.7) No additional requirements. TE service definition URI (clause 6.6.8) No additional requirements. Service information extensions (clause 6.6.9) No additional requirements. History information (clause 6.4.4) The ServiceDigitalIdentity component in a ServiceHistoryInstance component shall contain at least the X509SKI component. The ServiceDigitalIdentity component in a ServiceHistoryInstance component shall not contain an X509Certificate component. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 66 H.4 Signature When a JSON binding is used to issue the Pub-EAA providers list, the list shall be signed by means of a compact JAdES Baseline B signature as specified in ETSI TS 119 182-1 [3]. When an XML binding is used to issue the Pub-EAA providers list, the Signature component shall be present with a XAdES Baseline B signature as specified in ETSI EN 319 132-1 [4], meeting the following requirements: 1) It shall be an enveloped digital signature. 2) Its ds:SignedInfo element shall contain a ds:Reference element with the URI attribute set to an empty string (i.e. URI=""), so as to refer to the entire document. This ds:Reference element shall satisfy the following requirements: a) It shall contain only one ds:Transforms element. b) This ds:Transforms element shall contain two ds:Transform elements. The first one will be one whose Algorithm attribute indicates the enveloped transformation with the value: "http://www.w3.org/2000/09/xmldsig#enveloped-signature". The second one will be one whose Algorithm attribute instructs to perform the exclusive canonicalization "http://www.w3.org/2001/10/xml- exc-c14n#". 3) ds:CanonicalizationMethod shall be "http://www.w3.org/2001/10/xml-exc-c14n#". 4) It may have other ds:Reference elements. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 67 Annex I (normative): Profile for a list of registrars and registers I.0 Introduction The present annex specifies a LoTE profile aimed at supporting the publication by the European Commission of a list of on registrars of wallet-relying parties and registers of wallet-relying parties according to CIR 2024/2980 [i.2] Article 5(1). In the present annex, this list is referred to as "the list of registrars and registers". I.1 General requirements The list of registrars and registers shall be issued as a list of trusted entities compliant to the present document. The list of registrars and registers shall comply with the scheme explicit JSON schema definition specified in Annex A of the present document. The list of registrars and registers components shall comply with the additional requirements specified in present annex. I.2 Scheme information The ListAndSchemeInformation component of the list of registrars and registers shall comply with the requirements laid down in Table I.1. Table I.1: List of registrars and registers scheme information LoTE component Additional requirement LoTE version identifier (clause 6.3.1) The value of the LoTEVersionIdentifier component shall be "1". LoTE sequence number (clause 6.3.2) The first instance of the list of registrars and registers shall be issued with the value of the LoTESequenceNumber component number set to "1". LoTE type (clause 6.3.3) The value of the LoTEType component shall be "http://uri.etsi.org/19602/LoTEType/EURegistrarsAndRegistersList". Scheme operator name (clause 6.3.4) No additional requirements. Scheme operator address (clause 6.3.5) No additional requirements. Scheme name (clause 6.3.6) No additional requirements. Scheme information URI (clause 6.3.7) The SchemeInformationURI component shall contain: a) A URI where users can receive information about the list of registrars and registers; and b) A URI where users can retrieve all previous instances of the list of registrars and registers. Status determination approach (clause 6.3.8) The value of the StatusDeterminationApproach component shall be "http://uri.etsi.org/19602/RegistrarsAndRegistersList/StatusDetn/EU" Scheme type/community/rules (clause 6.3.9) The value of the SchemeTypeCommunityRules component shall be "http://uri.etsi.org/19602/RegistrarsAndRegistersList/schemerules/EU". Scheme territory (clause 6.3.10) The value of the SchemeTerritory component shall be "EU". LoTE policy/legal notice (clause 6.3.11) No additional requirements. Historical information period (clause 6.3.12) The HistoricalInformationPeriod component shall not be present, meaning in compliance to clause 6.3.12 of the present document that historical information is not kept in the list. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 68 LoTE component Additional requirement Pointers to other LoTEs (clause 6.3.13) The PointersToOtherLoTE component shall contain a pointer to the present list of registers and registrars itself. List issue date and time (clause 6.3.14) No additional requirements. Next update (clause 6.3.15) The maximum value between the list issue date and time and the next update shall be 6 months. Distribution points (clause 6.3.16) No additional requirements. Scheme extensions (clause 6.3.17) No additional requirements. I.3 List of trusted entities Each TrustedEntityInformation component present in a TrustedEntity component listed in the TrustedEntitiesList component of the list of registrars and registers shall comply with the requirements laid down in Table I.2. Table I.2: Registrar information (for each listed registrars) LoTE component Additional requirement TE name (clause 6.5.1) The value of the TEName component shall be the name of the registrar. TE trade name (clause 6.5.2) The TETradeName component shall include, where applicable, the registration number of the registrar. TE address (clause 6.5.3) The TEAddress component shall contain: a) the postal address of the registrar; and b) the contact email and contact phone number of the registrar, for matters related to the register it is responsible for. TE information URI (clause 6.5.4) The TEInformationURI component shall contain: a) the URL of the webpage where the registration policy that applies to the register and related information are located; b) where applicable, the URL of a webpage for additional information about the registrar and the register. c) the URI "http://uri.etsi.org/19602/ListOfTrustedEntities/Registrar/C C" where "CC" is replaced by the ISO 3166-1 [2] Alpha 2 code of the Member State which is responsible for that registrar. TE information extensions (clause 6.5.5) No additional requirements. Trusted Entity Services (list of services) (clause 6.4.2) See Table I.3. Each ServiceInformation component present in the TrustedEntityServices component of a TrustedEntity component listed in the TrustedEntitiesList component of the list of registrars and registers shall comply with the requirements laid down in Table I.3. Table I.3: Register information (for each service of a listed registrars) LoTE component Additional requirement Service type identifier (clause 6.6.1) The following URI may be used as value of the ServiceTypeIdentifier component, to the exclusion of any other: "http://uri.etsi.org/19602/SvcType/Register". Service name (clause 6.6.2) The ServiceName component shall contain the name of the register for which the registrar identified through the TEName component is responsible. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 69 LoTE component Additional requirement Service digital identity (clause 6.6.3) The ServiceDigitalIdentity component shall contain one or more X.509 certificates which can be used to verify the signature or seal created by the registrar on the register data and for which the certified identity data include the name of the registrar, and where applicable, the registration number of the registrar, as specified in the TEName and TETradeName components respectively. Service current status (clause 6.6.4) The ServiceStatus component shall not be used. As noted in clause 6.6.0 of the present document, when the HistoricalInformationPeriod component is absent, or present with a zero value, and the ServiceStatus component is absent, this signifies that all listed trusted entity services have the same approval status in the list of trusted entities scheme. Under the present profile, the absence of the service status means that all listed registrars and the registers they are responsible for are currently mandated by an EU Member State to register wallet relying parties in that Member State. When a listed registrar does not have that mandate anymore, it shall be removed from the list. Current status starting date and time (clause 6.6.5) The StatusStartingTime component shall not be used. As noted in clause 6.6.0 of the present document, when the StatusStartingTime component is absent, this signifies verification of the approval status of a listed entity service can only be done at current time. LoTE without the StatusStartingTime component are not suitable for verification of approval statuses of entity services in the past. Under the present profile, an HTTP URI leading to historical previous version of the list of registrars and registers is provided through the SchemeInformationURI component. Scheme service definition URI (clause 6.6.6) No additional requirements. Service supply points (clause 6.6.7) The ServiceSupplyPoint component shall contain the URI where the register is available in a machine processable manner. Any signed or sealed register data that can be obtained at the URI referenced in the ServiceSupplyPoint component shall be able to be authenticated using one of the certificates listed in ServiceDigitalIdentity component. TE service definition URI (clause 6.6.8) No additional requirements. Service information extensions (clause 6.6.9) No additional requirements. History information (clause 6.4.4) No additional requirements. I.4 Signature The list of registrars and registers shall be signed by means of a compact JAdES Baseline B signature as specified in ETSI TS 119 182-1 [3]. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 70 History Document history V1.1.1 November 2025 Publication |
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 (clause 4.2); and - JSON-LD W3C VC EAAP (Annex A). NOTE 1: The realization of X509-AC EAAP will be added in the next version of the present document. 2) Specifies two (2) profiles of protocols for allowing Relying Parties (RP hereinafter) to request EAAPs or Personal Identification Data (PID hereinafter) to the EUDI Wallet, and the EUDI Wallet to send the requested EAAPs/PIDs to the RP. One of the profiles supports two transmission mechanisms, namely: API-mediated and non-API mediated. The other profile only supports the non-API mediated transmission mechanisms, as shown below: a) A profile is built on ISO/IEC 18013-5 [10] for non-API mediated transmission mechanism only. This profile is named ISO/IEC-mdoc profile and it is defined in clause 5 of the present document. b) A profile is built on OpenID4VC-HAIP [11] for both API-mediated and non-API mediated transmission mechanisms, as follows: Sections 5, 5.1, 5.3, 7, and 8 of [11] for transmission via Redirects or non-API mediated transmission mechanism; and Sections 5, 5.2, 5.3, 7, and 8 of [11] for API mediated transmission mechanism. This profile is named OpenID4VC-HAIP profile and it is defined in clause 6 of the present document. NOTE 2: The protocols for requesting and retrieving EAAPs/PIDs defined in OpenID4VC-HAIP [11] are profiles based on OpenID4 VP [7]. |
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 are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] W3C® Recommendation 15 May 2025: "Verifiable Credentials Data Model v2.0". [2] IETF RFC 9901: "Selective Disclosure for JSON Web Tokens", November 2025. [3] W3C® Recommendation 15 May 2025: "Securing Verifiable Credentials using JOSE and COSE". [4] IETF RFC 2397: "The 'data' URL scheme", August 1988. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 7 [5] ETSI TS 119 472-1: "Electronic Signatures and Trust Infrastructures (ESI); Profiles for Electronic Attestation of Attributes; Part 1: General requirements". [6] IETF RFC 9101: "The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)", August 2021. [7] OpenID4 VP: "OpenID for Verifiable Presentations 1.0", July 2025. [8] IETF RFC 7515: "JSON Web Signature (JWS)", May 2015. [9] IETF RFC 7516: "JSON Web Encryption (JWE)", May 2015. [10] ISO/IEC 18013-5: "Personal identification — ISO-compliant driving licence — Part 5: Mobile driving licence (mDL) application". [11] OpenID4VC-HAIP: "OpenID4VC High Assurance Interoperability Profile 1.0", 29 December 2025. [12] ETSI TS 119 612: "Electronic Signatures and Trust Infrastructures (ESI); Trusted Lists". [13] FIDO Alliance: "Client to authenticator protocol (CTAP)", Review Draft, 21 March 2023. [14] ETSI TS 119 475: "Electronic Signatures and Trust Infrastructures (ESI); Relying party attributes supporting EUDI Wallet user's authorization decisions". |
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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI TS 119 471: "Electronic Signatures and Trust Infrastructures (ESI); Policy and Security requirements for Providers of Electronic Attestation of Attributes Services". [i.2] ETSI TR 119 462: "Electronic Signatures and Trust Infrastructures (ESI); Wallet interfaces for trust services and signing". [i.3] European Digital Identity: "Architecture and Reference Framework (ARF)" version 2.4.0. [i.4] IETF RFC 8152: "CBOR Object Signing and Encryption (COSE)", July 2017. [i.5] ETSI TS 119 182-1: "Electronic Signatures and Trust Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures". [i.6] ETSI TS 119 152-1: "Electronic Signatures and Trust Infrastructures (ESI); CB AdES (CBOR-AdES) digital signatures Part 1: Building blocks and CB-AdES baseline signatures". [i.7] EUDI Wallet TS05: "Specification of common formats and API for Relying Party Registration information". [i.8] W3C® DC API: "Digital Credentials", Working Draft. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 8 |
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 to a specific Relying Party NOTE: This data can be generated in such a way that it is subject-bound. relying party registrar: entity in charge of registering the Relying Party's information necessary to allow for their electronic identification and authentication towards European Digital Identity Wallets |
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 EUDI European Digital Identity GEN General HAIP High Assurance Interoperability Profile JOSE JSON Object Signing and Encryption JSON JavaScript Object Notation JSON-LD W3C VC JOSE JSON-LD W3C Verifiable Credentials secured with JOSE JSON-LD W3C VC SD-JWT JSON-LD W3C Verifiable Credentials secured with SD-JWT JSON-LD W3C VC JSON-LD serialized W3C Verifiable Credentials JSON-LD W3C VP JOSE JSON-LD W3C Verifiable Presentations secured with JOSE JWS JSON Web Signature JWT JSON Web Token KB Key Binding KB-JWT Key Binding JSON Web Token LD Linked Data mDL mobile Driving Licence NFC Near Field Communication OIDFVP OpenID For Verifiable Presentations PID Personal Identification Data REQ Request RO Request Object RP Relying Party SD Selective Disclosure SD-JWT VC Selective Disclosure based JSON Web Token Verifiable Credentials SD-JWT Selective Disclosure based on JSON Web Token SD-JWT+KB SD-JWT with a Key Binding JWT URI Uniform Resource Identifier URL Uniform Resource Locator USB Universal Serial Bus VP Verifiable Presentation ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 9 W3C VC W3C Verifiable Credentials WU Wallet Unit X509-AC X.509 Attribute Certificate |
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 unity for each requirement. The following topic identifiers are used in the body part of the present document: 1) EAAP-SD-JWT VC for requirements on SD-JWT VC EAAPs (clause 4.1 of the present document). 2) EAAP-ISO/IEC-mdoc for requirements on ISO/IEC-mdoc EAAPs (clause 4.2 of the present document). 3) ISO/IEC 18013-SUPPORT for requirements on support by EUDI Wallet and RPs of the ISO/IEC-mdoc profile (clause 5.2 of the present document). 4) ISO/IEC 18013-GEN for common general requirements of the ISO/IEC-mdoc profile (clause 5.3.1 of the present document). 5) ISO/IEC 18013-REQ for common requirements on the EAAP Request of the ISO/IEC-mdoc profile (clause 5.3.2 of the present document). 6) ISO/IEC 18013-RESP for requirements on the EAAP Response of the ISO/IEC-mdoc profile (clause 5.3.3 of the present document). 7) OIDFVP-HAIP-SUPPORT for requirements on support by EUDI Wallet and RPs of the profile built on [11] (clause 6.2 of the present document). 8) OIDFVP-HAIP-GEN for common general requirements of the profile built on [11] (clause 6.3.1 of the present document). 9) OIDFVP-HAIP-COMMON-REQ for common requirements for EAAP Requests of the profile built on [11] (clause 6.3.2.1 of the present document). 10) OIDFVP-HAIP-COMMON-REQ-RO for common requirements for Requests Objects of the profile built on [11] (clause 6.3.2.2 of the present document). 11) OIDFVP-HAIP-COMMON-RESP for common requirements for EAAP Responses of the profile built on [11] (clause 6.3.3 of the present document). 12) OIDFVP-HAIP-REDIRECTS for specific requirements for non-API mediated transmission mechanism for the profile built on [11] (clause 6.4.1 of the present document). 13) OIDFVP-HAIP-REDIRECTS-RO for specific requirements for the Request Object in non-API mediated transmission mechanism for the profile built on [11] (clause 6.4.2 of the present document). 14) OIDFVP-HAIP-API for specific requirements for API-mediated transmission mechanism for the profile built on [11] (clause 6.5.1 of the present document). 15) OIDFVP-HAIP-ADD-API for additional requirements for API-mediated mechanism in the profile built on OpenID4VC-HAIP [11] (clause 6.5.2 of the present document). 16) EAAP-JSON-LD W3C VC JOSE for requirements on JSON-LD W3C VC EAAP (Annex A of the present document). 17) OIDFVP-HAIP-JSON_LD_EAA-GEN-REQ for requirements on JSON-LD W3C VC EAAP (Annex C of the present document). ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 10 18) X509_AC_EAA-GEN-REQ for requirements for requesting presentation of X509-AC EAAP (Annex D of the present document). 4 Implementation of Electronic Attestation of Attributes Presentations |
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 shall be a SD-JWT+KB as specified in IETF SD-JWT [2]. EAAP-SD-JWT VC-02: If the SD-JWT VC EAA does not contain the cnf claim, the corresponding SD-JWT VC EAAP shall be a SD-JWT VC EAAP as specified in IETF SD-JWT [2]. NOTE: If the SD-JWT VC EAA does not contain the cnf claim, the EAA subject binding, if needed, can be ensured by other means (e.g. claims-based binding, biometric-based binding), as specified by the EAA Provider or the rulebook. EAAP-SD-JWT VC-03: A SD-JWT VC EAAP shall be serialized using either the Compact Serialization, as specified in clause 5.2 of IETF SD-JWT [2], or the Flattened JSON Serialization, as specified in clause 8.2 of IETF SD-JWT [2]. EAAP-SD-JWT VC-04: The Key Binding JSON Web Token (KB-JWT) of a SD-JWT VC EAAP (which is a SD-JWT+KB) shall be signed by the EAA subject. |
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 elements and their namespaces. See ETSI TS 119 472-1 for more details. The EAAPs implemented according to the present clause will be designated as ISO/IEC-mdoc EAAP hereinafter. ISO/IEC 18013-5 [10] requires that the mdoc (the EUDI Wallet) builds an instance of type DeviceResponse in response to a correct instance of type DeviceRequest sent by the mdoc reader/verifier (a Relying Party). This instance of DeviceResponse type can contain the documents member, which is an array of instances of type Document. Each element in this array can contain an indication of error if the request of that element was not correctly built or any other problem has occurred during the processing of the request by the mdoc or during the generation of the corresponding document. EAAP-ISO/IEC-mdoc-01: Each element in the documents member of an instance of type DeviceResponse as defined in clause 10.3.3 of ISO/IEC 18013-5 [10] shall be an ISO/IEC-mdoc EAAP if the mentioned element does not contain the errors member. NOTE 2: As each element in the documents member of an instance of type DeviceResponse is of type Document, an ISO/IEC-mdoc EAAP is an instance of type Document that does not contain the errors member. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 11 EAAP-ISO/IEC-mdoc-02: The issuerSigned member of the DeviceResponse message shall contain all the disclosed attributes to be presented that have been signed by the EAA/PID Provider. EAAP-ISO/IEC-mdoc-03: The deviceSigned member of the DeviceResponse message may contain attributes not present in the issuerSigned member if and only if their inclusion has been explicitly authorized by the EAA/PID Provider. NOTE 3: The deviceSigned member is mainly devoted to contain transaction specific data. |
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 defines requirements on support of the profile and transmission mechanisms by RPs and EUDI Wallet. • Clause 5.3 and its subclauses specify the requirements for the protocol. |
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 defined in clause 5.3. ISO/IEC 18013-SUPPORT-03: A Relying Party shall meet the requirements defined in clause 5.3. |
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 the present document modifies a requirement in [10], the modified requirement defined by the present document shall prevail. |
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, which makes equal to COSE_Sign1 type defined in IETF RFC 8152 [i.4]. Therefore, readerAuth is a digital signature. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 12 ISO/IEC 18013-REQ-02: The digital signature implemented in readerAuth shall be generated with the private key whose corresponding public key is enclosed within the RP access certificate. ISO/IEC 18013-REQ-03: The x5chain unprotected header parameter shall contain the RP access certificate in its first element, and its certificate path up to, but excluding, the trust anchor. ISO/IEC 18013-REQ-04: The instances of type ItemsRequest, encapsulated in the elements in the docRequests member, shall contain a non-empty requestInfo member of type RequestInfo. NOTE 2: All the elements in the docRequests member are instances of type ItemsRequest encapsulated in a CBOR byte string (type ItemsRequestBytes). ISO/IEC 18013-REQ-05: The RequestInfo type shall be as the CDDL definition shows below. RequestInfo = { ?"eUWrprc": bstr, ; contains a registration certificate if ; available (see requirements below) "euWrpRegistrarInfo": EUWrpRegistrarInfo ; RP's Registrar-provided information (see ; requirements below. } ISO/IEC 18013-REQ-06: If the RP has a registration certificate, the mentioned requestInfo member shall contain a member with label "euWrprc". ISO/IEC 18013-REQ-07: The member with label "euWrprc" shall map the label "euWrprc" to a CBOR byte string. ISO/IEC 18013-REQ-08: The CBOR byte string mapped to the "euWrprc" label shall contain the serialization of the RP registration certificate. NOTE 3: This new member is required for incorporating the RP registration certificate(s), which are placed in an extension of the requestInfo. ISO/IEC 18013-REQ-09: The mentioned requestInfo member shall contain a member with label "euWrpRegistrarInfo". ISO/IEC 18013-REQ-10: The member with label "euWrpRegistrarInfo" shall map the label "euWrpRegistrarInfo" to a CBOR map, which shall be an instance of the EUWrpRegistrarInfo type. ISO/IEC 18013-REQ-11: The EUWrpRegistrarInfo type shall be as the CDDL definition shows below. EUWrpRegistrarInfo = { "identifier": [+Identifier], ; RP's identifiers as defined in ; Annex B2.2 of [14] "srvDescription": ServiceDescription, ; Description of the RP's service as defined in ; Annex B.2.1 of [14] "registryURI": tstr, ; URI of the RP's Registrar API as defined in ; Annex B.2.1 of [14] "intendedUseIdentifier": tstr ; Registrar-provided identifier of the RP's ; intended use, as defined in ; Annex B.2.7 of [14] "purpose": Purposes, ; Array of multilanguage strings containing the ; registered purposes of the intended data ; processing, as defined in Annex B.2.6 of [14] "policyURI": tstr, ; URI of the privacy policy of the registered ; intended use, as defined in Annex B.2.8 of ; [14] ?"credential": [+Credential] ; Array of credential objects, containing the ; set of attestations and set of attributes per ; attestation registered in the context of the ; intended use, as defined in Annex B.2.9 of ; [14] } Identifier = { ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 13 "type": tstr, ; For possible values, see Annex B.2.5 of [14] "identifier": tstr ; The identifier which identifies the RP. } ServiceDescription = [+ MultiLangString] ; 1 or more localized text ; describing the same service Purposes = [+ MultiLangString] ; 1 or more localized text describing the registered ; purposes of the intended data processing MultiLangString = { "lang": tstr, ; The country code of the localized text. A two-letter Alpha-2 ; language code according to ISO 639 [15](Set 1). "content": tstr ; The localized text as a string. } Credential = { "format": tstr, ; Format of the attestation as defined in Annex B.2.9 of [14] "meta": tstr, ; Object defining additional properties as defined in Annex B.2.9 ; of [14] ?"claim": [+Claim] ; Array of objects specifying the attributes in the requested ; attestation, as defined in Annex B.2.10 of [14]. If not ; available, all attributes are requested. } Claim = { "path": tstr, ; a path pointer that specifies the path to a claim ; within the Credential as defined in Annex B.2.10 ; of [14] ?"values": [+(tstr / int / bool)] ; Array of strings, integers or boolean ; values that specifies the expected values ; of the claim as defined in Annex B.2.10 of [14] } NOTE 4: The information in EUwrpRegistrarInfo is required by the Wallet Unit to be able to verify the RP's registration information for the presentation request's intended use, and present this information to the User. Note that in case the RP uses the services of an intermediary, the identifier in the element mapped to "identifier" label will be different from the name and identifier of the intermediary as included in the intermediary's access certificate. |
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-HAIP [11], sections 5, 5.1, 5.3, 7 and 8; and 2) An API-mediated transmission mechanism built on OpenID4VC-HAIP [11], sections 5, 5.2, 5.3, 7 and 8. The rest of clause 6 is organized as follows: ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 14 • Clause 6.2 defines requirements on support of the profile and transmission mechanisms by RPs and EUDI Wallet. • Clause 6.3 and its subclauses specify common requirements for both transmission mechanisms. • Clause 6.4 specifies requirements that are specific for the non-API mediated transmission mechanism. • Clause 6.5 specifies requirements that are specific for the API-mediated transmission mechanism. • Clause 6.6 deals with security considerations for this profile. NOTE: For the purposes of the present document, section 5 or requirements of section 5 of OpenID4VC-HAIP [11] refers only to the general requirements listed in the introductory text of section 5 and does not extend to subsections 5.1 onwards. |
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 may meet the requirements defined in clause 6.5 of the present document. NOTE 2: The former requirement corresponds to the API-mediated mechanism for presentations flows specified in clause 5.2 of OpenID4VC-HAIP [11]. OIDFVP-HAIP-SUPPORT-03: The EUDI Wallet shall support the cross-device flow using only the API-mediated mechanism. OIDFVP-HAIP-SUPPORT-04: A Relying Party shall meet the requirements defined in clauses 6.3 and 6.4 of the present document. NOTE 3: The former requirement implies that a Relying Party supports the non-API mediated mechanism for presentations flows specified in clause 5.1 of OpenID4VC-HAIP [11]. OIDFVP-HAIP-SUPPORT-05: A Relying Party may meet the requirements defined in clauses 6.5 of the present document. NOTE 4: The former requirement corresponds to the API-mediated mechanism for presentations flows specified in clause 5.2 of OpenID4VC-HAIP [11]. NOTE 5: Requirements OIDFVP-HAIP-SUPPORT-02 and OIDFVP-HAIP-SUPPORT-05 (support of API-mediated transmission mechanisms by the EUDI Wallet and RPs) could change in the future depending on the evolution of W3C DC API [i.8]. |
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 document modifies a requirement in OpenID4VC-HAIP [11], the modified requirement defined by the present document shall prevail. NOTE: This would allow, for instance, to convert in mandatory an optional requirement from OpenID4VC-HAIP [11] or to extend mandatory requirements. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 15 |
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 request_uri parameters that are defined in IETF RFC 9101 [6]. OIDFVP-HAIP-COMMON-REQ-RO-01: The RO JWT body shall contain the verifier_info parameter. OIDFVP-HAIP-COMMON-REQ-RO-02: The verifier_info parameter shall contain RP Registrar-provided data. OIDFVP-HAIP-COMMON-REQ-RO-03: The element in the verifier_info array enclosing the RP Registrar- provided data shall be a JSON Object which shall not contain the credential_ids member. OIDFVP-HAIP-COMMON-REQ-RO-04: The value of the format member of the element in the verifier_info array enclosing the RP Registrar-provided data shall be: "registrar_dataset". OIDFVP-HAIP-COMMON-REQ-RO-05: The value of the data member of the element in the verifier_info array parameter that contains the RP Registrar-provided data shall be a non-empty JSON Object. The data member of the element in the verifier_info array parameter that contains the RP Registrar-provided data: • OIDFVP-HAIP-COMMON-REQ-RO-06: Shall contain the identifier member specified in clause B.2.2 of [14], whose value shall be the RP's identifier. • OIDFVP-HAIP-COMMON-REQ-RO-07: Shall contain the srvDescription member specified in clause B.2.2 of [14], which shall be an array of JSON MultiLangString objects (defined in clause B.2.6 of [14]), whose contents shall be registered user-friendly descriptions of the RP's service. • OIDFVP-HAIP-COMMON-REQ-RO-08: Shall contain the registryURI member specified in clause B.2.1 of [14], whose value shall be the URI of the RP Registrar's API. • OIDFVP-HAIP-COMMON-REQ-RO-09: Shall contain the intendedUseIdentifier member specified in clause B.2.7 of [14], which contains the RP Registrar-provided identifier of the RP's intended use. • OIDFVP-HAIP-COMMON-REQ-RO-10: Shall contain the purpose member specified in clause B.2.7 of [14], which shall be an array of JSON MultiLangString objects (defined in clause B.2.6 of [14]), whose contents shall be the registered purposes of the intended data processing. • OIDFVP-HAIP-COMMON-REQ-RO-11: Shall contain the policyURI member specified in clause B.2.8 of [14], which shall contain the privacy policy URI of the registered intended use. • OIDFVP-HAIP-COMMON-REQ-RO-12: May contain the credential member specified in clause B.2.7 of [14], which shall be an Array of Credential objects (defined in clause B.2.9 of [14]), whose contents shall contain the set of attestations and set of attributes per attestation registered in the context of the intended use. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 16 NOTE 2: According to EUDI Wallet ARF [i.3], if the User indicated after being presented the presentation request, or as a general User setting, that they want to verify the information registered about the Relying Party and its intended use, but the Relying Party did not send a registration certificate to the EUDI Wallet, it will connect to the URL of the API of the Relying Party Registrar (see EUDI Wallet TS05 [i.7]) to obtain and verify this information. Information necessary for the presentation on the UI includes the user-friendly name and unique identifier of the Relying Party and a user-friendly description of the intended use of the Relying Party, including the list of requested attestations and their attributes, and the URI of the applying privacy policy (for purposes of informing User). The URL to the API of the Registrar of the Relying Party, the unique identifier of the Relying Party and the identifier of the intended use of the Relying Party are needed for the API query that is used to verify the validity of presented data from the Registrar of the Relying Party. Note that in case the RP uses the services of an intermediary, the identifier of requirement OIDFVP-HAIP-COMMON-REQ-RO-06 will be different from the identifier of the intermediary as included in the intermediary's access certificate. OIDFVP-HAIP-COMMON-REQ-RO-13: If the RP has a registration certificate, one of the elements of the verifier_info parameter shall include it. OIDFVP-HAIP-COMMON-REQ-RO-14: The element in the verifier_info array enclosing the registration certificate shall be a JSON Object which shall not contain the credential_ids member. OIDFVP-HAIP-COMMON-REQ-RO-15: The value of the format member of the element in the verifier_info array enclosing the registration certificate shall be: "registration_cert". OIDFVP-HAIP-COMMON-REQ-RO-16: The value of the data member of the element in the verifier_info array enclosing the registration certificate shall be the base64url encoding of the serialized RP registration certificate. OIDFVP-HAIP-COMMON-REQ-RO-17: The Authority Key Identifier shall use the ETSI trusted Lists (specified in ETSI TS 119 612 [12]) mechanism ("etsi_tl" type). OIDFVP-HAIP-COMMON-REQ-RO-18: The RO JWT body shall contain the client_metadata parameter. OIDFVP-HAIP-COMMON-REQ-RO-19: The client_metadata parameter shall contain the jwks member. OIDFVP-HAIP-COMMON-REQ-RO-20: The jwks member of the client_metadata parameter shall contain the kid and use parameters for identifying the key and the use of the identified key, respectively. OIDFVP-HAIP-COMMON-REQ-RO-21: The kid parameters shall univocally identify one key. NOTE 3: Clause 6.2 specifies the key types and the algorithms for the present profile. OIDFVP-HAIP-COMMON-REQ-RO-22: The RO JWT body shall contain the aud parameter. OIDFVP-HAIP-COMMON-REQ-RO-23: The RO shall be signed by the RP using the private key whose corresponding public key is enclosed within the RP access certificate. |
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 at least a custom URL scheme "eu-eaap://" for its authorization_endpoint. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 17 OIDFVP-HAIP-REDIRECTS-04: The Authorization Request shall contain the request_uri parameter, and therefore shall not contain the Request Object (RO). NOTE: With this mechanism of transmission, the Request Object is passed by reference to the EUDI Wallet. |
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 Header of the JWS signature on the RO shall contain the RP access certificate in its first element, and its certificate path up to, but excluding, the trust anchor. OIDFVP-HAIP-REDIRECTS_RO-03: The JWS Protected Header of the JWS signature on the RO shall incorporate the iat header parameter. 6.5 Specific requirements for API-mediated transmission mechanism |
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 Authorization Requests with exchange protocol value set to "openid4vp-1-unsigned". |
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 would enhance the services provided by the Operating System to the EUDI Wallet, for example, attestation selection in the context of the mediating API. There are the considerations related to operating systems and browsers which fall out of the control of implementers, which can be taken into account as indicated in the following notes 2 to 4: NOTE 2: A presentation request from a Relying Party supporting clause 5.2 of [11] can be processed by the browser and/or the Operating System for searching available EAAs, for preventing fraud targeting the User, or for troubleshooting purposes. NOTE 3: A presentation request from a Relying Party supporting clause 5.2 of [11] is expected to be processed by the browser and/or the Operating System for User security purposes. NOTE 4: A presentation request from a Relying Party supporting clause 5.2 of [11] is expected not to be processed by the browser and/or the Operating System for market analysis purposes (including as a secondary purpose) or for the browser's and/or the Operating System's internal purposes. OIDFVP-HAIP-ADD-API-02: If an EUDI Wallet deletes on the User's request a PID or EAA previously disclosed to the mediating API that works in accordance with clause 5.2 of [11], the EUDI Wallet shall disclose the fact that it no longer stores this PID or EAA to the mediating API. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 18 OIDFVP-HAIP-ADD-API-03: If the User uninstalls their EUDI Wallet, the EUDI Wallet shall disclose the fact that it no longer stores any previously disclosed PID(s) or EAA(s) to the mediating API that works in accordance with clause 5.2 of [11]. OIDFVP-HAIP-ADD-API-04: The EUDI Wallet shall provide a global user setting to disable the disclosure of stored EAAs via a mediating API that works as is defined in OIDFVP-HAIP-ADD-API-01. When this setting is disabled, the EUDI Wallet shall not advertise or respond to the API-mediated presentation or issuance requests. OIDFVP-HAIP-ADD-API-05: Where supported by the browser and Operating System of the device of the EUDI Wallet, the EUDI Wallet shall use the CTAP 2.2 hybrid flow as defined in section 11.5 of [13] for cross-device communication between a browser and the device that the EUDI Wallet is installed in. NOTE 5: This flow establishes a secure tunnel between the browser and the device, which is then used to exchange the presentation request and the corresponding response. OIDFVP-HAIP-ADD-API-06: The browsers and Operating Systems shall use short-range CTAP transport bindings to transfer CTAP2 messages over BLE, NFC or USB, whichever applies. NOTE 6: The requirements defined in the present clause are the requirements defined in clause 5.5.2 applied to a mediating API that works in accordance with clause 5.2 of [11]. |
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-1 [5]. These EAAPs shall be generated as specified in W3C Recommendation (15 May 2025): [3]. This W3C Recommendation defines how to secure JSON-LD W3C Verifiable Credentials and JSON-LD W3C Verifiable Presentations either with JWS (the W3C Recommendation uses JOSE), or with SD-JWT. The EAAPs specified in clause A.2 of the present document use JWS signatures as specified in IETF RFC 7515 [8], for generating EAAPs of both JSON-LD W3C VC JOSE EAAs and JSON-LD W3C VC SD-JWT EAAs. These EAAPs will be designated as JSON-LD W3C VP JOSE EAAPs. A.2 JOSE-signed JSON-LD W3C EAAPs for JSON-LD W3C EAAs EAAP-JSON-LD W3C VC JOSE-01: A JSON-LD W3C VC JOSE EAAP shall meet the requirements defined in: clause 4.13 of [1], clause 3.1.2 of W3C Recommendation (15 May 2025): [3], and the requirements defined in the present clause. EAAP-JSON-LD W3C VC JOSE-02: A JSON-LD W3C VC JOSE EAAP shall be a JWS signature generated by the EAA subject. EAAP-JSON-LD W3C VC JOSE-03: The payload of a JSON-LD W3C VC JOSE EAAP shall be an object meeting the requirements defined in clause 4.13 of "Verifiable Credentials Data Model v2.0" [1]. EAAP-JSON-LD W3C VC JOSE-04: The payload of a JSON-LD W3C VC JOSE EAAP shall have the verifiableCredential property. NOTE 1: The verifiableCredential property is defined in clause 4.13 of [1] as an array. Each element of the verifiableCredential array encapsulates either a sequence of one or more JSON-LD W3C VC JOSE EAAs or a sequence of one or more JSON-LD W3C VC SD-JWT EAA as specified in clause 7 of ETSI TS 119 472-1 [5]. EAAP-JSON-LD W3C VC JOSE-05: Each element in the verifiableCredential array shall have the type, @context, and id properties. EAAP-JSON-LD W3C VC JOSE-06: The type property child of each element in the verifiableCredential array shall have the value EnvelopedVerifiableCredential. NOTE 2: This value signals that each element in the verifiableCredential array contains signed JSON-LD W3C VC JOSE EAAs and/or JSON-LD W3C VC SD-JWT EAAs as specified in clause 7 of ETSI TS 119 472-1 [5]. EAAP-JSON-LD W3C VC JOSE-07: The id property child of each element in the verifiableCredential array shall contain one or more data URIs as specified in IETF RFC 2397 [4]. EAAP-JSON-LD W3C VC JOSE-08: Each data URI within the id property shall be separated from the next one by the ';' character. EAAP-JSON-LD W3C VC JOSE-09: If the URI encapsulates a sequence of one or more JSON-LD W3C VC JOSE EAAs then the media type of the id property shall be application/vc+jwt. NOTE 3: These values declare that the data URL encapsulates a sequence of one or more JSON-LD W3C VC JOSE EAAs. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 20 EAAP-JSON-LD W3C VC JOSE-10: If the URI encapsulates a sequence of one or more JSON-LD W3C VC SD-JWT EAAs then the media type of the id property shall be application/vc+sd-jwt. NOTE 4: These values declare that the data URL encapsulates a sequence of one or more JSON-LD W3C VC SD-JWT EAAs. EAAP-JSON-LD W3C VC JOSE-11: All the signed JSON-LD W3C VC EAAs in the data part of the data URL of the id property shall use the same Serialization, either the Compact Serialization or the base64 encoding of the Flattened JSON. EAAP-JSON-LD W3C VC JOSE-12: If all the signed JSON-LD W3C VC EAAs in the data part of the data URL of the id property are base64 encoding of the Flattened JSON Serialization mentioned before, the string ";base64," shall be inserted between the value of the media type and the data part. NOTE 5: As a consequence of the former requirements JSON-LD W3C VC EAAs using Compact Serialization and JSON-LD W3C VC EAAs using Flattened JSON Serialization, are placed in different elements of the verifiableCredential array. NOTE 6: Therefore, each object in the verifiableCredential array encapsulates a sequence of one or more JSON-LD W3C VC JOSE EAAs or a sequence of one or more JSON-LD W3C VC SD-JWT EAAs as specified in clause 7 of ETSI TS 119 472-1 [5]. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 21 Annex B (informative): EAAP implementation based on X.509 Attribute Certificates (X509-AC) NOTE: To be completed in later versions. A possible solution would be to use an enveloping JAdES signature, specified in ETSI TS 119 182 [i.5], with the srAttrs header parameter, enclosing the certified member containing an array of X.509 Attribute certificates. Also other solutions need to be investigated. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 22 Annex C (normative): Requirements for requesting presentation of JSON-LD W3C-VC EAAs C.1 Introduction The present annex defines requirements for requesting and retrieving JSON-LD W3C-VC EAAP using the profiles based on HAIP defined in the present document. C.2 Authorization Request OIDFVP-HAIP-JSON_LD_EAA-GEN-REQ-01: For requesting a JSON-LD W3C-VC EAA presentation as specified in Annex A of the present document, the format claim within the dcql_query shall have the value "vp+jwt". ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 23 Annex D (normative): Requirements for requesting presentation of X509-AC EAAs D.1 Introduction The present annex defines requirements for requesting and retrieving X509-AC EAA Presentations using the profiles based on HAIP defined in the present document. D.2 Authorization Request X509_AC_EAA-GEN-REQ-01: For requesting a X509-AC EAAP as specified in Annex B of the present document, the format claim within the dcql_query shall have the value "x509_attr". ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 24 Annex E (informative): Change history Date Version Information about changes 28/12/2025 V1.1.2 Major changes performed based on comments on v1.1.1. Below follow details: 1) Major re-structuring of the material due to the incorporation of API-mediated transmission mechanisms for both profiles ISO/IEC-mdoc (built on ISO/IEC 18013) and HAIP. Now the structure for each profile contains: • Requirements on EUDI Wallet and RP support • Common requirements for all the transmission mechanisms • Specific requirements for non-API mediated transmission mechanisms. • Specific requirements for API-mediated transmission mechanisms 2) ISO/IEC-mdoc profile: • Deleted a number of wrong set of HAIP requirements that had been placed in clauses defining the profile built on ISO/IEC 18013). This was clause 5.2 of v1.1.1. • EAAP Request: Definition of new member requestInfo with RP's Registrar- provided information and optionally the registration certificate of the RP. • EAAP Response: o deviceSigned may now contain attributes IF the EAA Provider has explicitly authorized them. This is for covering certain use cases apparently requested by Germany (self-issued EAAs). o Suppressed mention to algorithms (wrong algorithms taken from HAIP): ISO specifies the usable algorithms. o Suppressed requirement of deviceAuth containing only deviceSignature (ISO also allows MAC: deviceMac allowed). • Dropped requirements that are repetition of ISO requirements • Added specific requirements for API-mediated transmission mechanism 3) HAIP profile. • Dropped requirement mandating that EUDI Wallet supports both A128GCM and A256GCM, as this could leave out some implementations. Note that RPs are mandated to support both algorithms. • Kept details only on how to requests presentations of EAA built on SD-JWT VC and ISO/IEC-mdoc. The details on how to requests presentations of EAA built on X.509-AC and JSON-LD W3C VC, moved to Annexes A and B. • Make verifier_info mandatory in RO JWT body. • verifier_info shall contain registrar-provided data. • If registration certificate available, then verifier_info shall contain it • Defined details for the element containing registrar-provided data. NO trade_name: assumed concerns mentioned for ETSI TS 119 472-3 also apply here. • Dropped requirements that repeat requirements either in HAIP or in OID4VP • Dropped requirements on iat and aud in RO. • Not mandatory that EAAPs are signed • Added specific requirements for API-mediated transmission mechanism 16/1/2026 V1.1.3 Implemented dispositions to comments to v1.1.2 agreed at the two ad hoc calls held on January 2026. See clause "Comments raised by EC experts team and iDAKTO" of document https://docbox.etsi.org/ESI/ESI/05- CONTRIBUTIONS/2026/ESI(26)000030r1_ESI_88a_Disp2Comms_iDAKTO_EC2_TS_ 119472-2v1_1_2.doc the dispositions implemented in this version. ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 25 Date Version Information about changes 30/1/2026 V1.1.4 Implemented dispositions to comments to v1.1.3 agreed at ESI#88a meeting. • Dropped the API-mediated mechanism from the ISO-mdoc profile. • Make support by Wallet and RPs of API-mediated mechanism in HAIP, optional. • Add a note reporting that this can change in the future depending on the evolution of DC-API. • Add an informative reference to DC-API. • Make optional the presence of credential parameter in the RO (OpenID4VC- HAIP profile). • Keep in clause 6.3.2.2 requirements that are not imposed by neither OpenID4VC nor by HAIP. • Add a note explaining that JAR actually mandates that all the parameters of the Authorization Request are placed in the RO. • Modify CDDL in clause 5.3.2 for adding to EUWrpRegistrarInfo, purpose (mandatory), policyUri (mandatory), and credential (optional). 4/2/2026 V1.1.5 Editorial changes: • Removed DM from Annex A Title (from "EAAP implementation based on JSON-LD W3C VC DM" to "EAAP implementation based on JSON-LD W3C VC", for coherence with notation used in TS 119 472-1 clause 7. • Removed DM abbreviation from clause 3.3 Abbreviations • Changed "W3C VC DM W3C Verifiable Credentials Data Model" to "W3C VC W3C Verifiable Credentials" in clause 3.3 Abbreviations ETSI ETSI TS 119 472-2 V1.2.1 (2026-03) 26 History Version Date Status V1.1.1 December 2025 Publication V1.2.1 March 2026 Publication |
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 Attributes, and the Electronic Attestations of Attributes issued by or on behalf of a public body responsible for an authentic source, also defined in Regulation (EU) 2024/1183 [i.2] clause 4. 3) Defines 4 realizations for the former data model. These realizations include, wherever needed, specific requirements for the Qualified Attestations of Attributes, and the Electronic Attestations of Attributes issued by or on behalf of a public body responsible for an authentic source, defined in Regulation (EU) 2024/1183 [i.2], particularized for the different realizations. Below follows the list of realizations: a) SD-JWT VC. Realization based on SD-JWT VC (clause 5). SD-JWT VC is specified in IETF SD-JWT [5]. b) ISO/IEC-mdoc. Realization based on the structures defined in ISO/IEC 18013-5 [12], suitably extended by the present document, and data elements defined in ISO/IEC 18013-5 [12], ISO/IEC 23220-2 [13], and the present document. NOTE: ISO/IEC 18013-5 [12] defines a namespace and a set of elements (placed in the mentioned namespace) suitable for EAAs that are mobile driving licenses. ISO/IEC 23220-2 [13] defines another namespace and a set of elements of general use in any type of electronic document, suitable for EAAs that are NOT mobile driving licenses. c) JSON-LD W3C-VC. Realization based on JSON-LD serialization of W3C Verifiable Credentials Data Model (clause 7). W3C Verifiable Credentials Data Model is specified in W3C Recommendation (15 May 2025): "Verifiable Credentials Data Model v2.0" [1]. d) X.509-AC. Realization based on X.509 Attribute Certificates (clause 8). X.509 Attribute Certificates are specified in IETF RFC 5755 [6]. 4) Aims to support the Commission Implementing Regulation (EU) 2024/2977 [i.3]. |
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 are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] W3C® Recommendation (15 May 2025): "Verifiable Credentials Data Model v2.0". [2] W3C® Recommendation (15 May 2025): "Securing Verifiable Credentials using JOSE and COSE". (W3C VC_JOSE_COSE). [3] IETF SD-JWT VC draft-ietf-oauth-sd-jwt-vc-13: "SD-JWT-based Verifiable Credentials (SD-JWT VC)", November 2025. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 11 [4] IETF RFC 7519 (May 2015): "JSON Web Token (JWT)". [5] IETF SD-JWT draft-ietf-oauth-selective-disclosure-jwt-22: "Selective Disclosure for JWTs (SD-JWT)", May 2025. [6] IETF RFC 5755 (January 2010): "An Internet Attribute Certificate Profile for Authorization". January 2010. [7] Recommendation ITU-T X.680-X.683: "Information technology - Abstract Syntax Notation One (ASN.1)". [8] IETF RFC 7515 (May 2015): "JSON Web Signature (JWS)". [9] IETF RFC 5280 (May 2008): "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". [10] W3C® Recommendation (5 April 2012): "W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes". [11] ETSI TS 119 182-1: "Electronic Signatures and Trust Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures". [12] ISO/IEC 18013-5: "Personal identification — ISO-compliant driving licence Part 5: Mobile driving licence (mDL) application ". [13] ISO/IEC 23220-2: "Cards and security devices for personal identification — Building blocks for identity management via mobile devices — Part 2: Data objects and encoding rules for generic eID-System". [14] IETF RFC 7800 (April 2016): "Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)". [15] ISO 3166-1:2020: "Codes for the representation of names of countries and their subdivisions — Part 1: Country codes". [16] ETSI EN 319 412-1: "Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 1: Overview and common data structures". [17] ETSI TS 119 412-6: "Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 6: Certificate profile requirements for PID, Wallet, EAA, QEAA, and PSBEAA providers". [18] W3C® Recommendation (15 May 2025): "Data Integrity ECDSA Cryptosuites v1.0". [19] W3C® Candidate Recommendation (3 April 2025): "Data Integrity BBS Cryptosuites v1.0". [20] IETF RFC 9360 (February 2023): "CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 Certificates". [21] JSON Schema Core: "JSON Schema: A Media Type for Describing JSON Documents". [22] IETF RFC 8610 (June 2019): "Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures". [23] W3C® Recommendation (20 July 2017): "Shapes Constraint Language (SHACL)". [24] W3C® Recommendation (15 May 2025): "Bitstring Status List v1.0". [25] IETF draft-ietf-oauth-status-list-13: "Token Status List (TSL)". [26] W3C® Recommendation (15 May 2025): "Verifiable Credential Data Integrity v1.0". [27] IETF RFC 5646 (September 2009): "Tags for Identifying Languages". [28] IETF RFC 6960 (June 2013): "X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP". ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 12 [29] W3C® Recommendation (16 July 2020): "JSON-LD 1.1. A JSON-based Serialization for Linked Data". [30] IETF RFC 7517 (May 2015): "JSON Web Key (JWK)". [31] OpenId Fundation: "OpenID Identity Assurance Schema Definition 1.0", October 2024. |
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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI TS 119 471:"Electronic Signatures and Trust Infrastructures (ESI); Policy and Security requirements for Providers of Electronic Attestation of Attributes Services". [i.2] Regulation (EU) 2024/1183 of the European Parliament and of the Council of 11 April 2024 amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity Framework. [i.3] Commission Implementing Regulation (EU) 2024/2977 of 28 November 2024 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards person identification data and electronic attestations of attributes issued to European Digital Identity Wallets". [i.4] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.5] EU Architecture and Reference Framework version 2.4.0. [i.6] EUDI Wallet TS11: "Specification of interfaces and formats for the catalogue of attributes and the catalogue of attestations". |
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 technical validity period: dates (and possibly times) from and up to which the EAA is valid NOTE: Definition taken from the ARF [i.5]. Electronic Attestation of Attributes context: information, additional to the electronic attestation of attributes itself, that the relying party may require for being fully able to process it ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 13 Electronic Attestation of Attributes issued by or on behalf of a public body responsible for an authentic source (PuB-EAA): electronic attestation of attributes issued by a public sector body that is responsible for an authentic source or by a public sector body that is designated by the Member State to issue such attestations of attributes on behalf of the public sector bodies responsible for authentic sources in accordance with Article 45f and with Annex VII of eIDAS2 Regulation [i.2] Electronic Attestation of Attributes Presentation (EAAP): tampered-proof presentation of an electronic attestation of attributes built in such a way that the subject of the EAA presented can be trusted through a cryptographic verification |
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 Signing and Encryption CRL Certificate Revocation List DER Distinguished Encoding Rules DID Decentralized Identifier EAA Electronic Attestation of Attributes EAAP Electronic Attestation of Attributes Presentation ECDSA Elliptic Curve Digital Signature Algorithm ISO/IEC-mdoc EAA EAA implemented using the structures of ISO/IEC 18013-5 [12] and the data elements defined in ISO/IEC 18013-5 [12] and ISO/IEC 23220-2 [13] as specified in the present document ISO/IEC-mdoc PuB-EAA PuB-EAA implemented using the structures of ISO/IEC 18013-5 [12] and the data elements defined in ISO/IEC 18013-5 [12] and ISO/IEC 23220-2 [13] as specified in the present document ISO/IEC-mdoc QEAA QEAA implemented using the structures of ISO/IEC 18013-5 [12] and the data elements defined in ISO/IEC 18013-5 [12] and ISO/IEC 23220-2 [13] as specified in the present document JOSE JSON Object Signing and Encryption JSON-LD W3C VC JOSE JSON-LD W3C Verifiable Credentials secured with JOSE. JSON-LD W3C VC SD-JWT JSON-LD W3C Verifiable Credentials secured with SD-JWT JSON-LD W3C-VC EAA EAA implemented with JSON-LD serialization of "Verifiable Credentials Data Model v2.0" [1] as specified in the present document JSON-LD W3C-VC PuB-EAA PuB-EAA implemented with "Verifiable Credentials Data Model v2.0" [1] as specified in the present document JSON-LD W3C-VC QEAA QEAA implemented with "Verifiable Credentials Data Model v2.0" [1] as specified in the present document JSON-LD W3C-VC JSON-LD serialized W3C Verifiable Credentials JWS JSON Web Signature JWT JSON Web Token LD Linked Data mDL mobile Driving Licence OCSP Online Certificate Status Protocol OID Object Identifier PID Personal Identification Data PSB Public Sector Body PuB-EAA Electronic Attestation of Attributes issued by or on behalf of a public body responsible for an authentic source ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 14 QEAA Qualified Electronic Attestation of Attributes RDF Resource Description Framework SD-JWT VC EAA EAA implemented with IETF SD-JWT VC [3] as specified in the present document SD-JWT VC PuB-EAA PuB-EAA implemented with IETF SD-JWT VC [3] as specified in the present document SD-JWT VC QEAA QEAA implemented with IETF SD-JWT VC [3] as specified in the present document SD-JWT VC Selective Disclosure based JSON Web Token Verifiable Credentials SD-JWT Selective Disclosure based JSON Web Token SHA Secured Hash Algorithm SHACL Shapes Constraint Language URI Uniform Resource Identifier URL Uniform Resource Locator URN Uniform Resource Name UTC Coordinated Universal Time VAT Value Added Tax VC Verifiable Credential X.509-AC EAA EAA implemented with IETF RFC 5755 [6] as specified in the present document X.509-AC PuB-EAA PuB-EAA implemented with IETF RFC 5755 [6] as specified in the present document X.509-AC QEAA QEAA implemented with IETF RFC 5755 [6] as specified in the present document X.509-AC X.509 Attribute Certificate XML Extensible Markup Language XSD XML Schema Definition |
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 signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per [i.2]. General requirements for EAAs (including generally applicable requirements for Qualified EAAs and EAAs issued by or on behalf of a public body responsible for an authentic source) are assigned identifiers resulting from the concatenation of the following components: 1) The initial string "EAA-". 2) The number of the clause where the requirement is defined. 3) A number of 2 digits. In each clause the number will start in 01 and it will increase in one unity for each requirement. Wherever it is required, the present document defines specific requirements only applicable to Qualified Electronic Attestation of Attributes, as defined in Annex V of Regulation (EU) 2024/1183 [i.2]. The present document refers to this type of EAAs either as "EU Qualified EAA" or by the abbreviation QEAA. Some of these specific requirements for QEAA may replace general EAAs requirements (those ones whose identifiers start with "EAA-") already defined. These requirements are defined within specific clauses clearly identified with the title: "Requirements for EU Qualified Electronic Attestation of Attributes (QEAA)". The present document assigns an identifier for each of these requirements as per the concatenation of the following components: 1) The initial string "QEAA-". 2) The number of the clause where the requirement is defined. 3) A number of 2 digits. In each clause the number will start in 01 and it will increase in one unity for each requirement. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 15 Wherever it is required, the present document defines specific requirements only applicable to Electronic Attestation of Attributes issued by or on behalf of a public body responsible for an authentic source, as defined in Annex VII of Regulation (EU) 2024/1183 [i.2]. The present document refers to this type of EAAs with the abbreviation PuB-EAA. Some of the requirements for PuB-EAA may replace general requirements (those ones whose identifiers start with "EAA-") already defined. These requirements are defined within specific clauses clearly identified with the title: "Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA)". The present document assigns an identifier for each of these requirements as per the concatenation of the following components: 1) The initial string "PuB-EAA-". 2) The number of the clause where the requirement is defined. 3) A number of 2 digits. In each clause the number will start in 01 and it will increase in one unity for each requirement. |
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 metadata. 4) Clause 4.5 defines semantics for key binding. 5) Clause 4.6 defines semantics for the digital signature of the EAA and the EAA signing certificate. |
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 these components. EAA-4.2.1.3-03: The incorporation, value, and placement of the information of the EAA context components shall depend on the specific EAA implementation. |
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 reference in the aforementioned sequence: 1) Shall include a type identifier; and 2) Shall include a URI Reference which references the schema itself. EAA-4.2.1.4-04: The incorporation and placement of the aforementioned sequence shall depend on the specific EAA implementation. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.2 EAA category |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.