- From: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>
- Date: Mon, 23 Aug 2021 14:11:30 +0000
- To: Steve Capell <steve.capell@gmail.com>, Henry Story <henry.story@gmail.com>
- CC: "public-credentials (public-credentials@w3.org)" <public-credentials@w3.org>
- Message-ID: <MWHPR1301MB2094A07B8122F8E86C079179C3C49@MWHPR1301MB2094.namprd13.prod.outlook.>
These are all great examples. Let me explain my motivation for the original question "what existing protocols/platform standards, in your mind, are the most similar to VCs (at a top-level)?"... What I'm looking for is a specification (or group of specifications) that we can model/pattern/structure the "VC Specification" after ...i.e. in a similiar way. Currently, for example, we have the "data model specification", the "use cases" document, an "implementation guide" but, for example, we don't have a top-level document that knits them together (don’t jump on this idea just yet 😊). So with the above motivation, what, in your mind, is a "best in class" specification (or group of specifications) that describe something similar to "a Verifiable Credentials platform as a set of data models and protocols for creating and verifying verifiable data packets and their exchange between 2 or more software agents (don't get hung up on the specific wording)"? Let's give this another kick at the can. Michael -----Original Message----- From: Steve Capell <steve.capell@gmail.com> Sent: August 23, 2021 5:11 AM To: Henry Story <henry.story@gmail.com> Cc: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>; public-credentials (public-credentials@w3.org) <public-credentials@w3.org> Subject: Re: What are VCs similar to? Also a good analogy. Probably depends on your intended audience - a tech audience will most likely understand and appreciate the x.509 analogy - but a business / policy audience will give you a blank stare if you say “it’s just like x.509”. I think the passport chip is a better story for the non tech audience I may venture to suggest that the biggest problem I’ve faced (and probably this group faces) is not convincing tech savvy people - but rather getting business / policy people to understand the benefits to the extent that they will allocate budget to projects so they can realise that benefit I still struggle with this - almost every day Steven Capell Mob: 0410 437854 > On 23 Aug 2021, at 9:03 pm, Henry Story <henry.story@gmail.com<mailto:henry.story@gmail.com>> wrote: > > > >> On 23. Aug 2021, at 11:49, Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net<mailto:mwherman@parallelspace.net>> wrote: >> >> If you assume a simple definition of a Verifiable Credentials platform as a set of data models and protocols for creating and verifying verifiable data packets and their exchange between 2 or more software agents (don't get hung up on the specific wording), what existing protocols/platform standards, in your mind, are the most similar to VCs (at a top-level)? >> - DNS? >> - TCP packets? >> - SOAP messages? >> - something else? > > X509 Certificates (with 40 years of tech improvements added to them). > > A Verifiable Claim is just a signed content, and the big leap of VC > stack is that it is built on well defined, open, extensible logics. > > Henry > >> >> Michael Herman >> >> Get Outlook for Android > >
Received on Monday, 23 August 2021 14:11:48 UTC