owned this note   changed 4 years ago  
Linked with GitHub

Comparison

This is a working Document

Protocol

Goal: Define interactions beween parties for a specific purpose

  • identified by name only
  • Support embodied in code.
  • defines messages and semantic meaning

Machine Readable Governance Framework

Goal: Provide information about roots of trust.

https://github.com/hyperledger/aries-rfcs/blob/82ace6001f97552f05d3da5472bcf9dbf7726a05/concepts/0430-machine-readable-governance-frameworks/README.md

  • identified and retrieved by URI
  • code must support readable format, but can otherwise use any document.
  • contains references to:
    • schemas
    • issuers (DIDs)
    • verifiers (DIDs)
  • can be used to cache info for offline purposes

Thoughts:

  • Needs a better name?
  • Need updated/new RFCs about current practices

Interaction Documents

Goal: Provide template for scripted interaction

  • identified and retrieved by URI?
  • indicates protocols and values within protocols to use
  • threads protocols together
  • "this happens, then this happens"
    • example: driver verifies the cop, cop then verifies the driver

Mike's Areas of Governance

  1. Who to trust (issuers, verifiers, schemas)
  2. Rules - permission, prerequistes, requirements
  3. Workflows - who does what when
  4. Trust Registries - discovery of governance/issuers etc. which governance to trust.
Select a repo