2024-04-22 CTWG Meeting Notes

2024-04-22 CTWG Meeting Notes

Meeting Date

  • Apr 8, 2024 : ToIP Concepts and Terminology WG Bi-Weekly Meeting  10:00-11:00 PT / 18:00-19:00 UTC. 
    See the ToIP Calendar for the full schedule.

Zoom Meeting Recording

Attendees

  • @Drummond Reed

  • @Henk van Cann

  • @Rieks Joosten 

  • @Brian Richter 

  • @Judith Fleenor (Deactivated) 

Agenda Items and Notes (including all relevant links)

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:

10 min

General announcements

All

Any news and updates of general interest to CTWG members:
1.  Concepts & Terminology Working Group landing page edits before IIW → New page proposal

ACTION: ALL to read and review the new CTWG landing page proposal.


2. IIW Update. Judith shared that "every single session was in-depth content" relative to many core ToIP projects. There were also several excellent "face-off"/"bake-off" sessions providing overviews of different areas (specifically trust registries and personal data stores). Scott Perry gave a session on governance that was much better attended and appreciated than at earlier IIWs.

3. @Rieks Joosten shared that TEv2 has an example site now: 

TEv2 MVE for Github Pages (tno-terminology-design.github.io)



5 min

Review of previous action items

Chairs

Action: @Henk van Cann  selectively scrape terms from external glossaries based on a ToIP-SSI set of terms that we'd like to keep from conflating over various scopes. From a @Kyle Robinson remark last meeting. 
Now an WOT-terms issue, follow development there.

15 min

Terminology Governance Guide

@Henk van Cann

Every meeting a new aspect to discuss and decide upon. https://trustoverip.github.io/ctwg-terminology-governance-guide/

ACTION: @Henk van Cann to report on progress of this project at the next meeting. This week: Source management Use Cases

@Henk van Cann gave an update on the progress of the tooling and documentation he's been working on. In screenshot #1 below, he shows the text describing wiki-based edting; in #2, he shows IDE-based editing; in #3, he shows git-based editing that can be done as a PR. The big difference is that wiki-based editing relies on wiki permissions, vs. IDE-based using GitHub permissions.



10 min

Spec-Up Use

@Darrell O'Donnell

 @Neil Thomson @Drummond Reed  

Spec-Up tips & tricks As we have many specifications in flight I have been compiling some SpecUp tips & tricks

ACTION: Coordinate with @Darrell O'Donnell on a "cheat sheet" for Spec-Up with input from @Drummond Reed and @Neil Thomson



10 min

Report on Spec-Up Coding Project

@Brian Richter  @Henk van Cann 

Edit-button and History-button

10 min

ToIP Glossary Open Items

@Drummond Reed 

Action plan:

Brian's PR has been accepted by DIF.

In our ToIP specification template, we need to incorporate the correct Spec-Up code.

Then Kor's changes should be accepted at DIF.

We also need to make the change to one-file-per-term.

We also need to be able to refer to a single term with a link that is persistent to the latest version.

We also need to look into it for existing specs.

ACTION: @Drummond Reed to coordinate with @Darrell O'Donnell, @Henk van Cann , and @Kor Dwarshuis to find a meeting time.

5 mins

  • Review decisions/action items

  • Planning for next meeting 

Chairs



Screenshots/Diagrams (numbered for reference in notes above)

#1 


#2


#3






Decisions

  • None.

Action Items

ACTION: ALL to read and review the new CTWG landing page proposal.
ACTION: Coordinate with @Darrell O'Donnell on a "cheat sheet" for Spec-Up with input from @Drummond Reed and @Neil Thomson
ACTION: @Drummond Reed to coordinate with @Darrell O'Donnell, @Henk van Cann , and @Kor Dwarshuis to find a meeting time.