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

Thank you, Anil.
What are the scenarios and customers who will support this profile? that also drove decisions in this profile?
Are there any plan to extend this profile to include transport protocols, DID methods (if DIDs are used), revocation methods, crypto suites, etc. that is required for the full interoperability?
Cheers,
Kristina

From: John, Anil <anil.john@hq.dhs.gov>
Sent: Thursday, September 29, 2022 11:24 AM
To: public-credentials@w3.org
Subject: FYI >> DHS W3C VC/DID Implementation Profile: Credential Data Model Representation Syntax & Proof Format

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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-credentials%2F2022Jul%2Fatt-0027%2FDHS.SVIP-Scaling.W3C.VC.DID.Interoperability-SHARE_20220712.pdf&data=05%7C01%7Ckristina.yasuda%40microsoft.com%7C725e03419f4742349a2508daa248a9a6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638000730278809626%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=joydOCULJZsb4Qz1BiNwkOeW6wYZfKzYXhIsE6Aco8A%3D&reserved=0>) 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dhs.gov%2Fscience-and-technology&data=05%7C01%7Ckristina.yasuda%40microsoft.com%7C725e03419f4742349a2508daa248a9a6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638000730278809626%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uHvWIobmx%2FmgIV8DkakT69X8TkSKNK90MeL8np3kb6s%3D&reserved=0>[/Users/holly.johnson/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1972159395]