1) Check on Rieks Joosten and Brian Richter meeting 2) Discuss $20K Terminology Toolbox 2.0 bounty 3) Game plan for ToIP Technology Architecture V1.0 Specification glossary 4) Holiday meeting schedule
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:
Chadha Degachi recently started working with Rieks in the ____ Ecosystems Group. She is working on the Term Reference Resolution tool.
5 min
General announcements
All
Any news and updates of general interest to CTWG members
None
2 min
Review of previous action items
Chairs
ACTION:Drummond Reedto offer a meeting on terminology and mental models to the ToIP Technology Architecture V1.0 Spec Editors team.
ACTION:Drummond Reedto introduce Brian Richter toRieks Joostenvia email or Slack so Rieks can explain the scope of the Terminology Toolbox 2.0 work.
Rieks explained that the current Terminology Toolbox 1.0 glossary tool generates glossaries directly from terms wikis, whereas the Terminology Toolbox 2.0 will first use the MRGT to convert a terms wiki (or other input format) into a machine-readable source, then the HRGT is used to produce a human-readable output format.
Chadha explained that she has talked to Sid Haniff about his work on the MRGT.
ACTION: Chadha will share with Brian information about the MRGT.
Chadha said that she is working on the Term Ref Resolution Tool, which is the second tool int he suite.
Rieks suggested that the full tool suite be tested in the TNO environment first,
Nicky feels this is a wonderful opportunity to marry the social side of glossary development with the technical/mechanical side.
Nicky shared that it is critically important that ToIP deliverables not be derailed by disputes on terminology, because that can happen if the group does not align early and make a priority of doing terminology design.
What worries Nicky Hickman slightly about "cool tools" for terminology is that the tooling does not actually solve any of the problems that can only be solved by people. The questions of meaning and definition can only be agreed upon by the community members.
10 min
Game plan for ToIP Technology Architecture V1.0 Specification glossary
Drummond summarized that the Technology Architecture TF knows that it has a big job on its plate to prepare a complete glossary (and possibly one or more mental models) for the ToIP Technology Architecture V1.0 Specification (TAS).
Neil Thomson says that we need to go about a real process of what Rieks calls terminology design for the TAS glossary. It will be a great litmus test for the process we are working through here.
Neil has some specific suggestions for how to go about this process.