You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

We are going to have two tracks to the conference:

  • The primary track will be a sequence of discussions that will follow the path we expect will be selected to accomplish the goal of the conference. On that expected path, there are a number of technical decisions to be made, discussions to be had, trade-offs to be explored and (as best we can) a backlog of technical work to be defined (and assigned!!).
  • The secondary track will be a series of presentations/discussions on topics related to the user story that we are trying to accomplish, but that are not part of the immediate changes we expect to be making. Think of this as the “unconference” part of the Interop-athon. If ideas come from the secondary track sessions that could or should alter the expected path, we’ll make that happen.

For both tracks, we need experts/facilitators on the topics to lead the sessions and we welcome volunteers for each session. For the primary track sessions, you’ll be stuck with me (Stephen Curran) as the default facilitator, but I’ll be more than happy to let others lead sessions they are interested in--please let me know. For the secondary tracks, there must be a volunteer to lead each session.

Primary Track:

  • One DID Method to rule them all
    • Namespacing — before or after the second “:”?
    • Writing/evolving the DID Method Specification (current did:sov method)
    • Governance of the DID Method specification
  • Finding network metadata — genesis files, governance framework, etc.
    • A registry?  Governed by whom?
    • Ideas: GitHub, .well-known, others...
  • DID and ledger object references in data structures (credential, proof, etc.)
  • Storing DID and ledger object references (Aries storage, Indy wallet)
  • What changes to make where?
    • Indy Node
    • Indy SDK
    • Indy VDR, Aries Storage
    • Aries Frameworks
  • Who is going to make the changes and when?


Secondary Track (Proposed):

  • KERI and Indy - Dr. Sam Smith
  • DIDDocs on Indy - ??
    • Using DID standard DIDDocs on Indy
  • A Vision for Interoperable Schema - Robert Mitwicki
  • Indy Plug-Ins and Interoperability - ??
    • What could the impact be of different networks running different plugins?
  • The State of Indy Networks - ?? (suggest multiple)
  • The impact of BBS+ on Indy - ??
    • To have or not have JSON-LD contexts on the ledger
  • Off ledger revocation registries? - ??
    • The pros and cons of on and off ledger registries
  • Other things we need in Indy - ??
    • Open forum to collect most wanted features

Tuesday - Day 1

  • Hour 1: Introductions, goals and process
  • Hour 2-3: Technical Session: Broadening the solution space
  • Hour 4: Break
  • Hour 5: Summary of Morning; Planning Breakouts
  • Hour 6-7: Breakout Sessions on elements of the solution space
  • Hour 8: Wrap-up Discussion/Days

Wednesday - Day 2

  • Hour 1: Summary of Day 1, process for Day 2
  • Hour 2-3: Technical Session: Shrinking the solution space
  • Hour 4: Break
  • Hour 5: Summary of Morning; What's decided, where do we need to focus?
  • Hour 6-7: Breakout Sessions on planning and documenting the work to be done
  • Hour 8: Wrap-up discussion:
    • What needs to be done?
    • Who is going to do the work?
    • What open questions remain?


  • No labels