2023-12-18 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)

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

  • Judith Fleenor said that the next All-Members Meeting is January 10th at 10AM Pacific Time, and this will be a chance for all WGs to share their plan for the year.
2 minReview of previous action itemsChairs
10 minUpdate on TEv2 progress

Rieks Joosten mentioned that TEv2 tools are being polished (small changes and additions are made as the tool is being put to use in multiple github and gitlab repo's) and documentation is slowly being more accurate and simplified. Rieks said that the tooling can now produce a human-readable glossary and sort it in some standard ways.

Brian Richter raised a PR in the TEv2 tools repo for the ingress tool. It needs to be tested and documentation needs to be added. Brian has started on the documentation and hopes that it should ready by the next TEv2 meeting.

10 minScheduling "Putting TEv2 To Work" meetingDrummond Reed 

We clarified that this meeting is a technical meeting to go through the tooling, especially to explain it to Henk so he has the full picture. To be rescheduled — assigned to Drummond.

Neil Thomson suggested that, in addition to a developer's walk-through meeting, we may also need a content author's walk-through meeting.

25 minTransitioning from Rieks to Henk van Cann as new CTWG co-chair

Rieks shared that his goals for 2024 is that he can be assured that other can continue this work so that he can go into 2025 knowing that the work is in good hands. The more people that start using the tool and naturally come up with feature requests and change requests, the better.

Rieks confirmed that the TEv2 repo is all open source, Apache 2.0, and will continue to be maintained by TNO. It will be integrated with the Semantic Treehouse tooling, which can do for message schema and ontology documentation what TEv2 does for terminology. This should also give a new kind of support for terminology development, making it more efficient for both.

Henk asked if the repo was set up for external PRs. Rieks confirmed that the playground is implemented entirely in GitHub. The tool is already being used for the development of some standards, so the production version needs to be very high quality.

Henk is still studying the TEv2 tooling and repo so he can fully understand how it works, which ideally support what he has been doing with KERISSE. Henk confirmed that his goal is 2024 is to bring the TEv2 tooling and the KERISSE tooling together.

Judith asked about where the TEv2 tooling repo is now hosted. Rieks explained that the repo is now a public GitHub repo to maximize the public value. The repos are:

Henk asked about the license file, and Rieks confirmed it is at this location: 

ACTION: Rieks Joosten to add a license file to the specification repo.

Drummond shared that ___________

Neil said that we've always had a path from informal to formal sharing of information, so his goal is to make the path as easy as possible for authors to do that.

Brian Richter's goal is to see a lot of people use it, including him.

Rieks Joosten suggested that there are specific repos that could take specific advantage of starting to use the tooling. If we can show the tooling working in those repos, it will get us off to a great start.

Judith Fleenor's #1 goal for this WG is to see if there can be a unified way to do glossaries and terminology that gets all the tooling and processes in alignment. And secondarily that ToIP deliverables are using that tooling. And thirdly that we can export that functionality to help other LF projects such as DIF and C2PA.

5 mins
  • Review decisions/action items
  • Planning for next meeting 
ChairsOur next meeting will be Monday January 15.

Screenshots/Diagrams (numbered for reference in notes above)

#1


Decisions

  • Sample Decision Item

Action Items