Summary

• Accessing "resources" via DID resolution - Drummond
• Serialization formats - use JSON?
• A "close to finished" DID Method Specification?

Recording from the call: 

Welcome and Introductions

Announcements

Attendees

• Stephen Curran
• Dan Gisolfi

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)

• Serialization formats

This Week's Discussion:

• Resolving DIDs to get a resource
  
  • Naming of non-NYMs to include the namespace
• The "close-to-finished" DID Method Spec – please review
  • At risk – DNR/DND
• Include in document that DIDDocs are JSON-LD
  • Three serialization formats in the DID Core spec – let's go with 1 to reduce interop and implementation effort.
  • Daniel Hardmanwants to discuss this further, so that we consider JSON.

Future Discussions:

• Other Indy Ledger Objects as DIDs (e.g. schema, etc):
  • Drummonds proposal: https://docs.google.com/document/d/1f99z4Bf8F-DA8EbkNjInVQv2ncJGPwF_Dp7I7Mfyhqs/edit
  • Other options:
    • Use the `@context` to indicate what type of Indy object is being referenced.
    • Use a GET_DID transaction that uses the local identifier for the different objects and the ledger figures out the doc type and returns the appropriate result – e.g. a SCHEMA, CLAIM_DEF, etc.  The existing transactions remain and are used if the client wants.  The GET_DID can also be used to return a NYM.
      • STATE_PROOF comes back in the reply as currently done.
  • Existing transactions?
• Handling existing objects on the ledger as DIDDocs?
• DNR and DND discussions
  • To find networks we will require at least the first and perhaps the second of these approaches, while the rest are suggested:
    • Config files for one or more known networks
    • A mechanism for a ledger operator to register discovery information for other ledgers (aka "human gossip")
      • A DID/DIDDoc on a ledger will contain cross-registry information
      • A mechanism is needed for finding the DID(s) that contain the registrations – ideas have been put forward - a DID Name Directory (DND) is the likely approach.
      • Document about the DND and DNR records
    • Decentralized registries based on verifiable credentials
    • Other registry mechanisms, such as the DDNR proposal
    • The DID Method Spec will include a reference to a repo (likely) "indy-did-networks" within Hyperledger that will be a lightly managed, structured repository of folders per Indy network with at least the config file(s) for the networks. Use of the repo is voluntary, but provides a convenient way for networks to publish information about the network. Maintainers will be selected from the community and should exhibit a light hand in accepting PRs, being concerned mainly with structure of the data (not content) and that contributors are not being malicious about updating the information of other network operators. The Hyperledger governance structure may be used for disputes as appropriate. This is not a replacement for the Governance that a specific network should implement.