Versions Compared

Old Version 2

changes.mady.by.user Henk van Cann

Saved on

compared with

New Version Current

changes.mady.by.user Drummond Reed

Saved on

Key

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

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:

5 minReview of previous action itemsChairs

ACTION: Brian Richter and Henk van Cann and Drummond Reed to discuss the normative section in the Terminology Governance Guide and spec it up.

15 minTerminology Governance Guide

Henk van Cann

Every meeting an new aspect to discuss and decide upon. How to contribute will be explained.

https://trustoverip.github.io/ctwg-terminology-governance-guide/

  1. This meeting's goal: Terminology design aids, section 10. 

  2. https://github.com/trustoverip/ctwg-main-glossary/pull/7 source management process review, see image #1
10 minUpdates on TEv2 and KERISSE engine / kerific

Henk van Cann Brian Richter 
Rieks Joosten 

Report on what progress (if any) took place over the past 2 weeks on either TEv2 or KERISSE tooling and code bases.

20

ACTION: CHAIRS — Henk van Cann Add ToIP Glossary Spec-Up document GitHub source management process review to the agenda for the next meeting.

10 minSpec-Up Use

Darrell O'Donnell

 Henk van Cann 

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

Brian Richter 

The meeting did result in a recommendation for how to handle abbreviations. The solution would look like this: Def, print and ref abbreviations
This would fix the abbreviation reference problem, the mal-formed defs problem and the offer option to selectively print abbreviations.

10 minToIP Glossary Open ItemsDrummond Reed 

Now that the ToIP Glossary has been published as a Spec-Up document, we have several open items:

  1. Filling in the front matter and end matter in the document (since the ToIP Glossary is not a typical ToIP specification).
  2. Enabling conventional web linking to ToIP Glossary definitions (in addition to Spec-Up xrefs).
  3. Publishing it at a short, permanent URL for standard web links. Proposal:

https://trustoverip.org/glossary/v1/#term

We discussed the challenges of source management and versioning. This will be discussed in the next meeting.

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


  •  ACTION: Kyle Robinson mentioned that the scope of application field will be far too big to collect them all in the ToIP dictionary via KERISSE engine. Action point for Henk van Cann to 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.


Screenshots/Diagrams (numbered for reference in notes above)

#1 Image Added


...

Decisions

  • None.

Action Items

  • ACTION: CHAIRS — Henk van Cann Add ToIP Glossary Spec-Up document GitHub source management process review to the agenda for the next meeting.
  • ACTION: Kyle Robinson mentioned that the scope of application field will be far too big to collect them all in the ToIP dictionary via KERISSE engine. Action point for Henk van Cann to 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.