Meeting Date

  • : 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

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

  • Rieks: Regarding terminology governance, we may want to revisit Daniel Hardmain's slides of some time ago. New Link.
  • Rieks: ownership and maintenance of TEv2 repos has been transferred to TNO's Semantic Tree House development team.
    • Drummond Reed asked about how CTWG would engage with the Semantic Treehouse code base and team.
    • Rieks Joosten suggested that we could invite someone from Semantic Treehouse.
    • Henk van Cann said he has already set up an appointment with a representative of the Semantic Treehouse. Henk cautioned that we should make sure we're focused on TEv2 first.
    • Rieks shared more about the full mission of Semantic Treehouse, which is an open source project that tackles all kinds of issues regarding semantic standards and harmonization. It began with the semantics of messages, and moved into the documentation of ontologies.
    • Judith asked how they will be ingesting TEv2. Rieks explained that TEv2 will become an integral part of the Semantic Treehouse documentation suite. But Rieks said that TEv2 will also work as a standalone package.
7 minReview of previous action itemsChairs
  • 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 minTerminology Governance Guide

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 minUpdates on TEv2 and KERISSE engine / kerific

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 minReport on Spec-Up Coding Project

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. [[x-ref: SpecTag, Term, AltTerm]]

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
  • Review decisions/action items
  • Planning for next meeting 
Chairs

Screenshots/Diagrams (numbered for reference in notes above)

#1


#2


#3



#4


#5


#6



#7



Decisions

  • None.

Action Items