W3C home > Mailing lists > Public > public-credentials@w3.org > March 2022

Re: 2022-2026 Verifiable Data Standards Roadmap [DRAFT]

From: Heather Vescent <heathervescent@gmail.com>
Date: Sun, 20 Mar 2022 11:16:27 -0700
Message-ID: <CA+C6qMw2nebjyZpj_95xPYH4pxa2Cuo9cEMpvEYmnoTZpmJsrw@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
On Fri, Mar 18, 2022 at 5:43 AM Manu Sporny <msporny@digitalbazaar.com>

> On 3/18/22 4:10 AM, Snorre Lothar von Gohren Edwin wrote:
> > to set up a herding group (I know that is probably impossible)
> Not impossible, but it would take volunteers from this community (and
> others)
> to step up to do the work, and that might be more than we can muster at
> this
> point in time.

> That is what I took from Heather's commentary -- it wasn't about building
> silos and walling ourselves off from each other -- it was about being
> pragmatic and working with what we have right now because everyone's time
> is
> limited and precious and, like it or not, we can't address everyone's high
> priority items simultaneously.
> The talent it takes to do this stuff is an extremely limited resource and
> they're focusing on what they think is the most effective use of their
> time.
> At least, that's what I took away from Heather's statements. Heather, did I
> misread the gist of what you wrote?

Yes on being pragmatic. Yes on seeing the reality of the situation and
understanding that people are doing the best they can at each moment. And
realizing that the best one can do at the moment sometimes does not satisfy
the needs of the group, an individual, your commitment, someone's vision of
the ideal way all these things should work.

Welcome to life with other people!

> > The second answer to this question I would say is just be open to
> > collecting, no need to go out and pull information.
> Here are two concrete actions that have been suggested so far that are
> do-able:
> 1. Re-implement the Verifiable Data Roadmap in mermaid.js
>    in an attempt to make it a collaborative document.
> 2. Take pull requests from the owners of particular work
>    items (Editors/Chairs), across organizations, to put
>    items on the roadmap.
> I can do #1 above, #2 would need some sort of committee/maintainer (and I'm
> not volunteering to do that because 1) I don't have those sorts of spare
> cycles -- I'm already weeks behind on the DID Spec Registries duties I
> have,
> and 2) I don't want to be put in a position of saying "No, sorry,
> Centralized-VC-Exchange really shouldn't be on an SSI Roadmap".
> I'll commit to doing #1; it's a solid idea, thank you Snorre.
> #2 will need some set of brave souls that don't mind playing the part of
> villain or doormat.
> -- manu
> --
> Manu Sporny - https://www.linkedin.com/in/manusporny/
> Founder/CEO - Digital Bazaar, Inc.
> News: Digital Bazaar Announces New Case Studies (2021)
> https://www.digitalbazaar.com/

Heather Vescent <http://www.heathervescent.com/>
Co-Chair, Credentials Community Group @W3C
President, The Purple Tornado, Inc <https://thepurpletornado.com/>
Author, The Secret of Spies <https://amzn.to/2GfJpXH>
Author, The Cyber Attack Survival Manual
Author, A Comprehensive Guide to Self Sovereign Identity

@heathervescent <https://twitter.com/heathervescent> | Film Futures
<https://vimeo.com/heathervescent> | Medium
<https://medium.com/@heathervescent/> | LinkedIn
<https://www.linkedin.com/in/heathervescent/> | Future of Security Updates
Received on Sunday, 20 March 2022 18:17:51 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:25:29 UTC