• Start recording
• Welcome & antitrust notice
• Introduction of new members
• Agenda review

• 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:

• ACTION: Rieks Joosten and Daniel Hardman to arrange a meeting to discuss how this hyperlinking should work with ToIP Term Tool V1 and our current terms wikis.
• ACTION: Rieks to incorporate feedback and publish revisions to his mental model diagram for the relationship of CTWG terminology and ToIP terminology.
• ACTION: ALL to review and comment on Rieks' draft proposal defining the objectives, ingestion policies, and curation policies for the ToIP terms community.
• ACTION: ALL to review the ISO Guide to IT Terminology. 

Report on the outcome of the first action item above.

• --

Daniel's notes from Slack:

• I have turned on glossary publication for the toip-terms repo and the ctwg-terms repo. This means our first two glossaries are live (published). You can see the results here:
  • https://trustoverip.github.io/toip-terms/glossary.html
  • https://trustoverip.github.io/ctwg-terms/glossary.html
• The actions that build these glossaries are one-click, but they need to be manually re-run for now; they don’t automatically run when a wiki page is updated. That’s a future enhancement. (@Rieks Joosten: I remember that we wanted to rename these repos, removing the “-terms” part of the name. I haven’t done that yet, but it will be trivial as soon as the CTWG approves.)
• The process I used to do this work is documented here: 
  • https://docs.google.com/document/d/1g9H1voPijT4ZHQddPT873PIMSpkLzhZ_smJpndzUkLk/edit?usp=sharing
• I think we need to move this documentation somewhere else, but I can’t remember where off the top of my head, and I’m now off to other tasks for a while. Feel free to move yourself — or I’ll come back and do it when I remember.

I suggest that we enable toip-groups to add terminology stuff to their existing repo's, requiring them to:

1. specify a location (URL) where they publish (rendered) documents (papers, documentation, ...), by default at trustoverip.github.io/reponame, which would include trustoverip.github.io/reponame/glossary for its (rendered) glossary. This allows people to quickly find stuff, and authors of GDocs, Confluence pages and the like will have stable URLs to link to. We should start out by ONLY using the default location.
2. specify a location where they maintain the 'raw docs' from which they render the stuff, by default at github.com/trustoverip/reponame/docs. This allows people to contribute to the groups documents by means of issues and pull requests to the repo. We should start out by ONLY using the default location.
3. specify a location where they curate their terminology, from which they produce their 'raw glossary' (putting the result in the 'docs' folder, which is subsequently rendered and published as a usable glossary), by default in the subdirectory docs/terms of the repo. This allows people to contribute to the group's terminology by means of issues and pull requests. We should start out by ONLY using the default location.
4. consider using the wiki of the repo as a terms-wiki like we do now.
5. consider some practical conventions for facilitating group members to contribute to the development of their terminology, e.g. by making specific issue-labels and/or templates. This would be (near-)future work.
6. read the documents (such as which you are drafting) that support repo admins in doing terminology. Of course, the 'raw text' would then reside at github.com/trustoverip/ctwg/docs, and it would be viewable at trustoverip.github.io/ctwg/doc-id. That would be the link that could be linked to from confluence pages, GDocs, etc.

Daniel Hardman's counter-proposal:

1. Rename the current repos that have -terms in their name into the name without that suffix: ctwg-terms becomes ctwg, for example. This would mean we would have a glossary published at https://trustoverip.github.io/ctwg/glossary.html. A permalink. I am in favor of this proposal but want the WG to ratify it. An analogous URL, with a different group name, would be the canonical location for any group within TOIP.
2. Accept the limitation that the glossary URL has to end in .html.
3. Implement your suggestions 1 and 2  and 5 and 6 as written.
4. Unlike your #4, require a terms wiki. We have no tooling that supports anything else, and we have no plans to produce any such tooling.

Daniel adds: I have now enabled automatic glossary generation on terms wiki edit, so any time someone changes a page in the terms wiki for either of the active repos, the glossary is automatically rebuilt (on about a 60-second delay).

See the ToIP Core Terminology Management Process section of the ToIP Core terms wiki README.md

• --

• Review decisions/action items
• Plan for next meeting 

Discuss concrete next steps for putting the ToIP Core terms wiki into production.

• The Governance Stack WG is ready to start adding terms.