W3C home > Mailing lists > Public > public-credentials@w3.org > November 2021

RE: Verifiable Driver's Licenses and ISO-18013-5 (mDL)

From: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>
Date: Tue, 30 Nov 2021 12:12:26 +0000
To: "Michael Herman (Trusted Digital Web)" <mwherman@parallelspace.net>, Manu Sporny <msporny@digitalbazaar.com>, W3C Credentials CG <public-credentials@w3.org>
Message-ID: <MWHPR1301MB2094019006FDD6D4C41B6495C3679@MWHPR1301MB2094.namprd13.prod.outlook.com>
p.s. A commentary on our different and diverse working group efforts... I believe that our recent challenges with confirming the DID specification and now with the mDL specification not embracing VCs can be greatly improved if we had an overarching vision, a platform vision, ...a software reference architecture, ...for what we think we're all contributing to.

... else what we have is what Microsoft development platform has been highly criticized for in the past: being a "bunch of stuff" ...a great "bucket of bolts" but just a "bucket of bolts".

Here's one solution ...one example of what I'm talking about ...a place to start...

Trusted Digital Web: 8-Layer Architecture Reference Model (TDW-ARM)



- https://wiktionary.en-academic.com/105734/bucket_of_bolts

- https://hyperonomy.com/2016/06/15/ms-azure-is-a-bit-of-a-bucket-of-bolts-very-good-bolts-but-relative-to-the-other-iot-vendors-a-bucket-of-bolts/

Best regards,

Michael Herman

Far Left Self-Sovereignist

First Principles Thinker

Self-Sovereign Blockchain Architect

Trusted Digital Web

Hyperonomy Digital Identity Lab

Parallelspace Corporation

-----Original Message-----
From: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>
Sent: Monday, November 29, 2021 1:05 PM
To: Manu Sporny <msporny@digitalbazaar.com>; W3C Credentials CG <public-credentials@w3.org>
Subject: RE: Verifiable Driver's Licenses and ISO-18013-5 (mDL)

As with all past standards (ad-hoc, defacto, or otherwise), an #EmbraceAndExtend strategy is often the most useful approach.

Reference: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

-----Original Message-----

From: Manu Sporny <msporny@digitalbazaar.com<mailto:msporny@digitalbazaar.com>>

Sent: Monday, November 29, 2021 9:55 AM

To: W3C Credentials CG <public-credentials@w3.org<mailto:public-credentials@w3.org>>

Subject: Verifiable Driver's Licenses and ISO-18013-5 (mDL)

Hi all,

As some of you might be aware, ISO-18013-5 (mDL -- Mobile Driver's License[1]) was published as a global ISO standard in September 2021. A number of us in the W3C CCG and W3C VCWG attempted to ensure that W3C Verifiable Credentials were supported by the mDL work, but that effort is not reflected in the finalized ISO mDL standard (and due to the way ISO operates, we are not at liberty to share any details). There have been increasing concerns related to the divergence of mDL with W3C Verifiable Credentials[2][3][4][5][6] and to the market dynamics at play[7][8] around mDL.

In an effort to demonstrate that it is possible to express the entire mDL data model, Spruce, MATTR, and Digital Bazaar have collaborated on creating an interoperability test suite for something we're calling the "Verifiable Driver's License" (temporary name):


The test suite demonstrates that a few things are possible in addition to what mDL provides:

1. The mDL data model can be expressed cleanly using W3C Verifiable Credentials.

2. The Verifiable Driver's License can be issued and verified today using the Verifiable Credentials API (mDL does not provide any details on issuance/verification infrastructure).

3. There is demonstrable interoperability today among at least 3 vendors, and we expect that to be true among all the vendors that comply with the Verifiable Credentials API today (we invite all vendors to add their implementations to the test suite).

4. It is possible to express the vDL as a compact QR Code, thus providing a "path to paper" (mDL has no path to paper).

5. It is possible to utilize the BBS+ selective disclosure mechanism to selectively disclose subsets of the Verifiable Driver's License Credential.

6. It is possible to utilize privacy-preserving revocation mechanisms that don't phone home (utilizing privacy-aware technologies like StatusList2021).

7. The Verifiable Driver's License can be exchanged in online scenarios using some of the emerging open wallet protocols. There is also support for offline exchange (via QR Codes and other optical carriers).

All that said, it is also important to understand that the current W3C Verifiable Credentials ecosystem is not capable of radio transmission of the Verifiable Driver's License (e.g., at airline security checkpoints or police traffic stops), and does not currently have the backing of any known "certified" mDL vendor. This is not a case where there is a clear winner; this is the start to a concrete public engagement about the future of these technologies as applied to driving credentials.

CCG Chairs,

Spruce, MATTR, and Digital Bazaar would like to request some time on an upcoming CCG call to introduce this work item to the group and see if there is interest in picking it up:


-- manu

[1]https://www.iso.org/standard/69084.html (paywalled) [2]https://downloads.regulations.gov/DHS-2020-0028-0032/attachment_1.pdf








Manu Sporny - https://www.linkedin.com/in/manusporny/

Founder/CEO - Digital Bazaar, Inc.

News: Digital Bazaar Announces New Case Studies (2021) https://www.digitalbazaar.com/

Received on Tuesday, 30 November 2021 12:12:44 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:25:24 UTC