• 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

• Blog post https://trustoverip.org/news/2023/12/15/announcing-public-review-of-the-didwebs-method-specification/
  • Public review requires repo access, etc. for non-members to provide their feedback
• ToIP spec template https://github.com/trustoverip/specification-template
  • kudos to ToIP and our TF
  • We will need to adopt the latest changes back into our repo
• Henk van Cann has an M3 mac and will go through the GETTING_STARTED and provide updates to help others.

We discussed how the tree of possibilities in KERI can't cloud the simplest steps. And so the spec needs to be very clear about what is optional/additional and needs to logically build in a way that makes it obvious to the reader where they can stop for their use case.

Guiding the user through KERI features needed for did:webs:

We discussed updates to the diagram here https://github.com/trustoverip/tswg-did-method-webs-specification/pull/124

Catchup on final changes status:

• What needs to be completed to enter the public review process?
  • All public review changes should be well documented so that they can watch the process
    • Normative vs Informative information in the spec is important prior to release https://github.com/trustoverip/tswg-did-method-webs-specification/issues/120
      • Work backwards from the normative statements. Triage informative to minimum.
        • If you start with these bones it's easier to hang all of the minimal informative information and move everything else outside of the spec.
      • Informative that isn't needed in the spec
        • Appendix
        • Implementation guide
        • Explain why in a separate paper
  • Service endpoint section updates
  • KERIpy release candidate https://pypi.org/project/keri/#history
  • How can contributors help?
    • what are the biggest risks, etc.

See the ToIP template, might have ISO influence

• 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