RE: FYI >> DHS W3C VC/DID Implementation Profile: Credential Data Model Representation Syntax & Proof Format

Hello Dmitri,

Glad to hear!

We are doing our best to mine good practices that have been demonstrated to work IRL across multiple, independent implementations as part of our profiling work.

We are fortunate to be working with and receiving constructive feedback from folks who ARE NOT techno-utopian architecture astronauts (“Where the rubber meets the sky and not the road!”), and have been around long enough to have the confidence to change their mind/direction when new information comes in!  :-)

Best Regards,

Anil


From: Dmitri Zagidulin <dzagidulin@gmail.com>
Sent: Wednesday, October 12, 2022 5:39 PM
To: John, Anil <anil.john@hq.dhs.gov>
Cc: public-credentials@w3.org
Subject: Re: FYI >> DHS W3C VC/DID Implementation Profile: Credential Data Model Representation Syntax & Proof Format

CAUTION: This email originated from outside of DHS. DO NOT click links or open attachments unless you recognize and/or trust the sender. Contact your component SOC with questions or concerns.

Anil, this is fantastic, thank you!

I was pleasantly surprised to see the item “SHOULD leverage objects instead of strings to refer to Issuers and Holders”!
We’ve been using issuer objects (which include issuer name & logo) in the VC-Edu task force, and I was planning to campaign for supporting this natively in the VC 2.0 data model. So it’s really great to see support/confirmation for this.

On Thu, Sep 29, 2022 at 2:30 PM John, Anil <anil.john@hq.dhs.gov<mailto:anil.john@hq.dhs.gov>> wrote:
Dear DID/VC Community,

Encouraging and supporting a plurality of independent, interoperable, standards-based implementations to counter vendor/technology lock-in and perverse incentives that accrue market power to entities that can result in a gatekeeper functionality between the Government and its customers has been, and continues to be, a core aspect of our work in the W3C VC/DID ecosystem.

We believe that in order to truly scale interoperability, an implementation profile that makes clear choices is critical AND that the way to create such an implementation profile is by bringing together Implementation Principles (https://lists.w3.org/Archives/Public/public-credentials/2022Jul/att-0027/DHS.SVIP-Scaling.W3C.VC.DID.Interoperability-SHARE_20220712.pdf<https://urldefense.us/v3/__https:/lists.w3.org/Archives/Public/public-credentials/2022Jul/att-0027/DHS.SVIP-Scaling.W3C.VC.DID.Interoperability-SHARE_20220712.pdf__;!!BClRuOV5cvtbuNI!QKGor5H1TxNQN8QTVZsbgFPcrUO3EFCcWUxr-_lKGguV6tjSdBBjCwSo6QXNV4iW4p9C$>) with results and lessons learned from multi-platform, multi-vendor interoperability plug-fests to document choices that work in the real world -- as demonstrated by running code/implementations that demonstrate interoperability, and supporting test suites and other mechanisms that allow for verifying conformance to the profile.

We are walking this path step-by-step by documenting the results and lessons from the DHS sponsored multi-platform, multi-vendor interoperability plug-fests and other rigorous plug-fests with similar goals to develop a “DHS Implementation Profile of W3C Verifiable Credentials and W3C Decentralized Identifiers” to ensure the use of Security, Privacy and Interoperability implementation choices that are acceptable to the USG such that these capabilities can be deployed on and connect to USG networks and infrastructure.

There are many moving pieces to any such implementation, and as we make specific standards profiling choices within the scope of our use of open, global standards and specifications, we will continue our commitment to global transparency in our work by sharing those choices with the DID/VC community on an ongoing basis.

To start, please find attached the DHS Implementation Profile of W3C VCs and W3C DIDs normative guidance on:

•         Credential Data Model Representation Syntax

•         Credential Data Model Proof Format

Best Regards,

Anil

Anil John
Technical Director, Silicon Valley Innovation Program
Science and Technology Directorate
US Department of Homeland Security
Washington, DC, USA

Email Response Time – 24 Hours

[A picture containing graphical user interface    Description automatically generated]<https://www.dhs.gov/science-and-technology>[/Users/holly.johnson/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1972159395]