• 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

Catchup on final changes status:

• Diagraming in ToIP
  • An index of diagrams would help
    • a markdown table that provides metadata/context that allows for the community to determine the usefulness/reputation of the diagram.
    • Lets start with KERISSE (at least for KERI related diagrams?). Perhaps this will expand to the wider ToIP ecosystem.
      • Broken links checker is automated and will help us maintain.
      • Medium articles can be scraped as well.
  • Diagrams should be close to their origin (ie. in the repo it applies to) but linking can lead to drill-down, discovery, and more
    • Discussions on the diagram occur within the repo. It may prompt discussion at a higher level (repo), etc.
  • Needs to be very dynamic, PRs etc. will result in updates, removal, etc.
  • Some are informational, some map a spec, some are future ideas, etc.
  • A decentralized model is necessary in order to maintain what diagrams are important, useful, out-of-date
• 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
• 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

•  Lance Byrd will update the spec version and add a section asking for additional reference implementations to exercise and improve the spec and to show interop with our python hyperledger-labs reference impl
•  Lance Byrd will cleanup co-chair lists
•  Lance Byrd will define the minimal interoperability profile for did:webs spec.... then we can define additional profiles that include the optional/nice-to-have features like whois .
•  Take a look at Ed's diagram https://github.com/trustoverip/tswg-acdc-specification/issues/77 to discuss (quickly) next week.
•  Henk van Cann and Kor Dwarshuis will work on the KERISSE-engine maintained diagrams & images list:
  

  1. metadata table pointing to (URLs) - and describing images and diagrams with addition options (reputation, level, status, etc.)
  2. a search option in KERISSE with only images, based on a scrape-function Kor has already written: getTextAroundImage
  3. the broken link checker reports every Monday that the images are still out there