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: 

•  Action: Kor Dwarshuis A YouTube instructional video on how to set up a spec-up-t project from the beginning would be great.
  
•  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>
•  Workshop Spec-Up-T based glossaries; planned:
  Oct 10 7PM-8PM CEST,  10AM PDT

•   Carly Huitema: If I am to contribute content, how do I do that? do I get added as a contributor, or do I fork the repo?
  In general: You fork the repo and offer PRs
  The various roles and their Use Case are described here:
  https://trustoverip.github.io/spec-up-t-website/
  

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.

@drummondreed mentioned that he'd love to see a definition-only version of the search option ->

•  Action: @kordwarshuis [Issue38](https://github.com/blockchainbird/spec-up-t/issues/38). Status: Ongoing Oct-7.
•  Preview: https://dwarshuis.com/test/temp-ctwg-main-glossary/docs/#terms-and-definitions. Search with both harmonica open and closed. The number of hits will adapt. Use the left and right arrow keys to navigate through the hits.
  Kor Dwarshuis:
  Example:
  -search for blockchain
  -collapse definitons
  -see nr of search results adapt
  So the search adapts to the definitions being collapsed or not
  
  
•  

  We get stuck with the fact that if content writers use defs outside of the terms def directory of that ~, then <dd> is also created there and then my code is messed up because I do not yet know how to target the terms / defs. We suggest to limit: That is why we are just going to say →defs in one place
  Action: Kor Dwarshuis will solve this feature that we consider a bug in Spec-Up-T.

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.
  
  18:40:21 From Carly Huitema to Everyone:
  https://www.w3.org/OWL/
  18:42:33 From Carly Huitema to Everyone:
  https://nlp.stanford.edu/IR-book/html/htmledition/stemming-and-lemmatization-1.html
  18:43:41 From Carly Huitema to Everyone:
  "In OWL (Web Ontology Language), an "Also Known As" relationship is typically modeled using the owl:sameAs property. The owl:sameAs property indicates that two URIs (resources) refer to the same entity, essentially linking different identifiers or terms that represent the same concept."
  18:43:43 From Carly Huitema to Everyone:
  <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:owl="http://www.w3.org/2002/07/owl#"> <!-- Define two URIs for the same concept --> <owl:Class rdf:about="http://example.org/ontology/Person"/> <owl:Class rdf:about="http://example.com/vocab/Individual"/> <!-- Indicate that both URIs refer to the same concept --> <owl:sameAs rdf:resource="http://example.com/vocab/Individual"/> </rdf:RDF>