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: None.
5 minReview of previous action itemsChairs
  • Action: Henk van Cann  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. From a Kyle Robinson remark last meeting. 
15 minTerminology Governance Guide

Henk van Cann

Every meeting a new aspect to discuss and decide upon. https://trustoverip.github.io/ctwg-terminology-governance-guide/

  1. This meeting's goal (postponed from previous): Terminology design aids, section 10. 

Henk proposed that we solve the problem of how to individually version a term and its definition in a glossary by adopting an overall model shown in screenshot #1.

Henk proposed that we can take current Spec-Up glossary files, such as the ToIP Glossary, and break them into files for every term. Then any terms community can use the individual files with any source management tool to manage their individual terms. Screenshots #1 and #2 shows how this could work with a terms wiki.

Screenshot #3 shows how Spec-Up can process individual Markdown files into a single published glossary document.

Screenshot #4 shows how glossaries can have edit buttons to show the ability to immediately edit a term.

Drummond Reed expressed that what Henk described is exactly the functionality he would like to have for the ToIP Glossary — and for any glossary maintained by a ToIP WG or TF. And the ability to link directly to a version of a term would be ideal.

ACTION: Henk van Cann to report on progress of his glossary management tooling project at the next meeting.

10 minSpec-Up Use

Darrell O'Donnell

 Neil Thomson Drummond Reed  

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. 

Notes from today's discussion:

Henk shared that he and Kor have added two other PRs to Spec-Up open source project at DIF (maintained by Daniel Buchner) to add a search button, back to top button and highlight menu item .

10 minReport on Spec-Up Coding Project

Brian Richter 

Brian will consider to integrate an abbreviations solution in his his deliverables. Drummond mentioned it's not compulsory in the assignment, but a walk (in) the extra mile.
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. Since the ToIP Glossary is not a typical ToIP specification, we rearrange the data in the the spec-up end result by reorganizing specs.json.
  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:

a. https://trustoverip.org/glossary/#term (latest)
b. Edit button besides every term that leads to the  prefered source management tool of the term
c. A link to the commit# of the term being referred to https://trustoverip.org/glossary/{commit#}#term

We discussed the design in #1 - #3 of flexible source management and single term - files at the core of the design.

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

Screenshots/Diagrams (numbered for reference in notes above)

#1 

#2

#3

#4


Decisions

Action Items