Meeting Date

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

Zoom Meeting Recording

Attendees

Main Goals of this Meeting

1) Introduce Brian Richter as a potential new Terminology Toolbox 2.0 developer, 2) attend to Nicky Hickman's linking questions, 3) discuss the development plan for terms wikis and glossaries needed for the ToIP Technology Architecture Specification V1.0 and ToIP Governance Architecture Specification V1.0.

Agenda Items and Notes (including all relevant links)

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:
    • Brian Richter attended Internet Identity Workshop last week (and the previous one last spring). He is working on putting together a hackathon of folks working in the SSI space. He's been in the space for ~2 years now. He first started issuing credentials into the BC Gov OrgBook. His company built a POC for how companies can issue/use licensing credentials. Brian is based in Victoria BC. He heard more about CTWG at IIW and is interested. 
5 minGeneral announcementsAll

Any news and updates of general interest to CTWG members

  • Neil shared that he's seeing a need to start from English language terms for commonly-used SSI terms such as "integrity". So we should start with those "root" definitions and then specialize from there. We can then note when there are multiple meanings of a term that apply.
    • Drummond noted that a root term could be automatically linked to specialized uses of the term provided that those specialized uses end in the same root term.
    • This could also apply to synonyms.
    • Nicky pointed out that if the goal is "a common understanding of a term", then when there are multiple uses/meanings of a term, it may need to be resolved by a mental model.
2 minReview of previous action itemsChairs
  • ACTION: Drummond Reed to check with Judith Fleenor about resources on hiring additional resources/budgets in order to complete the Terminology Toolbox 2.0 functionality.
  • ACTION: Drummond Reed to offer a meeting on terminology and mental models to the ToIP Technology Architecture V1.0 Spec Editors team.
20 minDiscuss Terminology Toolbox 2.0 bounty with Brian Richter

Review current state of Terminology Toolbox 2.0 development, including the Machine-Readable Glossary Implementation Notes from Sid Haniff, and what Brian might be able to do under the planned bounty.

  • We discussed that mental models that explain a group of terms should ideally be stored in a GitHub Markdown document in one of the associated terms wikis.
  • We discussed the "headline features" of Terminology Toolbox 2.0:
    • Auto-markup of GitHub Markdown documents.
    • Auto-generation of multi-source glossaries based on:
      • Terms wikis as a whole
      • Terms wikis filtered by a tag (which includes tags for a mental model)

ACTION: Drummond Reed to introduce Brian Richter to Rieks Joosten via email or Slack so Rieks can explain the scope of the Terminology Toolbox 2.0 work.

10 minAnswer Nicky Hickman's glossary linking questions

From Nicky's question in the CTWG Slack channel:

I am just setting forth to do the terms wiki for the harms paper.  I am confused about what I should be doing for links.  This type [agent](agent@essiflab), just creates a new page for you to fill out because it cannot resolve. This type [digital data](https://trustoverip.github.io/essiflab/glossary.html#digital-data) resolves to a deprecated url so all of these now need to be replaced in Yoma for example.  What form of links should I use?

  • Nicky explained the challenges she had been running into; in particular that the glossary generator is not picking up new terms in the HXWG terms wiki.
  • For the time being, she is going to use the long form of the links.
  • The sooner we have the Terminology Toolbox 2.0 tooling, the sooner we can leverage them.
15 minPlanning for usage of Terminology Toolbox 2.0

The first public review draft of the ToIP Technology Architecture V1.0 Specification has been released. Now we need to plan for the work needed to fully incorporate glossary links (and ideally popups) in the second public review draft. (And also in the ToIP Governance Architecture Specification V1.0, which still needs its glossary work completed).

  • We ran out of time to discuss this topic in any depth, but Drummond noted that the sooner the Terminology Toolbox 2.0 is ready, the sooner both of these specifications can have fully linked glossaries.
5 mins
  • Review decisions/action items
  • Planning for next meeting 
ChairsOur next meeting is in two weeks; ideally by then Rieks and Brian will have connected and we can discuss the Terminology Toolbox 2.0 SOW.

Decisions

  • None.

Action Items

  • ACTION: Drummond Reed to offer a meeting on terminology and mental models to the ToIP Technology Architecture V1.0 Spec Editors team.
  • ACTION: Drummond Reed to introduce Brian Richter to Rieks Joosten via email or Slack so Rieks can explain the scope of the Terminology Toolbox 2.0 work.


  • No labels