- From: John, Anil <anil.john@hq.dhs.gov>
- Date: Mon, 8 Mar 2021 23:46:48 +0000
- To: Steve Capell <steve.capell@gmail.com>, "public-credentials@w3.org" <public-credentials@w3.org>
- Message-ID: <SA1PR09MB8815798FE065D1479E015065C5939@SA1PR09MB8815.namprd09.prod.outlook.com>
Hi Steve, Been a while since I connected with my colleagues in Australia. Have been fan and very jealous for a long time regarding your match/no-match DVS implementation ( https://www.idmatch.gov.au/) that helps ensure validation of high value docs against the authoritative source, and as such mitigate identity fraud. If they have any questions about the work, do let them know I am happy to chat with them. 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 [https://www.dhs.gov/science-and-technology/svip] From: Steve Capell <steve.capell@gmail.com> Sent: Saturday, March 6, 2021 9:28 AM To: John, Anil <anil.john@hq.dhs.gov> Cc: public-credentials@w3.org Subject: Re: DHS/SVIP Interoperability Plug-Fest 2 : Features Under Test ... 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. Thank you anil DHS leadership in this area is fantastic. Interoperability doesn’t happen just because there’s a standards document. It has to be forced and tested. I’m working to convince our government in Australia of the importance of taking the same leadership to drive interop and equal playing fields. Your work at DHS is great exemplar that helps me make the case Kind regards Steven Capell Mob: 0410 437854 On 5 Mar 2021, at 9:38 am, John, Anil <anil.john@hq.dhs.gov> wrote: Hello VC/DID Ecosystem & Community, The W3C/CCG Community and the DIF have been very supportive in concretely and truly making true interoperability a priority in the VC/DID ecosystem. In the spirit of keeping the community updated on the work that DHS/SVIP has been doing in this area, I wanted to share an update about what has been accomplished, what is under flight, and what still remains. As you know, we had our first Interop plug-fest last year in May 2020, which was a heavy lift for our portfolio companies -- To be blunt, while there was a lot of hand-waving on interop, that was the first time anyone had demonstrated any manner of concrete cross-vendor / cross-platform interop in the VC/DID community. We demonstrated that interoperability across the following “feature-sets”: * JSON-LD * Linked Data Signatures * DID Resolution * VC-HTTP-API - https://github.com/w3c-ccg/vc-http-api<https://urldefense.us/v3/__https:/github.com/w3c-ccg/vc-http-api__;!!BClRuOV5cvtbuNI!RyyxjHq5rUhrgW0clLNiLoWXAojoBKheYTLIEozSCJE8aiI5A5DOpT7xcr0F9SiEijeX$> * Verifiable Presentation Request - https://w3c-ccg.github.io/vp-request-spec/<https://urldefense.us/v3/__https:/w3c-ccg.github.io/vp-request-spec/__;!!BClRuOV5cvtbuNI!RyyxjHq5rUhrgW0clLNiLoWXAojoBKheYTLIEozSCJE8aiI5A5DOpT7xcr0F9R4t6haf$> * Citizenship Vocabulary - https://w3c-ccg.github.io/citizenship-vocab/<https://urldefense.us/v3/__https:/w3c-ccg.github.io/citizenship-vocab/__;!!BClRuOV5cvtbuNI!RyyxjHq5rUhrgW0clLNiLoWXAojoBKheYTLIEozSCJE8aiI5A5DOpT7xcr0F9UIgB91z$> * Issuer support for multiple mobile/web wallets * Verifier support for multiple mobile/web wallets * CHAPI support for mobile/web based wallets We will be conducting our Plug Fest 2, later this month, where we are testing interoperability across the following feature-sets: * [Everything Tested in Plug Fest 1] << Because we don’t want anything to drop out! * Traceability Vocabulary - https://w3c-ccg.github.io/traceability-vocab/<https://urldefense.us/v3/__https:/w3c-ccg.github.io/traceability-vocab/__;!!BClRuOV5cvtbuNI!RyyxjHq5rUhrgW0clLNiLoWXAojoBKheYTLIEozSCJE8aiI5A5DOpT7xcr0F9Xo0Zdt2$> * Vaccination Certificate Vocabulary - https://w3id.org/vaccination<https://urldefense.us/v3/__https:/w3id.org/vaccination__;!!BClRuOV5cvtbuNI!RyyxjHq5rUhrgW0clLNiLoWXAojoBKheYTLIEozSCJE8aiI5A5DOpT7xcr0F9W9iRHNb$> * FIPS Compliant Cryptographic Primitives * VC Aggregation and Presentation using Verifiable Presentation (VP) * VC Revocation with Herd Privacy * did:web to represent Issuers Only * VP Support for selective disclosure using BBS+ Signatures Because the feature-sets were complex, it took some careful thinking and even more critical implementations by the portfolio companies to move from Plug-Fest 1 to be ready for our upcoming Plug-Fest 2. What is good is that we are now in a place where a common and full level of functionality exists that we feel can serve as the foundation of any enterprise implementation where the enterprise does not wish to buy into the ‘one ring to bind them all’ philosophy. Going forward, we expect to have the plug-fests happen on a faster cadence, with shorter timelines between them, with a smaller set of features under test (perhaps even a single critical feature). That allows members of our cohort, based on the industry verticals or use cases they are focused on, to prioritize what new features they support and when, and also the ability to work on community plug-fests that can test a particular feature-set without the community implementer having to buy into a more complex feature-set. As always, all of the artifacts, tool chains and test suites that we are using and contributing to remains under the purview of the W3C/CCG to support the broader community on the journey to true interoperability. We look forward to and would welcome community contributions to them in order to ensure the work truly benefits the community! 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 <image002.png> <DHS.ST.SVIP.Interoperability-PlugFest-2.pdf>
Attachments
- image/png attachment: image002.png
Received on Monday, 8 March 2021 23:47:21 UTC