2024-12-16 CTWG Meeting Notes

Time

Agenda Item

Lead

Notes

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 min

General announcement

ToIP Glossary V1

All

Application in KERI glossary - planned January #1-#3

DIF synchronization

@Henk van Cann

DIF approach:

1. updates
2. NPM install instead of the old way
3. Make it optional to take the terminology engine

Action: vote to proceed, result: no objections so far

Action @henkvancann: check linux foundation legal stuff

15 min

Review of previous action items

All

Demo GitHub-less installs

Action: @Kor Dwarshuis It would be good to investigate how we could bring the menu into github actions, for Carly can't use the menu, and most probable many others.

Demo tref = a shallow form an xref

Action: @henkvancann check front-end editing in DS is possible?
Carly's reference:

https://github.com/ClimateSmartAgCollab/HUB-Harmonization/tree/main/library

generating:

https://climatesmartagcollab.github.io/HUB-Harmonization/ - frontend

min

Spec-Up-T

@Henk van Cann

Action: @Neil Thomson spins up a machine / image first.
Then guinea pig's role for following the documentation. Henk contacts Neils before the next meeting.
The first activity could be: edit https://trustoverip.github.io/spec-up-t-website/docs/intro/#real-life-example-keri-team
The second activity could be to test the menu on a Windows machine. But the commands can be run separately on the command line.
https://github.com/trustoverip/spec-up-t-website/blob/main/docs/general/windows-and-linux-installation.md

Action: All: Find editors for the various levels of documentation, see last meeting notes of Carly, Judith and Neil.

@Kor Dwarshuis: "We get stuck with the fact that if content writers use defs outside of the terms def directory of that ~, then <dd> is also created there and then my code is messed up because I do not yet know how to target the terms / defs." We suggest to limit: That is why we are just going to say →defs in one place
Action: @Kor Dwarshuis will solve this feature that we consider a bug in Spec-Up-T. : https://github.com/trustoverip/spec-up-t/issues/39 . Status: Fixed

min

Main ToIP Glossary

@Rieks Joosten @Henk van Cann

Postponed: How to cope with multiple/singular versions of terms, with/without dashes. etc TEv2 tooling?
Rieks has put a proposal in Slack in the July 1 CTWG chat. Already added as a draft to the Terminology Governance Guide. We will discuss this.
This is a "Also Known As" challenge.

Postponed: Revisit Carly's remarks here on Oct 7.
Henk's chatGPT conversation on Oct 21:
https://chatgpt.com/share/67167941-3964-800a-9f43-6d1f16662954

2 mins

Review decisions/action items
Planning for next meeting

Chairs

Zoom Recording

Attendees

Files/Screenshots/Diagrams (numbered for reference in notes above)

Decisions, see inline + wrap up:

Action Items, see inline