Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeAgenda ItemLeadNotes
5 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
5 minsReview of action items from previous meetingChairs
  •  Lance Byrd will continue to pull informative info into implementors guide section PR
5 minsAnnouncementsTF Leads
5 mins

Reports

Open
  • Charles Lanahan is walking through the CESR spec and has been providing PRs/Issues for the spec as he implements a CESR parser.
    • Elixir impl
  • Henk van Cann Setting diagrams directory on WebOfTrust
    • Diagram-list wrap up:
      Decision after a round of initial listing: We have to invent a minimal effort version of the diagram - list

      Simple rules:
          •    Your repo is on trustoverip
          •    Your diagram is in /diagrams
          •    Decentralized approach referencing the diagrams
          •    Prevent copies

  • Cole Davis Switchchord went live. Resulted in lots of activity across multiple industries.
    • Many implications in the royalty business requiring strong identity related tech
    • Big opportunity for growth
25 minsDiscussionOpen

Catchup on final changes status:

  • Implementors draft, to get multiple implementations to verify the steps
    • Quality check on the spec
    • Should be able to show interop between implementations
    • This allows us to enter 'final' public review
    • This should be socialized that more implementations are needed as a next step that we would like to help support

The "decentralized diagrams/images directory" and the totally automated approach of metadata gathering:

  1. Input: We've defined a definition of a diagram: an image that resides on one of the weboftrust or trustoverip repos. We've defined a reference to a diagram: a URL to a source that resides on one of weboftrust or trustoverip user accounts. We reckoned that a diagram with a reference on the github page or elsewhere of its own repo is a strong commitment to its status (reputation of the diagram, if you will).We reckoned that a reference to diagram on any other github page of the group of repos that together form the "decentralized diagrams/images directory" is also a strong statement to its reputation. We grab the text around all references to a certain diagram to offer context about how it's used.
  2. Question to be discussed: are we going the right direction with 1. ? Are there any other automatically derivable reputational scores?
  3. Request for input: what are the repos that belong to the group and could you point us (path!) to valuable image sources under each of these repos?
    • The (intensity of the) orange columns ( row 1+2) of this prototype metadata of diagrams and images to be processed says how likely it'll be that we can automatically derive the data from the repos (example: column 'commit hash') versus the need to manually input afterwards (example: column 'level') (edited) 
  • Separating the admin control from did:web, to provide separate signing control is a big step.
    • Wording this in a way that helps those outside our community to understand/appreciate that step is extremely valuable.
  • What needs to be completed to enter the public review process?
5 minsAny other businessOpen


5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs


...