Versions Compared

Key

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

...

TimeAgenda ItemLeadNotes
3 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
  • 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.
  • New Members:
5 minGeneral announcementsAll

Any news and updates of general interest to CTWG members

  • -
2 minReview of previous action itemsChairs
  •  ACTION: Drummond Reed and/or Judith Fleenor to arrange that the EasyCLA issue gets sorted for the entire TOIP context. The issue is that EasyCLA prevents github actions to merge generated code into main/master. Consult Brian Richter as needed.
  •  ACTION: Drummond Reed to send out a request to the All-Member mailing list requesting volunteer assistance for converting  "Decentralized SSI Governance" into a ToIP template to publish it as a white paper.
5 minVolunteers for the Decentralized SSI Governance white paper conversion

We had five potential volunteers respond to the call for volunteers above. Plus one ToIP member who had issues with the content of the paper.

How should we proceed?

5 minUpdate on EasyCLA issue
5 minUpdate on TEv2 progress

Brian Richter has hired another person that will help him out on the work.

@chadha is still having some trouble with integration, but the TRRT seems to work.

We have labeled MRG issues with prio=high that need to be done first, prio=medium that need to be done next. There are some feature requests that have not been prioritized. Overall prio is to get the long-term tools up and running, so minimal effort will be spent on fixing stuff that will be phased out (dhh's tools). After MRGT, Brian will work on HRGT, and we expect TRRT will be ready when HRGT Is. 

30 minMental Model Development Process

In our last meeting, Rieks suggested the following steps in the development of a mental model:

  1. Start writing the spec and mark every term that needs a definition.
  2. Document each noted term by supplying a first criterion by which the members of the task force can determine if an instance is an example of the term. For example, throw a number of use cases at it, and see if the criterion works. If it doesn't, find the criterion that does.
  3. Document these discussions so you end up with a little document for each term that not only provides a definition, but gives readers an understanding of the criterion that were used and why.
  4. Once you have agreement, you return to the specification document and revise it to incorporate the terms based on the the new definitions and criteria.
  5. When you find that the terms all relate to each other in a clear way, then you have a mental model you can draw and document.

Drummond and Neil are wondering about the best way to go about this process prior to starting to draft the specification. In other words, how can we at least start building a mental model during stages 1 thru 6 of the development stages in this table before we get to the spec drafting stage (recognizing that the mental model will be further improved during the Working Draft stage)?


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

...