2024-01-15 CTWG Meeting Notes
Meeting Date
Jan 15, 2024 The CTWG meets bi-weekly on Mondays at 10:00-11:00 PT / 17:00-18:00 UTC. See the ToIP Calendar for the full schedule.
Zoom Meeting Recording
Attendees
@Drummond Reed
@Henk van Cann
@Brian Richter
@John Wunderlich
@Darrell O'Donnell
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
3 min |
| Chairs |
|
15 min | General announcements | All | Any news and updates of general interest to CTWG members
ACTION: @Drummond Reed to get back to @Scott Perry regarding next steps for developing a glossary for the Issuer Requirements Guide. |
2 min | Review of previous action items | Chairs | ACTION: @Drummond Reed to schedule a "Putting TEv2 To Work" meeting in early January to discuss how we can start using the TEv2 tooling with GitHub Markdown documents for ToIP deliverables. This will be largely a technical session to lay the groundwork for a subsequent tutorial session for ToIP WG and TF chairs and deliverable authors. Ideally this meeting will be in the evening Pacific Time so that it will be in the morning for Rieks. Proposed attendees: @Rieks Joosten, @Brian Richter, @Henk van Cann, @Neil Thomson, @Kevin Griffin, @Darrell O'Donnell, @Drummond Reed, @Judith Fleenor (Deactivated), and @Daniel Hardman.
|
10 min | Updates on TEv2 and KERISSE | @Henk van Cann @Brian Richter | Report on what progress (if any) took place over the past month on either TEv2 or KERISSE tooling and code bases. Also: should we still keep the Monday 9AM PT/17:00 UTC calls on TEv2 code development? @Henk van Cann showed a proposed approach to glossary development for the ToIP Issuer Requirements Guide (see screenshot #1 below). It shows how glossary terms can be added to an existing document using a tool called KERIFIC that knows how to parse HTML to find matching terms and then add buttons with links to the definitions of those terms. Henk then showed a hand-written diagram (screenshot #2) showing how the CTWG TEv2 code base and the KERISSE code bases related. Then he showed another diagram (screenshot #3) to show how the GitHub repos related to Google Sheet and Google doc "middle" to add necessary metadata and feed it to the backend tools (such as SpecUp or dynamic site generators). Lastly Henk showed the spreadsheet he uses to carry the actual definitions for the KERISSE tooling (screenshot #4). @Darrell O'Donnell asked the question: Could the tooling pull in terms from two glossaries...
...and then create a merged glossary for the final spec document. We then went over how markup can be added to a Markdown document. Henk showed the example shown in screenshot #5. @John Wunderlich pointed us to the W3C Data Privacy Vocabulary at https://w3c.github.io/dpv/dpv/ Henk then gave a short demo of KERISSE (screenshot #6). |
25 min | 2024 Plan for CTWG Tooling and the ToIP Glossary | ALL | Discuss if we want to converge the TEv2 and KERISSE tooling and code bases; if so, what is the plan for that; if not, who wants to work on what. Also, what is our revised plan for the "Putting TEv2 to Work" action item above? ACTION: @Drummond Reed to have an offline meeting with his Technology Stack WG co-chair @Darrell O'Donnell to discuss the essential tooling needed to add glossaries to the current and upcoming TSWG specifications and report back via Slack or no later than the next meeting. |
5 mins |
| Chairs |
Screenshots/Diagrams (numbered for reference in notes above)
#1
#2
#3
#4
#5
#6
Decisions
None.