Summary

• Summary of close-to-done Spec.
• To Do's going forward

Recording from the call: 20210504 Indy DID Method Specification Call Recording

Welcome and Introductions

Announcements

Attendees

• Stephen Curran

Collaboration Channels

• Current hackmd document 
• indy-did-method on RocketChat - https://chat.hyperledger.org/channel/indy-did-method
• indy-did-method repo: ReSpec vs. SpecUp

Agreed Upon:

• See HackMD Document for most of what we have discussed

Online Discussion (from RocketChat this week)

This Week's Discussion:

• Notes and Help Wanted from another pass over the hackmd Spec:
  • Help Wanted: Wording of the "namespace" section, with primary and secondary components.
  • Question: Current verkey change does NOT require signature of a new verkey. Should it?
  • Question: Will it be easy/possible to do "versionTime" query for a DID?
  • Question: Should a "versionId" query require the seqNo be for a NYM, or should it search back on ledger for value of NYM at that time – same as "versionTime"?
  • Question: The new Claim Def DID URL does NOT include the ID of the Schema. That means that you can't have the same named Claim Def using two different Schema. Is that a problem?
    • Nice to have: Analysis of Sovrin MainNet and Sovrin StagingNet to see how many instances of that exist.
  • Question: DID URL Handling for Rev Reg Entries
    • Does not use a straight, request object/return object as with other objects. Instead, may use the RevRegDelta Txn.
    • Good idea?
  • Help Wanted: Security Considerations sections
  • Help Wanted: Privacy Considerations sections
• To Do:
  • HackMD Cleanup – another pass
  • Requirements from the DID Core Spec. – 8.1, 8.2, 8.3
  • Convert to SpecUp and publish
  • Create an Indy HIPE that points to the spec.
  • Define the backlog of tasks:
    • indy-node (assuming there is no indy-plenum work)
    • indy-sdk and indy-vdr
    • universal resolver image

Future Discussions: