2024-02-26 CTWG Meeting Notes
Meeting Date
Feb 26, 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
@Neil Thomson
@Judith Fleenor (Deactivated)
@Brian Richter
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
|
7 min | Review of previous action items | Chairs | ACTION: @Drummond Reed to work with @Kevin Griffin to decide which repos associated with CTWG and glossaries. ACTION: Brian Richter and Henk van Cann and Drummond Reed to discuss the normative section in the Terminology Governance Guide and spec it up. This is still pending while we work through the specifics of consistency checks on different ways of spelling terms. ACTION: Henk van Cann to connect with Kevin Griffin to determine the right CTWG repo (or a new one) for the Terminology Governance Guide. Feb15: Planned, going to be a new repo: ctwg-terminology-governance-guide. Rieks Joosten and Henk van Cann to plan an in-person get together including Kor Dwarshuis: March 4, 8AM, Groningen |
15 min | @Henk van Cann | Every meeting an new aspect to discuss and decide upon. https://trustoverip.github.io/ctwg-terminology-governance-guide/ Henk showed his work (see screenshots #1 through #4 below). His goal is for all of us to contribute to the Guide. @Ed Eykholt has already started to help. | |
5 min | Updates on TEv2 and KERISSE engine / kerific | @Henk van Cann @Brian Richter | Report on what progress (if any) took place over the past 2 weeks on either TEv2 or KERISSE tooling and code bases. @Henk van Cann and @Kor Dwarshuis have forked the two TEv2 repos for testing and contribution purposes. Issues are reported through the regular Github issues; one of them has been solved. |
25 min | Report on Spec-Up Coding Project | @Brian Richter | Brian first showed how he handled dangling refs and defs. He clarified that he For external references, Brian added a config called external_specs array. The tool then pulls in those documents, puts them in the spec, and hides them from view. Then it adds the x-ref tool that defines the x-ref tag. It takes two parameters, the spec tag followed by the term. Brian's code produces the same pop-ups as a local reference. @Henk van Cann asked Brian about how he handles aliases (aka synonyms). Brian explained that it is currently handled by added the aliases into the tag. Henk also asked about duplicate terms, i.e., a term that is defined locally AND also defined in an external. |
5 mins |
| Chairs |
|
Screenshots/Diagrams (numbered for reference in notes above)
#1
#2
#3
#4
#5
#6
#7
Decisions
None.
Action Items