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

Who should lead the heavy lift to coordinate across the various ecosystems?
CCG? The other areas? Where are the efforts to coordinate with CCG from
these other silos? CCG has been open to collaborating on these kinds of
maps, but to expect CCG to lead the tracking of efforts of work done
outside the CCG is a bit much, especially if they have limited
interaction/contribution to the CCG. I would appreciate more overlap and
coordination, but the effort to collaborate must come from both/all sides.

The unfortunate truth is that our various orgs are honestly focused on
their individual efforts. The people that participate in multiple orgs are
the ones that do the knowledge sharing and collaboration. It's ad hoc at
best. I don't think it's intentional to build silos, but there is limited
incentive to collaborate more broadly, because if there was, we'd already
be doing it. I think the best we can do is not let our feathers get ruffled
when one of the silos is doing their own thing that may or not dovetail or
support another orgs activities. The solution to that scenario, jump in and
participate in the orgs you want to lower the silo barriers. Or I guess
take the lead on creating the coordinating ecosystem map and have everyone
sign off on it.

-Heather

On Wed, Mar 16, 2022 at 8:02 AM Phillip D. Long <phil@rhzconsulting.com>
wrote:

> Manu - it does lead to multiple questions. But we can’t strive for
> perfection, just somewhat greater clarity
>
> Should we point out technologies that are competitive with one another
> and/or
> largely overlap in functionality?
>
>
> Yes, that would be very helpful as it gives us a chance to see how they
> overlap and perhaps understand their differences better.
>
>  There are at least three VC exchange protocols in play right now.
>
>
> I’m sure many are wondering why there are three approaches. And I’m sure
> there are points of optimization that are focusing on particular use cases
> coming for distinct verticals.  Getting that out there for all to see just
> might lead to consolidation, or at least better opportunities for those
> implementing to make decisions about their choices for protocols to support.
>
> There are 68 Aries RFCs... do we list all of them? Only the active ones?
>
>
> The Hyperledger community is very diverse. With that many options among
> RFCs, even only the active ones might be a challenge. If there are only a
> few relevant active ones, then yes, including them would be helpful. But
> it’s also an opportunity to send a note to the RFC authors saying here’s
> short, concise format to describe your work we’d like to include in the
> comprehensive roadmap. If they respond great! If not just listing an
> addendum of who was sought out and failed to respond is useful, as well.
>
> Do we list vocabularies? Privately developed ones? How do we choose?
>
>
> It’s the CCG’s roadmap. We get to choose. Start with what the CCG is using
> and ask for volunteers to describe the others they thing should be included
> perhaps?
>
> I don't for a minute fail to recognize it’s a seriously large task to pull
> something like this off. But inviting others outside of the CCG who are
> doing work in the space and giving them an format for contributing that is
> simple enough to undertake and return, but sufficient to at least give a
> sense for how their work fits into the larger picture is a variant of the
> chunking the tasks up into digestible bites that might contribute value.
>
> Just some thoughts.
>
>
> *Phillip D. Long*
> *e: *pdlong2@asu.edu
> Adaptive Learning Library Consultant
> *org:* EdPlus/ASU
> https://edplus.asu.edu/what-we-do/orchard-adaptive-learning-experience
> *SNS:* https://www.linkedin.com/in/longpd
> <https://edplus.asu.edu/what-we-do/orchard-adaptive-learning-experience>
>
>
>
>
>
>
>
> On Mar 16, 2022, at 10:26 AM, Manu Sporny <msporny@digitalbazaar.com>
> wrote:
>
> On 3/16/22 10:13 AM, Snorre Lothar von Gohren Edwin wrote:
>
> No one benefits from working in silos in this space, so I support a wider
> ecosystem roadmap with labels/marks.
>
>
> ... which then begs multiple questions:
>
> Should we point out technologies that are competitive with one another
> and/or
> largely overlap in functionality?
>
> For example: There are at least three VC exchange protocols in play right
> now.
>
> There are 68 Aries RFCs... do we list all of them? Only the active ones?
>
> Do we list vocabularies? Privately developed ones? How do we choose?
>
> -- manu
>
> --
> Manu Sporny -
> https://urldefense.com/v3/__https://www.linkedin.com/in/manusporny/__;!!IKRxdwAv5BmarQ!P6zGpIbi84WMClNMdwWAOFGKP0xPG8v-ADD-taL976tOfvqkRsLstMgXC48UN2k$
> Founder/CEO - Digital Bazaar, Inc.
> News: Digital Bazaar Announces New Case Studies (2021)
>
> https://urldefense.com/v3/__https://www.digitalbazaar.com/__;!!IKRxdwAv5BmarQ!P6zGpIbi84WMClNMdwWAOFGKP0xPG8v-ADD-taL976tOfvqkRsLstMgXF6CzRpk$
>
>
>
>

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

@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
<https://app.convertkit.com/landing_pages/325779/>