You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

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 Link / 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

7 minReview of previous action itemsChairs
  • ACTION: Drummond Reed to work with Kevin Griffin to decide which repos associated with CTWG and glossaries.
  • ACTION: Henk and Rieks bilateral; about alignment tools.
    Report conclusion:
    TEv2 is capable of doing what's needed in a fundamental way. It anticipates everything we need now and might need in the future. The KERISSE engine and kerific approaches the urgent challenges we have from a pratical stand point. Both worlds can mix. 
    The def-ref structure for terminology source in Spec-Up markdown files an intermediate solution with several drawbacks (to be discussed?)
    Follow up: Henk is motivated to put this on the work agenda as soon as the source management of our terminologies are in place. Kor and Henk will visit Rieks in early spring to prepare tests.
  • DECISION cancel the Monday 9AM PT/17:00 UTC calls on TEv2 code development
  • ACTION: Kevin Griffin, Darrell O’Donnell and Henk van Cann to discuss their thoughts on the best way to evolve the Spec-Up code base with the modifications necessary to support: a) dangling “def” and “ref” tags, 2) remote “ref” tags and to communicate their conclusions to Brian Richter. Suggestion: write normative section in Guide.
  • ACTION: Drummond Reed will notify Brian Richter (cc Judith Fleenor) that we will proceed make the proposed code contributions to Spec-Up to add the dangling ref/def and remote ref features as described in the2024-01-29 CTWG meeting notes Darrell O’Donnell and Kevin Griffin.
  • ACTION: Henk van Cann to propose the main agenda topic for the next CTWG meeting based on his discussions with Rieks Joosten and Kor Dwarshuis (and include one agenda topic for Brian Richter to report on his progress on his coding project as described above).
10 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.

  • Rieks Joosten said he will get together with Henk and Kor. To plan March-April.
  • Kor and Henk plan to clone and study TEv2 beforehand in Feb-March, which already results in PRs (currently on modest scale)
  • kerific-spec : Consensus tool
10 minReport on Spec-Up Coding ProjectProgress on his coding project as described in Slack #concepts-terminology-wg
20 min

2024 Plan for CTWG Tooling 

  • Source Management terminology Google Doc. Input variant 1 leading to Output variant
    "Darrell had the brilliant idea that the CTWG should begin publishing the ToIP Glossary as its own standalone Spec-Up specification"
  • Spec-Up and ToIP Specification template → this is currently being spearheaded by a new Technology Stack WG Task Force called the Specification Template Task Force
  • Def-ref consistency tooling in the Spec-Up environment.
    Discuss the separation of technical design and project guidance of the work Brian Richter is working on.
    Henk has an early draft available of what could be reasonable and measurable expectations of the deliverables and their pre-conditions. Draft
5 mins
  • Review decisions/action items
  • Planning for next meeting 
ChairsACTION:

Screenshots/Diagrams (numbered for reference in notes above)

#1



#2



#3



#4


Decisions

Action Items

  • Type your task here, using "@" to assign to a user and "//" to select a due date



  • No labels