---
tags: KERI, CESR, OOBI, ACDC, git, github, github actions, NodeJS, NPM, JS, Docusaurus, React, Resources, Education-site, Spec-Up, readthedocs, Typesense, JSX, MDX, Education, Github, Git, Actions
---
# KERI 2024 Terminology Technical Meeting agenda & actionlist

**[Archive June 2023 - Dec 2023](https://hackmd.io/@hvancann/r1UfmhYkC)**

[Archive before June 2023](https://hackmd.io/HYb2PuRhQRWbR5dqFpRVIA)

---
# Index of this page
[Go To: Zoom meetings](#Zoom-Meetings)
[Go To: Future-Topics](#Future-Topics)
[Go To: Guidelines](#Guidelines)
[Go To: Meeting Reports](#Meeting-Reports)

---

Host: Henk van Cann [email]([e-mail]) / Co-Host: Kor Dwarshuis [email]([e-mail])

Meetings two times a week starting 2023-03-06:
- **Edu Tech Mon**: Mondays at 20PM AMS / 19PM UTC
- **Edu Tech Thu**: Thursdays at 10AM AMS / 9AM UTC

Double check, times and dates may vary. We don't record so there are no recordings available.

### Next focus week
Now and again we work a full week focussed. This is the issue/agenda of the next focus week where topics pile up:
https://github.com/WebOfTrust/WOT-terms/issues/130

## Training

---
- AI processing of Zoom recordings: a. Requirements 0.5 hrs + quickscan tooling 1 hr b. tests - 2 hrs c. implementation test + batches - 3hrs
[Zoom recording to AI - chatGPT](https://chat.openai.com/share/9f78b8aa-7f42-421a-b6ee-82209573fb2f)

#### Requirements
- 180 Zoom recordings feed to Youtube? And all new recording (semi-automatic)
- Transcribing
- Feed Prompt : substitutions
- AI generates Index-files with meaning full description of what has discussed and explained and by whom
- Scrape result to Kerisse.
---

## Zoom Meetings
Topics: **git, github, github actions, NodeJS, NPM, JS, Docusaurus, React, Resources, Education-site, Spec-Up, readthedocs, Typesense**

#### Calendar Invite
[Join Zoom Meeting](https://us02web.zoom.us/j/6859702250?pwd=vdSs1uGxSCDKa3vh0QEmbd9rdeFtlH.1) - Meeting ID: 685 970 2250 - Passcode: 1ekXu2

## Sixth week work
Once every 6 weeks we do a recap week of all quick 1-1-1-1-1 efforts. In agenda Henk: "Recap-week Kor": In 2024: week 12-18-24-30-36-42-48.
- Week 12 kickoff, no report
- [Week 18 2024](https://github.com/WebOfTrust/WOT-terms/issues/129)
- [Week 27 2024](https://github.com/WebOfTrust/WOT-terms/issues/165):
Documentation and robustness.

## Needs attention
Added by Kor (2024-06-06): Fix Kerific Chrome extension. Does not meet Chrome web store requirements and could be removed in 30 days

## Meeting Reports

## 2024-06-27
2024-06-24 great work! -> 2 points left: 2 and 5
DECISION: installation spec-up-t described in README.md , configuration and use in Docusaurus site
## 2024-06-24

1. DECISION: Leave the spec-up-t install on kordwarshuis useraccount
2. ACTION Kor: Formulate minimal requirements to an xref repo :
- must be a spec-up repo.
- anchor link? {Kor checks Brian’s code}
3. DONE: Test user interface Github.com -> edit term file + commit, will Github actions be invoked? {Kor action} ==> Kor: Test result: yes, commit via webbased editing counts as a push and triggers the “gh-pages” Github Action
4. DONE: Diff: Kor solves the BUG (in issues). And we don’t keep track of commit hashes for ref, only xrefs; why not -> https://trustoverip.github.io/ctwg-terminology-governance-guide/#role-specification-terminology-author-covering-concepts
5. {user}.github.io/{reponame} What if user and/or repo will be changed in the future?? All xrefs would deliver a 404! ACTION Kor: test changing repo name.
DECISION: username has to be persistent.

6. DECISION: What if directory's name that contains terminology definitions is changed? No problem because the persistent link doesn't contian the directory name.

## 2024-05-09
Agenda: TEv2 MVP next week

## 2024-05-07
- [ ] Action Kor: A. investigating the filtering of commit hashes based on date of a specification fix.

- [x] Action Kor: Issue155 [Test the interference of spec-up versioning and git commit versioning per copied file](https://github.com/WebOfTrust/WOT-terms/issues/155)

- [ ] Action Kor: C. Add anchor links to the front-end (or do we have those already?)

#### Add A. The use case for A. is:
Someone wants to fix a version of the entire specification at time T (snapshot) with the definitions and the external definitions that this specification refers to and at THAT MOMENT the latest represents and be able to show it in a kind of historical glossary in the future.

We can then, as Drummond first suggested, try to copy the Xrefs (references to external glossaries), but that seems "Hell" to me for various reasons.

#### What a date can do
My idea yesterday was to retrieve the correct version (commit hashes) of the internal and external referenced definitions based on moment T and make it available in the comparison tool. By comparison tool I mean this prototype idea, but for a single term file, e.g. "appraise.md". Described from here in Slack https://trustoverip.slack.com/archives/C01BBNGRPUH/p1714418484585169
and also discussed as Step 1 here: https://wiki.trustoverip.org/display/HOME/2024-05-06+CTWG+Meeting+Notes

Why should my approach be preferred?
- Do not save copies of definitions back and forth.
- Use standard Github functionality

Intended result: 1-1-1-1-1- try to show "what a date can do"

## 2024-04-18
- [ ] Action - Henk: **design SearchEngine workflow** to check with Typesense whether it's possible to
- the small text results -> low precedence
- Plus icon-system: first result, don't show other **exact same** result but show "+3 (DIF, blog HvC, ToIP)" Link item between parenthesis to their search results that you're hiding.
A totally different approach to get rid of duplicity of search results is to filter them out in the left menu. This func is there already

## 2024-04-15
- [ ] PR reminder Spec-Up Daniel Buchner: working for TrustoverIP. (ION docu and you've met him at IIW in fall 2023)

Structure Business Rules for Lead Terminology creators -> if not applied -> a Basic Active Linter-Corrector -> splitting possible.

### 2024-04-08
- [ ] Action Kor: [split up terms_and_definitions.md](https://github.com/WebOfTrust/WOT-terms/issues/145) of the main ToIP glossary.
==> https://github.com/WebOfTrust/WOT-terms/issues/147

### 2024-04-02
- [ ] Action: Kor pls Add https://hackmd.io/zku3Dn8qQeub_58Q1ivKLA in scraper.
- [ ] DONE Action Kor: Tab in WOT terms sheet with overrides. Solution: just a link to the file from KERISSE How-we-did
- [ ] DECISION: Try to automate documentation from the documentation in the source files. Doxygen for Bash and JSdoc for nodeJS.
- See https://chat.openai.com/share/fdc4c4fe-814c-49dc-8975-325ac154a115
- https://jsdoc.app/about-getting-started
- https://www.doxygen.nl/

- [ ] Action Kor https://github.com/WebOfTrust/keripy/blob/development/docs/naming.md Python Style Guide for keripy
Overide: Python Naming, Python Style Guide

- [x] Action Henk: remove external links to other **glossaries** from text of the wiki definitions, because we have cross links (Dictionary)
Tue April 2: Done until 'E' - Wed April 3: Done until 'Q' - Thu April 4: Done till end
[result here](https://github.com/WebOfTrust/WOT-terms/wiki) look for commits with text "xlink removed"
### 2024-03-28
- [x] Action Kor: create OpenAI chatGPT channel https://chat.openai.com/g/g-mTlHjxQCp-keri-wizzard

- [ ] DONE OpenAI chatGPT channel : how call the chatGPT from within Docusaurus with chat window.
Answer: not possible without external service

- [ ] https://docs.github.com/en/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token Kor looks into this related github API work.

### 2024-03-25

Decided to show "1-1-1-1-1-1" examples more instead of deep diving into side-issues or completeness. More than one of those examples per week would be great (if doable), we strive for at least one.
Once every 6 weeks we do a recap week. In agenda Henk: "Recap-week Kor": In 2024: week 12 (last week :) ) -18-24-30-36-42-48.

- [x] [e-mail] -> [e-mail],[e-mail]
- [x] Action Kor: create Search for Spec-Up, host on github.com/kordwarshuis , discuss with Henk
- [x] Action Kor: Offer Search for Spec-Up as a PR to DIF
- [x] Action Kor: github API kerific user-account
==> https://github.com/WebOfTrust/WOT-terms/issues/136#issuecomment-2037052106
- [x] Action Kor: github API imagesdir commit#
==> https://github.com/WebOfTrust/WOT-terms/issues/136#issuecomment-2037051054
- [x] DONE Action Kor: discordbot - Heroku tutorial
- [x] Action Kor: Heroku Udemy
- [x] Action Henk: Heroku Udemy, planned March 28, finished April 8
- [x] Action Kor: Roadmap - investigate Github Projects + API
==> https://github.com/WebOfTrust/WOT-terms/issues/134
- [x] Action Henk : Roadmap - investigate Github Projects API
==> https://github.com/WebOfTrust/WOT-terms/issues/134
- [ ] Action Kor : we are going to maintain a hit list with form-phrases (Rieks TEv2) or regular expression to catch slight deviations from a term: upper/lower case, plural singular, adjective, noun, adverb, relation, verb variants of a term etc.
- [x] Kyle's glossary about mining (!) there we will only look for, for example, "verification" because that can cause a conflict with our world SSI and KERI
Use Keri glossary as filter for external glossaries. Only KERI native terms should be imported from external glossaries. Other terms are not relevant.
==> [ISSUE Keri glossary as filter for external glossaries](https://github.com/WebOfTrust/WOT-terms/issues/146)

### 2024-03-21

- [x] Discuss Headless CMS (added 2024-03-20)
- [X] Kor: remove “createtag” in root of WOT-terms?
- [ ] please extra switch in filter on Glossary
- [ ] please extra switch in filter on Dictionary SSI (or only this one and sort a possible Glossary-hit to the top of the hits)
- [ ] sort by H1/H2 in glossary hits
- [x] Image directory: next up is : show commit hash by getting it from a github API call.
==> https://github.com/WebOfTrust/WOT-terms/issues/136#issuecomment-2037056258
- [x] Image directory: then up is : allow reputational data to be added (e.g. thumb up or down or free text field)
==> https://github.com/WebOfTrust/WOT-terms/issues/136#issuecomment-2037056258

### 2024-03-12

- [x] DONE Kor Action: AI off the main page KERISSE
- [X] Kor: idea: make a script that downloads all images in the glossary (on hackmd). To safeguard the images (not relying on HackMD). Decision to make: essential vs. nice to have images.

### 2024-03-06

- [x] https://github.com/WebOfTrust/WOT-terms/issues/121 Image directory ISSUE now

### 2024-02-15
- [x] Action Kor: scrape new glossary together by going through certain headings (Terminology) in these repo :
- https://github.com/trustoverip/tswg-keri-specification and https://trustoverip.github.io/tswg-keri-specification/
- https://github.com/trustoverip/tswg-acdc-specification and https://trustoverip.github.io/tswg-acdc-specification/
- https://github.com/trustoverip/tswg-cesr-specification and https://trustoverip.github.io/tswg-cesr-specification/
Please add to combined glossaries after de-duplication
==> https://github.com/WebOfTrust/WOT-terms/issues/147#issuecomment-2049409013

- [X] ONHOLD Kor and Henk plan to clone and study TEv2 beforehand in Feb-March, which already results in PRs (currently on modest scale):

- [x] STUDY Fri-Sat [Introduction overview](https://tno-terminology-design.github.io/tev2-specifications/docs/category/introduction-overview)

- [x] DISCUSS Sunday Feb 25, Noon, 30 min

- [X] STUDY Mon-Wed [Guides](https://tno-terminology-design.github.io/tev2-specifications/docs/category/guides)
- [X] DESIGN a test Thursday Feb 22, Noon, 30 min

- [x] IMPLEMENT a test / send PRs Thu - Sat

- [X] DISCUSS Sunday Feb 25, Noon, 30 min

Sunday March 3

- [X] https://tno-terminology-design.github.io/tev2-specifications/docs/category/introduction-overview

### 2024-02-07
- [x] Action Kor: Google Doc ToIP to Markdown in wiki-dir and 1 file, both represented in spec-up.

- [x] Action Henk: clean wiki WOT-terms of unwanted files: image.png and ls-result.txt

### 2024-01-25
- [X] Discussed https://identity.foundation/spec-up/

- [x] Henk prepayment

- [x] Action Kor: Test pages KERISSE crash resolution (HvC: solution?), crash in Brave ==> subtitles clienModule disabled [Testpage with subtitles working](https://weboftrust.github.io/WOT-terms/docs/video/lets-keri-on-together)

- [ ] Action Henk: How to use Consensus Feature of Kerific for various roles?

- [X] Discussed kerific consensus spec until anchor #what-advantagegoal-does-the-consensus-feature-have

### 2024-01-22
Gov Doc Temp : search longest tail first + use column A,B,C to construct variable name.

### 2024-01-18
- [x] Action Kor : document Github Actions scripts [here in this file](https://github.com/WebOfTrust/WOT-terms/blob/main/docs/how-we-did/_organization-of-Github-Action-scripts.md) and remove leading _ afterwards.
- by hand / automatic?
- calling each other?
- Deployment calls auto update glossary

---
**Ad document Github Actions scripts:** Documenting GitHub actions results in quite a bit more work, which is urgently necessary:

1. The SVG flow charts need to be updated.
2. They might need to be consolidated into one page because there is a relationship between the schemas.
3. Clarify the relationship more clearly.
4. In which parts can you divide all the scripts, what are the main tasks?
5. Which scripts run in GitHub actions and which ones are manual, and is this what we want?
6. When should the GitHub actions run?

Regarding point 4: The scripts can be divided into:
* Creating the glossary
* Scrapers that generate content for the search engine
* Managing metadata in Google Sheets
* Maintenance
* Various glossaries in a unified style
* "Carbon copies" (renaming to "annotated copies")

Regarding point 6:
* After push
* Manually initiated
* After wiki update (Gollum)
---

- [X] how-we-did directory revised by Henk, check @kordwarshuis TBW.

- [ ] Kor: https://weboftrust.github.io/WOT-terms/docs/github-latest-activity not working

### 2024-01-15

- [ ] Action Kor: investigate? Typesense: [sorting based on conditions](https://typesense.org/docs/0.25.2/api/search.html#sorting-based-on-conditions) -> could we do this for glossary hits?
- [ ] 'Click and add' in Kerific : subsets of glossaries possible for those who don't have one yet? Two tastes:
ownership (5 terms copied)| adoption (54 terms adopted)
- [ ] Action: Henk - Technical design including Usecases
- [ ] Action Kor: Add meaningful anchors to terms in Unified glossary that keeps the users inside KERISSE.
- [ ] When you turn on scraper, would you like to output a header for each term in "All combined" that I can access as a URL with an anchor? for example "#### keri-toip' and '#### keri-WebofTrust', #### staat voor iets in html dat een anchor produceert, het hoeft niet eens zichtbaar te zijn dat "keri-WebofTrust" als ik er maar naar toe ga in de pagina.
- [ ] https://weboftrust.github.io/WOT-terms/docs/glossary-unified?level=2 but then it should be https://weboftrust.github.io/WOT-terms/docs/glossary-unified?level =2#keri-toip for example, so it jumps to exactly that definition; what is the definition of KERI according to ToIP. I already see a challenge: the ToIP filter at the top must be "on" in this example.

- [X] Action Henk: IP rights present -> how-we-did/ip-rights-scraping.md
- [X] Action Henk: define Kerific and Kerisse

### 2024-01-11
- [x] Action Kor: pull issues in some datastructuur via api as a test in a github action "Roadmap" in WOT-terms repo.
- [x] Action Kor: 1 issue in 1 repo (WOT-terms) 1 status change of 1 custom field (Relevance), results in 1 roadmap change in 1 github project.

[==> https://github.com/WebOfTrust/WOT-terms/issues/134](https://github.com/WebOfTrust/WOT-terms/issues/134#issuecomment-2049397142)

- [x] Action Henk: Integrity app on Mac - Henk try

### 2024-01-09
- [x] DONE Action Henk: https://github.com/WebOfTrust/WOT-terms/blob/main/logs/brokenLinks.md
- [x] Action Kor: https://github.com/WebOfTrust/WOT-terms/blob/main/logs/brokenLinks.md
- [X] Kor: idea: make a page with all visualisation images in Slack History on one page in KERISSE.
- [x] Action Kor: add a section with all visualisation images from glossary on one page in KERISSE.
- [x] Action Kor: Discord bot / “See” redirects.
==> https://github.com/WebOfTrust/WOT-terms/issues/140#issuecomment-2039810595
- [x] CANCELLED href on KERISSE is wrong? “Technical meetings on KERISSE take place twice a week. Drop us a line if you're considering participation by creating an issue here. The repo for the Web of Trust terminology and glossaries is here.” https://github.com/WebOfTrust/keri?tab=readme-ov-file
- [x] ON HOLD Kor: How to handle .mmd files on Github.
mmd files are mermaid markdown files. How to show interpreted mermaid code in search results?
===
Code:
https://weboftrust.github.io/WOT-terms/docs/glossary/PRNG?Wot-terms%5Bquery%5D=Account+Creation+Workflow&Wot-terms%5BrefinementList%5D%5Bcategory%5D%5B0%5D=Code&searchModalStatus=open
===
Results in:
Graphic representation:
https://github.com/WebOfTrust/signify-ts/blob/main/diagrams/account-creation-workflow.mmd
===

### 2024-01-04

- [x] CANCEL chosen for Heroku March 2024 - Action Kor : Ask Kent for tips NPM services AWS.
- [X] Action Henk : create recipe for Phil&Sam how to indicate dependency, effect, importance, urgency, timing (starts, takes calender weeks) based on their guesses. What are all the defaults?
- [X] Discord bot / “See” redirects, done!

---
## Guidelines
Howto's of WebofTrust documentation effort in github project page: [Howto](https://github.com/WebOfTrust/WOT-terms/tree/gh-pages/docs/howto)

How can we use the hackmd Meeting agenda & action list better, less duplication of work and more results with fewer repetitions of moves and search work (less forced to cancel 6 months later)?

### TO DO after every meeting
1. always do urgent small things within 48 hours to prevent our memory from failing us, or make an addition (+ report with one sentence and link), so that "it is clear to me that it is clear to you".
2. Assignee rewrites action points originally written by Assigner to confirm understanding.
3. reporting + results AND documentation available with one click (two links usually)
4. Without further spec, all actions done before next meeting
5. Split an unfinished action item into what is completed + result link and a new action item.
6. An example result link + how-we-did directly behind the action item in the hackmd.

### Use self-explanatory links in the reports.

For example:

https://weboftrust.github.io/WOT-terms/docs/how-we-did/create-search-index?level=2
This link is self-explanatory, fine. It's the documentation link.

So not: https://hackmd.io/@hvancann/ry2EB_bq2?type=view#Typesense

But [Typesense override method documented in June 2023 Archive WOT Education site Tech meetings](https://hackmd.io/@hvancann/ry2EB_bq2?type=view#Typesense)

#### Good:
- [ ] Action Henk: remove external links to other **glossaries** from text of the wiki definitions, because we have cross links (Dictionary)
Tue April 2: Done until 'E'
Wed April 3: Done until 'Q'

#### Better:
- [ ] Action Henk: remove external links to other **glossaries** from text of the wiki definitions, because we have cross links (Dictionary)
- [X] Tue April 2: Done until 'E'
- [X] Wed April 3: Done until 'Q'
- [ ] Thu planned until 'Z'