- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Tue, 31 Dec 2024 10:37:03 -0500
- To: public-vc-edu@w3.org
- Cc: Kerri Lemoie <klemoie@mit.edu>, Nate Otto <nate@ottonomy.net>, "Phillip D. Long" <phil@rhzconsulting.com>, Kate Giovacchini <kate.giovacchini@asu.edu>, Taylor Kendal <taylor@learningeconomy.io>, Ian Davidson <ian@idatafy.com>, chris purifoy <chris@learningeconomy.io>
On Mon, Dec 30, 2024 at 5:20 PM Ian Davidson <ian@idatafy.com> wrote: > Kate's suggestion was to call the category "Credential Management" and then have some of the sub-categories described as wallets. Yes, IMHO, that is exactly the right level of abstraction for this class of tools. We've struggled in non-EDU market verticals to explain that "Your app/website can provide credential management functionality." only to be met with "Yeah, but our app/website isn't a digital wallet." -- I think we've leaned into the "digital wallet" terminology too heavily over the past several years. It was useful to get people to understand use cases that had an analog to a physical wallet, but is a challenging analogy when you have something that doesn't necessarily fit into a physical wallet (like an OpenBadge or LER). Additionally, the capability that W3C VCs can be printed on a piece of paper or embedded in a PDF as a verifiable QR Code further strains the "digital wallet" analogy. We do call these things "Credential Repositories" in the current spec: https://w3c.github.io/vc-data-model/#dfn-credential-repositories ... but I like "credential manager" better. Should we update the term to something like "credential manager" or "credential management software" in the current specification? It would be a fairly easy editorial change. "Credential Management" applications, websites, and tooling feels like a good direction. -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. https://www.digitalbazaar.com/
Received on Tuesday, 31 December 2024 15:37:43 UTC