• Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.

• Tech stack WG has a new mailing list for the new charter. This is part of the acceptance of the new IP, etc. Open Web Foundation licensing.

  • • https://lists.trustoverip.org/g/technology-stack-wg-2

      Scroll to the Bottom
      Click Green Button to log-in to the mailing list
      Then Click Blue Button to +Join the list

• New Members: 

• Current work

  • Spec repo is here https://github.com/trustoverip/tswg-did-method-webs-specification
    • Registered in the did registry here https://w3c.github.io/did-spec-registries/#did-methods
  • Reference implementation is here https://github.com/hyperledger-labs/did-webs-resolver

• 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
• Upgraded the python reference impl to KERI 1.1.4

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 further validate the spec
  • This should be socialized that more implementations are needed as a next step that we would like to help support

Visit the "decentralized diagrams/images directory" and the description of the totally automated approach of metadata gathering. Feel free to add comments.

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:
3.  1. ? Are there any other automatically derivable reputational scores?
4. 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?
  • Whois PR
  • Normative/Informative
  • Service endpoint section updates
  • KERIpy release candidate https://pypi.org/project/keri/#history

• Todos and missing information sections need to be addressed today
  • Milestone for 1.0 https://github.com/trustoverip/tswg-did-method-webs-specification/milestone/2
• Reivew current state of hyperledger-labs did:webs reference implementation https://github.com/hyperledger-labs/did-webs-resolver 
• Open PRs and Issues
  • https://github.com/trustoverip/tswg-did-method-webs-specification/issues
  • https://github.com/trustoverip/tswg-did-method-webs-specification/pulls