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

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 <mailto:pdlong2@asu.edu>
Adaptive Learning Library Consultant
org: EdPlus/ASU
https://edplus.asu.edu/what-we-do/orchard-adaptive-learning-experience <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 <mailto: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$ <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$ <https://urldefense.com/v3/__https://www.digitalbazaar.com/__;!!IKRxdwAv5BmarQ!P6zGpIbi84WMClNMdwWAOFGKP0xPG8v-ADD-taL976tOfvqkRsLstMgXF6CzRpk$> 
> 
>