A ranging discussion on state of the project, for which was discussed as input to....
How does ToIP Tech Arch get from here (Dec 1) to Interop in 18 to 24 months?
Observations:
- SSI in transition. Tough to know which existing tech, or in-development tech, to bet on for building ToIP Tech Arch interop in 12-24 months
- Tough for devs/teams switching tech or joining ToIP to know where to start.
- For bleeding edge ToIP tech, it’s hard to keep up, as dev teams focus is “do” vs “explain”
- ToIP stack + new tech changing SSI, but in transition:
- Some dev on new tech, some developing on existing, planning for transition to new “in the future”
- Cooptition reality - existing tech vendors promoting their variation, but that may not be the future.
- e.g., KERI vs 100++ DID Methods, DID Auth
- Is there an identified list of prioritized tech “gaps” and/or do we need one?
- Does VC interop (including within the same VC ecosystem (e.g., travel, health)) have a road map?
- Naive perception - same-old resistance to “anyone else’s ‘standard’”
- Potentially insurmountable semantic differences (e.g,, VCs are sufficiently different the information isn't compatible)
- Top reason ToIP Interop with fail?
Suggestions:
- Need to start an Interop immediately, which is continually updated.
- There will likely be multiple paths, but that’s OK
- Need a Use Case driven development priorities roadmap, starting with a “base” use case the framework as a whole, plus independent areas that can be worked in parallel (e.g., Trust Registries, DIDAuth, …)
- This constantly evolves and reprioritizes as needed
- Needed for both bleeding edge dev teams and “fast followers” looking to learn/build ASAP
- Need pragmatic “how to get up to speed” guides, pre-built dev sandboxes to get started
- For new dev on existing tech (whether as future or as “test mules”)
- Capture what dev orgs/vendors have ToIP-compatible “dev sandboxes”
- Encourage dev orgs/vendors to build future sandboxes
- Need explainers to follow bleeding edge work to build the “how to” guides and cooperation from devs to “explain to the explainers”
Andor Kesselman added the following post-meeting:
Create a “Decentralized Identity and Trust Ecosystem Onboarding TF”, with the following goals:
- Build a model around ssi adoption strategies and implementation.
- Identify friction in the current ecosystem to onboard.
- Spark new initiatives to help address #2.
A possible deliverable from this group might be a guide to onboarding into SSI