Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

Agenda Items and Notes (including all relevant links)

Any news to CTWG AOB
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: None.
5 minGeneral announcementsAll

News and updates of general interest

to CTWG members:

https://weboftrust.github.io/WOT-terms/docs/glossary/witness?level=1

  • Judith Fleenor reminded everyone that Wednesday 13 December at 10AM PT is our All-Members Meeting where Justin Richer will give his talk on "Why Your Identity Is Not Self-Sovereign". 
2 minReview of previous action itemsChairs
  •  ACTION: Nicky Hickman to add HXWG terms to the ToIP Glossary Workspace.
  •  ACTION: Drummond Reed to put the topic of "hardening the ToIP Glossary" on the agenda of the next meeting.
  •  ACTION: Drummond Reed to work with the TSWG Task Forces to prepare the Markdown documents to be used with the TEv2 tooling and then scheduling a tutorial session (ideally in the evening Pacific Time so that it will be in the morning for Rieks).
    •  This is superceded by the action item assigned in this meeting.
10 minReport of TEv2 ProgressHow close are we to being able to apply it to ToIP deliverables?

Rieks Joosten gave an update on progress. The code is now available here: https://github.com/tno-terminology-design/tev2-tools

Rieks Joosten shared that there is now a human-readable glossary tool. He also clarified that any of the content available via the human-readable glossary tool is also available in a machine-readable format.

He said you can also specify the syntax of the term references (termrefs). So you can create markups that are just links, or they can produce pop-ups that can be configured.

He also said that they have refactored the code repositories. 

Brian Richter is hoping to send a PR to the repo above in order to consolidate the full TEv2 toolset. Brian needs to add a couple small additional features and then will submit it to the TNO repo above.

Judith Fleenor asked that in January we hold a meeting for all WG & TF leads to educate them about the TEv2 toolset and how they can use it with their deliverables.

Rieks Joosten felt there was still a gap between what the TEv2 toolset can handle and what the end-users (the deliverable authors) will need. For example, the TEv2 toolset currently works with carefully structured terms wikis. But that can still be a high bar. So there is still "a bit of bridging" to do.

Rieks' vision for "the farther future" is that, since TEv2 tools are being integrated into other TNO tools, there may be an entire tool suite for terminology maintenance. 

Rieks also mentioned the issue with the EasyCLA challenge and the need to fix it. The LF staff was looking into a new feature called "merge queues" that might fix that.

30 minHardening the ToIP Glossary

Discuss next steps on how to make the ToIP Glossary an official ToIP deliverable, and also how to manage versions

.
10 min

.

Henk van Cann said that one issue is versioning of a definition. For example, if there is a contribution to a definition that does not have wide support. KERISSE is relying on GitHub for this, as you can see both who made a revision and when it was made. So the hardening step would need this level of authentication and also reputation associated with each definition.

Drummond Reed shared that it was always a temporary step to use Google docs to assemble the ToIP Glossary. The intent has always been to ingest it into the curated text stage.

Rieks Joosten said that the next step would be for deliverables that use the terminology to start testing the definitions of the terms that they are using in those deliverables.

Henk van Cann suggested that support for upvoting and downvoting would be another ideal feature.

Neil Thomson felt that the most important step is "nailing down the toolset" in terms of how it will work and how easy we can make it for different TFs to work with. This may require a documentation specialist in each WG or TF that needs to work with the tools. He suggested we need to build some courseware around it to gain operational understanding.

ACTION: Drummond Reed to schedule a "Putting TEv2 To Work" meeting (preferably for the week of Dec 11, but if necessary the week of Dec 18) to discuss how we can start using the TEv2 tooling with GitHub Markdown documents for ToIP deliverables. This will be largely a technical session to lay the groundwork for a subsequent tutorial session for ToIP WG and TF chairs and deliverable authors. Ideally this meeting will be in the evening Pacific Time so that it will be in the morning for Rieks. Proposed attendees: Rieks Joosten, Brian Richter, Henk van Cann, Neil Thomson, Kevin Griffin, Darrell O'Donnell, Drummond Reed,  Judith Fleenor, and Daniel Hardman.

5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

Screenshots/Diagrams (numbered for reference in notes above)

#1

Decisions

  • Sample Decision Item

Action Items

  •  Sample Action Item
Our final meeting of the year will be Monday 18 December. Ideally we will have had our "Putting TEv2 To Work" meeting before this.

Decisions

  • None

Action Items