Page Comparison

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

•  A new chapter in the draft term gov guide, after talking to DIDAS people (see announcement above):
  https://trustoverip.github.io/ctwg-terminology-governance-guide/#audiences-and-languages
  
  
•  Kent's blog post about SAIDs is live: https://kentbull.com/2024/09/22/keri-series-understanding-self-addressing-identifiers-said/ 

Action: Kor Dwarshuis A YouTube instructional video on how to set up a spec-up-t project from the beginning would be great.

•   Add new terms OR underscore in the Spec-Up-T terminal menu
  The idea was brought in that we could also use Git branches (development versus main). This is, of course, true but requires another level of git user capacity. The underscore would be a workaround.
  Decision: postpone feature.
  
  
•   Freeze OR Snapshot: Snapshot
  
  
•  Action: We need links that are self-explanatory with version numbers in them. Because those links are what people are going to use to refer to the glossary as a whole and to specific terms. @kordwarshuis and @henkvancann could look into how the current fundamental tracking of commits could add to this concept.
  <base-url>/v1/#term:<term>
  <base-url>/latest/#term:<term>
•  Discuss a tutorial "How to use the Main Glossary". → Workshop planned between Oct 8 and Oct 11, options:
  Oct 8 6PM-7PM CEST,  9AM PDT
  
  
  Oct 9 5PM-6PM CEST, 8AM PDT
  
  
  Oct 10 7PM-8PM CEST,  10AM PDT

•  URL Configuration
•  @HenkvanCann:  I think that http://glossary.trustoverip.org/#name can cause ambiguity with a "normal" header with the same name as a term. But I am not sure. We have to delve into this.
  Decision: This week, we'll decide on this proposal, but with the version numbers on board of the URL as well. Decision final: we stick to the #term to prevent collisions with normal headers in markdown.

Henk van Cann  

•  ACTION: Henk and Kor need a Spec-Up-T repo at trustoverip

Request was sent to Kevin. https://github.com/trustoverip/spec-up-t target.

Rieks Joosten Henk van Cann 

•  How to cope with multiple/singular versions of terms, with/without dashes. etc TEv2 tooling?
  Rieks has put a proposal in Slack in the July 1 CTWG chat. Already added as a draft to the Terminology Governance Guide. We will discuss this.
  This is a "Also Known As" challenge.