-
Notifications
You must be signed in to change notification settings - Fork 19
ISO/IEC 18013-7:2025 - ISO-compliant driving licence — Part 7: Mobile driving licence (mDL) add-on functions #1
Copy link
Copy link
Open
Labels
Art 5a(23) P&IProtocols & Interfaces to be supported by the EUDI FrameworkProtocols & Interfaces to be supported by the EUDI FrameworkCIR (EU) 2024/2982Protocols and interfaces - https://data.europa.eu/eli/reg_impl/2024/2982/ojProtocols and interfaces - https://data.europa.eu/eli/reg_impl/2024/2982/ojCIR (EU) 2026/1731Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982Cat: Protocols & InteroperabilityFunctional requirements defining common standards ensuring seamless cross-border interoperability.Functional requirements defining common standards ensuring seamless cross-border interoperability.Cat: Relying PartiesFunctional requirements for relying parties on registration, auth, data requests, and handling.Functional requirements for relying parties on registration, auth, data requests, and handling.Cat: Wallet ProvidersFunctional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Functional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Domain: WalletCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsEssentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialFn: PresentationFunctional: Presentation of attestation and attributes to a Relying PartyyFunctional: Presentation of attestation and attributes to a Relying PartyyFnRAn STS that specifies Functional RequirementsAn STS that specifies Functional RequirementsRegulationStandards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.Standards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.gapThis ticket is about a gap identified in our analysis and needs to be scheduledThis ticket is about a gap identified in our analysis and needs to be schedulednpaThe standard is not publicly availableThe standard is not publicly availablests: needs follow upThe standard needs follow up due to a forthcoming updated versionThe standard needs follow up due to a forthcoming updated versionsts: readyThe standard has a stable version publishedThe standard has a stable version publishedsts: tentative etaThe standard needs more work. Final further away. The target date is tentative and needs reviewThe standard needs more work. Final further away. The target date is tentative and needs reviewtest specificationSTS entry has linked functional conformance testing activities.STS entry has linked functional conformance testing activities.
Milestone
Description
Metadata
Metadata
Assignees
Labels
Art 5a(23) P&IProtocols & Interfaces to be supported by the EUDI FrameworkProtocols & Interfaces to be supported by the EUDI FrameworkCIR (EU) 2024/2982Protocols and interfaces - https://data.europa.eu/eli/reg_impl/2024/2982/ojProtocols and interfaces - https://data.europa.eu/eli/reg_impl/2024/2982/ojCIR (EU) 2026/1731Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982Cat: Protocols & InteroperabilityFunctional requirements defining common standards ensuring seamless cross-border interoperability.Functional requirements defining common standards ensuring seamless cross-border interoperability.Cat: Relying PartiesFunctional requirements for relying parties on registration, auth, data requests, and handling.Functional requirements for relying parties on registration, auth, data requests, and handling.Cat: Wallet ProvidersFunctional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Functional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Domain: WalletCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsEssentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialFn: PresentationFunctional: Presentation of attestation and attributes to a Relying PartyyFunctional: Presentation of attestation and attributes to a Relying PartyyFnRAn STS that specifies Functional RequirementsAn STS that specifies Functional RequirementsRegulationStandards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.Standards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.gapThis ticket is about a gap identified in our analysis and needs to be scheduledThis ticket is about a gap identified in our analysis and needs to be schedulednpaThe standard is not publicly availableThe standard is not publicly availablests: needs follow upThe standard needs follow up due to a forthcoming updated versionThe standard needs follow up due to a forthcoming updated versionsts: readyThe standard has a stable version publishedThe standard has a stable version publishedsts: tentative etaThe standard needs more work. Final further away. The target date is tentative and needs reviewThe standard needs more work. Final further away. The target date is tentative and needs reviewtest specificationSTS entry has linked functional conformance testing activities.STS entry has linked functional conformance testing activities.
Type
Projects
StatusShow more project fields
🏗 In progress
Formal name
ISO/IEC 18013-7:2025 - ISO-compliant driving licence - Part 7: Mobile driving licence (mDL) add-on functions
Overview
This document augments the capabilities of the mobile driving licence (mDL) standardized in ISO/IEC 18013-5 with the following additional functionality of presentation of a mobile driving licence to a reader over the internet.
This document specifies a REST API over which Wallet Instances and Relying Parties can request and present attestations in the mdoc format specified in ISO/IEC 18013-5. As such it is an alternative to the OpenID4VP protocol.
Furthermore, this document specifies an interoperable profile for OpenID4VP, with the aim of using the OpenID4VP protocol to request and present attestations in the mdoc format. Some of the choices made in this profile could conceivably also be used to create a similar profile for requesting and presenting attestations in SD-JWT VC-compliant format.
This standard references draft20 of openid4vp. Technically, it cannot use the same version of openid4vp to do mdocs and sd-jwt.
ISO/IEC 18013-7 Annex B specifies a profile for OpenID4VP. This profile is mdoc-specific, meaning that it only applies if the attestations that are requested and released are in ISO-compliant format. However, this profile is based on draft 18 of OpenID4VP, whereas the latest available version of OpenID4VP is version 1.0. As a final version of OpenID4VP has been published, and if the EC decides that OpenID4VP can be used for requesting and presenting ISO-compliant attestations in the EUDI Wallet ecosystem, this profile needs to be revisited.
Work Plan
Current Version
EC Assessment Status
Forthcoming Version
Testing & Conformance
Updates
Alerts
There are no open alerts.
References
None.