Any news and updates of general interest to CTWG members

• Rieks Joosten has started some text concepts on terminology design, which is very much a first rough draft. Noteworthy perhaps is the 'real-life story', which contains ideas that we could all perhaps use.
• We can get Elisa/Judith for a TOIP zoom account to get access to the notes that contain transcripts of recordings. Makes notes taking easier - you can basically get everything from the transcript.

•  ACTION: Drummond Reed to check with Judith Fleenor about resources on hiring additional resources/budgets in order to complete the Terminology Toolbox 2.0 functionality.
  •  NOT DONE: Drummond will talk with Judith in person at the LF Member Summit meetings this coming week.
•  ACTION: Drummond Reed to offer a meeting on terminology and mental models to the ToIP Technology Architecture V1.0 Spec Editors team.
  •  NOT DONE: The spec editors have been too busy finishing the first public review draft. This meeting should happen after that is out (and U.S. Thanksgiving is past).
•  ACTION: Drummond Reed to read Neil's document on the Technology Architecture TF "authenticity and integrity" issue and summarize his thoughts and next steps in TATF GitHub issue #10.
  •  DONE: This issue is now in last call.
•  ACTION: ALL: review and provide feedback on the

• HXWG Overcoming

•  Human Harms in SSI Ecosystems paper. There has been some feedback (e.g., from Daniel Hardman, and others). It points to important issues; one issue seems to be that at the tech level you can do anything (create, e.g., potato peelers), but providing guarantees it won't be misused is quite another matter.

With IIW coming up next week, are there any particular sessions those of us attending would like to call on Concepts and Terminology?

Neil Thomson is already doing something on authentic data, part of which is getting the ideas (concepts?) straight (e.g., authentic, identity - and specific issues (e.g., integrity), and find out how they are related (making sense of it). It's all context. Perhaps we could use dot-notation, e.g., authentic.data, thus specifying your context. Rieks Joosten thought it might help to not focus on the terms, but rather on meaning. One trick is to use a bizarre, non-existent word - some consonants and vowels, e.g., 'praksel' (the actual word we used wasn't recorded!) as a placeholder of the term you are after, so that nobody associates anything with it. and then go after the meaning you want to express. Another trick is to explicitly state the context you want to remain in and dismiss anything said/argued that is not in that context. TNO want to inventory such 'tricks' and have started a very premature draft of texts that are to become a site on terminology design.

We haven't got to discuss any particular IIW sessions those of us attending would like to call on Concepts and Terminology. Let's ponder and if anything comes up, discuss on slack.

We have talked a bit about the holder binding paper that was started at RWOT the Hague, and how terminology plays a crucial role in getting the problems properly stated, and how difficult it is for all of us to use that same terminology - even though we agree on them. It becomes increasingly clear that different people use the same terms for different things, and mixing their stories (e.g., with standards such as for VCDM or DIDs) shows people have ideas that are quite problematic. One such idea is thinking that if the holder can prove control over the DID that is the subject identifier in a claim (in a credential) in a presentation, then the holder is the subject of the claim. Another such idea is that the holder should provide (and control) the DID that an issuer uses to represent the holder as the subject of a claim. 

Henk van Cann and Neil Thomson elaborated a bit on a new idea, perhaps based on an observation that people typically do not use terminology to express their ideas, but look for the meaning they want to express by 'hunting for terms': one can envisage an author that uses VSCode to write its markdown to have a plugin that can provide a popup with a suggestion of a term to use, with various definitions from different scopes, and selecting one would make it a 'term-ref' - similar to what plugins for programming languages do when you are looking for a particular function to call.