Complementary by design
The Foundation does not seek to displace any adjacent standard or the body that maintains it. Its scope is the cross-layer framework: trust governance at the access boundary, the attestation envelope, the contract tying a credential to an enterprise authorization, and the operational properties an integrator needs before signing off. The test is concrete: an implementer who builds to the Foundation’s specifications should interoperate with implementations built to the standards below, other than work the Foundation only tracks, without an architectural retrofit.
ISO/IEC 18013-5 and 18013-7
Consumes
The mdoc data model and proximity flow are the canonical credential format and protocol the Foundation anchors on; 18013-7, in progress, covers unattended and online presentation. Foundation extensions live alongside the standards and do not modify them. The mobile driver’s license schemas belong to the issuing authorities.
Aliro (Connectivity Standards Alliance)
Adjacent layer
Aliro defines transport, credential-exchange semantics, and how a reader and a credential establish trust within a session. The Foundation defines whose credentials qualify for that establishment and how a verifier confirms it through the registry. Both reference ISO 18013-5 mdoc structures where they apply. Foundation participants sit on the Aliro Insider Council, and the Foundation is documenting the boundary between the two specifications.
OpenID for Verifiable Presentations and Verifiable Credential Issuance
Carried within
The attestation envelope is designed to be carried within OpenID4VP flows. NFID-aligned credentials are issued through OpenID4VCI, with the pre-authorized code flow as the primary enterprise mechanism. The Foundation adds an access-specific payload to protocols it does not modify.
W3C Verifiable Credentials Data Model 2.0
Consumes
NFID-aligned credentials use the data model and its securing specifications: the COSE-secured form for embedded devices, the SD-JWT form for selective-disclosure scenarios. The Foundation does not duplicate the data model.
FIDO and WebAuthn
Complementary
Authentication establishes that a party is who they claim to be. The Foundation’s framework governs what that party is then authorized to do and how that authorization is trusted. Where both are needed, they work together.
eIDAS 2.0 and the European Digital Identity Wallet
Ecosystem credential category
Treated as an ecosystem-issued credential with its own trust infrastructure, defined by the Architecture and Reference Framework and its implementing acts. The Foundation resolves that trust and does not redefine it. Coordination with the European framework is forward-looking.
NIST identity publications
Consistent with
SP 800-63 on digital identity and its assurance levels, SP 800-157 on derived credentials, and FIPS 140-3 on cryptographic module validation bear on the Foundation’s work. The Foundation does not redefine the NIST assurance levels. A deployment that references them does so against the assurance of the underlying credential, and the framework is designed to be consistent with that referencing.
Open Wallet Foundation
Wallet-agnostic
The Foundation’s architecture consumes credentials from any wallet that meets the issuer’s requirements, and wallets built within the Open Wallet Foundation’s scope are within that set.
ICAO Doc 9303
Ecosystem credential category
Digital passports trace trust through the ICAO Public Key Directory, not the per-jurisdiction model of the mobile driver’s license. The envelope records the anchor appropriate to that category. Coordination with ICAO is forward-looking.
Matter for Access (Connectivity Standards Alliance)
Tracked
An evolving body of work the Foundation tracks and intends to stay interoperable with as its scope settles. The Foundation makes no commitments against specific revisions while that scope is still developing.
The full treatment is Section 7 of the paper.