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:
5 min
General announcements
All
Any news and updates of general interest to CTWG members
Neil Thomson shared that the Hospitality and Travel SIG at DIF is a major profile of traveler info that vendors do not want to hold. It includes all the PII typically needed to support travel. The SIG is turning that into a schema. It includes both self-attested info (such as preferences) with other verifiable data. Neil explained that it is going to need a glossary. It will be helpful to have access to the ToIP Glossary, and will also need their own local glossary. Neil has been voluntold to be the glossary manager.
Rieks Joosten asked if it was just schema work, or does it also extend to protocols? Neil said that it was anticipated that the use of the data involves a spectrum of information that would go through graduated disclosure. Discovery, booking, traveling. Rieks felt that this was a very typical ACDC use case. Rieks also recommended that the Semantic Treehouse project, that is taking over the TEv2 work, works on those kinds of messaging semantics standards. They have tools for schema documentation. So it might be worth looking into.
Neil said that there's a need to know the exact way that a query can be matched against the schema.
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 toBrian Richter. Suggestion: write normative section in Guide.
ACTION:Drummond Reedwill notifyBrian Richter(ccJudith 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 notesDarrell O’DonnellandKevin Griffin.
ACTION:Henk van Cannto propose the main agenda topic for the next CTWG meeting based on his discussions withRieks JoostenandKor Dwarshuis(and include one agenda topic forBrian Richterto report on his progress on his coding project as described above).
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
Chairs
ACTION:
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