• 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:
  • John Wunderlich is a "privacy curmudgeon" who chairs the Privacy-Enhancing Mobile Credentials WG at Kantara. He has an interest in the terms "appropriate friction" and "operational circumstances".
    • Refer you to the Kantara Privacy Enhancing Mobile Credentials Implementors Guidance report (published this month) it has a table of terms and definitions. https://kantarainitiative.org/reports-recommendations/
  • Darrell O'Donnell is one of the co-chairs of the Technology Stack Working Group and is currently the primary author driving the ToIP Trust Registry Protocol Specification, which needs glossary integration.
  • Henk van Cann also gave an introduction since this is his first meeting a new co-chair of the CTWG. He was an entrepreneur who got into the blockchain and then the SSI space, and then was introduced to KERI. He first joined CTWG 18 months ago as he got involved with the glossary work for KERI. He has been studying the deep glossary work from TNO and former CTWG co-chair Rieks Joosten. He and his colleague donate time to these efforts, but extensive additional work would need to be paid.

Any news and updates of general interest to CTWG members

• Scott Perry shared via Slack that the Issuer Requirements TF of the Governance Stack WG has approved a draft of their Issuer Requirements Guide and now wants to add a glossary (ideally using our TEv2 tooling, although the Guide is currently drafted as a Google doc).

ACTION: Drummond Reed to get back to Scott Perry regarding next steps for developing a glossary for the Issuer Requirements Guide.

• 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, and Daniel Hardman.

• This meeting needs to be postponed as we think through our new glossary tooling.

Henk van Cann Brian Richter 
Rieks Joosten 

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...

1. The ToIP Glossary.
2. A specification-specific glossary

...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).

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.