2023-10-23 CTWG Meeting Notes
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 Link / Recording
Attendees
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
3 min |
| Chairs |
|
5 min | General announcements | All | Any news and updates of general interest to CTWG members
|
2 min | Review of previous action items | Chairs |
|
15 min | Review of Internet Identity Workshop session on the ToIP Glossary | From Slack: As promised, Brian and I held a session on the last day of IIW called “ToIP Glossary”. We had about 20 attendees. The first half of the session I spent showing the public ToIP Glossary Google doc, which Nicky Hickman and I finished upgrading from the earlier “dictionary” approach (allowing multiple definitions per term) to a strict glossary structure (one definition per term — although when we had more than one definition for a term, we kept the others as “supporting definitions”. It now has ~350 terms, roughly 8% of which are acronyms. The second half of the session was Brian showing his code for the TEv2 engine. Drummond Reed re-tracked the process for the transforming the workspace from dictionary to glossary. Now >350 terms. Henk van Cann commented that >500 terms in the KERI glossary hope to use tools to do it, expect common terms to have different meanings - aim would be to automatically link and relate to it. Using Google Sheet to add metadata to glossary we have - ie Github wiki method on our own repo. Have human friendly tools to make it relevant to the user (e.g. beginner might filter out more complex terms) In the KERI Suite glossary we use an intermediate datasheet to add metadata to the terms: Rieks Joosten you are considering and comparing terms, e.g. if using different criteria then may have same term for different concepts, comparing between scopes enables you to learn a lot because it tells you about how the different communities conceptualise the world. We can progress this in different ways 1) Daniel Hardman 's work, now progressing with Brian Richter 's work to go to V2 1) Ingress tool ingests texts to convert to 'curated texts', currently debating limits of what we can ask humans to do. So considering a few wiki pages that could be on your own repo, so that we could play around with wiki pages to see how they could be converted to curated texts and from there we can create the glossaries 2) creating human readable glossary tool. TEV2 also has ambition to create both a glossary and a dictionary. Vision is that we will have a machine readable dictionary tool where you could pick and choose terms from different scopes. Still unfunded and tech requirements analysis needs doing. Should not be too hard. In machine readable glossary tool we can already pick terms from different scopes and human readable version could do the same thing. This configurable quality for each entry suggests these comparisons could be easy to make. If you want to compare terms in a different group tags (relates to mental models ) and use this as a selection criteria. Henk van Cann like the grouping, ability to filter according to scope, own mental model - could create a defined glossary for a specific goal / vs scope. Want to be able to move quickly. Drummond Reed I think it would be a fantastic project to: a) identify the common terms between the ToIP Glossary and the KERI Glossary, b) see where we agree on the definitions (i.e., use the same criteria) and where we don’t, and c) decide how we want to deal with the exceptions. Nicky Hickman agrees, the key here is the insights that you get from understanding the world view / the epistemological insights. Drummond Reed I like the idea of explicit group tags that indicate scope. I can see the value of doing that within the ToIP Glossary right now (e.g., #beginner, #security, #governance, #specifications, etc.) | |
10 min | Review of next steps for TEv2 tooling | Brian reported that he and Rieks have had several calls since the IIW session. There are a few more tasks that Brian needs to complete on the ingress side. On the human-readable glossary side, there is not too much more to do. Markdown and images are on the list. Overall, there is a pretty good plan going forward. ACTION: Brian Richter and Rieks Joosten to proceed with TEv2 tooling development and report at the next meeting. | |
10 min | Review of ToIP Glossary cluster terms & potential for mental models | All | Drummond Reed pointed out the cluster terms he added to the ToIP Glossary Workspace document. This had two purposes:
|
10 min | ToIP community review of the ToIP Glossary | All | Drummond Reed asked: How should we proceed with review of the ToIP Glossary within other ToIP Working Group and Task Forces? The sense of the group was that we should visit individual WG's and TF's and ask the following questions: 1. What do YOU NEED from our glossary work? 2. Are your key terms in here and are the definitions 'right' for the concepts? 3. Which parts of the glossary work are (therefore) useful to you? 4. Which parts are not, and what makes them so? How could we make it work for you? Nicky Hickman suggested that we also need to look at the parts of speech represented in the glossary. She experimented with an Annexe in the ToIP Glossary document for the word "verify". Rieks Joosten noted that the noun "subject" is actual a relation! Without an object, there is no subject! That's why the definition says, "subject (of an identifier)". The same is true for other nouns for actions, such as "hit". So it would be good to identify the nouns that a particular verb relates. |
5 mins |
| Chairs |
Decisions
- None
Action Items
- ACTION: Nicky Hickman to add HXWG terms to the ToIP Glossary Workspace.
- ACTION: Brian Richter and Rieks Joosten to proceed with TEv2 tooling development and report at the next meeting.