Versions Compared

Key

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

...

  • The CTWG meets bi-weekly on Mondays at 10:00-11:00 PT / 18:00-19:00 UTC. See the ToIP Calendar for the full schedule.

Zoom Meeting Recording

...

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: none.
5 minGeneral announcementsAll

Any news and updates of general interest to CTWG members

  • Rieks Joosten said that criteria-application process is familiar to lawyers because that is how the law is applied. So they have a good operational reason for lawyers to be specific about terminology. Also, different laws can define terms differently. So the law is what we call a scope. The same is true of software engineers, where a namespace is a scope. Also, the semantics people use schemas to define their scope. All of these contexts have analogous ways of dealing with applying criteria to define terminology.
  • Rieks also talked about the EU Data Spaces Support Center (DSSC) coalition's work on terminology. It starts with conceptualization, which begins with understanding the criteria that defines what is and is not an instance of a concept. Then a term can be assigned to the concept. So each glossary consists of a term plus the criteria for distinguishing instances of the term. Everything else is explanatory text. In some cases, this can be enhanced with conceptual models aka mental models.
  • Neil Thomson asked where the "explanatory texts" should go? Rieks suggested they should go into a repository such as a GitHub repo.
    • One other option might be a Confluence "space".
    • The key criteria is to be able to link to the explanatory text documents.
    • Drummond Reed suggested that using Markdown files stored in the same GitHub repo as a terms wiki (and published glossary documents) should be the default choice.
    • Neil also pointed out that if GitHub repos are used for explanatory texts and mental model diagrams, then it will be easy to version.

DECISION: The CTWG will recommend that terms communities store explanatory texts and mental models as Markdown documents or PDFs in the same repo as their terms wiki.

2 minReview of previous action itemsChairs
    • Nicky's draft post is here.

ACTION: Drummond Reed to send Judith Fleenor the final Word doc and PDF of the Decentralized SSI Governance white paper.

  •  ACTION: Drummond Reed to thank all the volunteers for the above.
  •  ACTION: Drummond Reed and Neil Thomson to work out a process to start the Trust Registry TF and Trust Spanning Protocol TF on the process of creating a mental model for the terms needed in their respective specifications.
10 minUpdate on TEv2 progress

Brian reported that they are making progress. Ryan is awaiting invites.

Judith clarified that Ryan should need developer write access.

They are currently looking at the MRG bugs in order to get it running.

Brian has been posting questions to Slack. 

They are also working on the ingress tool.

Rieks Joosten offered to chat with Brian and Ryan in Slack to answer their questions.

10 minGitHub maintenanceHenk van Cann 

Henk would like to check on how we are handling GitHub repo maintenance.

Henk published this document describing the scope of the problem he has encountered and potential solutions.

We had a long discussion about this issue as it has been a continuing sore spot in our work — and it affects multiple ToIP WGs and TFs.

Henk believes we are going to need to devote budget to part-time paid resources. Drummond tends to agree, but also suggested such resources may be contributed by ToIP member companies who have GitHub experts on staff.

ACTION: Judith Fleenor, Henk van Cann, and Andor to develop recommendations for sustainable GitHub maintenance, including definitions of the skills and roles needed and how a ToIP GitHub Support Group should be formed and maintained.

15 minUpdate on Technology Stack WG Glossary progress

See this Glossary Workspace that Drummond has set up. The goal is to populate it with all the terms the Technology Stack WG task forces are currently discussing as a step towards both filling out the glossary and developing one or more mental models.

Rieks Joosten shared that if the stakeholders in these glossaries don't use the right process, they will do much extra work. His point is not the definitions that matter, but it is the stakeholder's conceptualizations that matter. So it is first understanding one another that is the most important.

10 minMental Models Task Force

Revisit whether we are ready to launch the MMTF. See this proposed charter. The TSWG glossary work may be a good opportunity to finally launch this effort.

We ran out of time to discuss this in any depth.

ACTION: Drummond Reed to put the Mental Models Task Force on the agenda for the next meeting.

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

Screenshots/Diagrams (numbered for reference in notes above)

#1


Decisions

  • DECISION: The CTWG will recommend that terms communities store explanatory texts and mental models as Markdown documents or PDFs in the same repo as their terms wiki.

...

  •  ACTION: Drummond Reed to send Judith Fleenor the final Word doc and PDF of the Decentralized SSI Governance white paper.
  •  ACTION: Judith Fleenor, Henk van Cann, and Andor to develop recommendations for sustainable GitHub maintenance, including definitions of the skills and roles needed and how a ToIP GitHub Support Group should be formed and maintained.
  •  ACTION: Drummond Reed to put the Mental Models Task Force on the agenda for the next meeting.