•  ACTION: Nicky Hickman to help complete the notes from this 2022-05-09 meeting. 
  •  Nicky will add more notes on the Glossary template.   She created a sub-folder and made a start on both the template & guidance doc. Key points: 

1. Is general guidance for ANY Glossary - agree to treat as such
2. Nicky to finish as draft for input to other groups and link to CTWG resources e.g. the terms wiki guidance
3. Still awaiting tools for new process - will update on my her current process as used for Yoma.

The Terminology Toolbox proposal, based on the formalized terminology model and diagram #1 below, was discussed in the last meeting which Drummond Reed missed, so he requests that we continue discussion.

• Rieks gave a complete overview of the Terminology Toolbox proposal. See the Zoom recording for the details along with screenshots #1, 2, and 3 below.
• Nicky Hickman asked whether the Inputs and Semantics WG could use this approach to design OCA plans for schemas. Rieks Joostensaid that there's been contact with Paul Knowles; we'll return to this topic once the tools are demonstratable.
• Nicky also wondered how a Glossary that follows this tooling can be kept in sync with revisions in a governance framework. For example, if the definition of jurisdictions changed (for example to encompass virtual Web3 jurisdictions), how does that affect the rest of the governance framework?
  • Drummond agreed that the governing authority must review impacts of terminology revisions on the rest of the GF.
  • Rieks mentioned (in the chat) that changes in the terminology would spawn a new version, so an existing work does not suffer, but can be 'upgraded' to the new version of the terminology after careful (terminological) considerations, and perhaps also have its own version number increased.
• Drummond asked about next steps in making Rieks vision a reality for our second generation Terminology Toolbox.
  • Rieks said he that the first step would be to do the tooling for the machine-readable-terminology generator.
  • The first step would be a "proof of principle".
  • However there may be some challenges. 

ACTION: Rieks Joostento write some text describing what a volunteer with relevant programming skills might contribute to the progress of the tools development, and send it out to the all-members list and/or slack channel