cleaning up the dir structure and move source glossary from ToIP to W…

…ebofTrust
WebOfTrust · Jul 8, 2023 · bcbabc7 · bcbabc7
1 parent b775167
commit bcbabc7
Show file tree

Hide file tree

Showing 448 changed files with 416 additions and 56 deletions.
diff --git a/docs/How we did/load-glossary-weboftrust-in-docusaurus.md b/docs/How we did/load-glossary-weboftrust-in-docusaurus.md
@@ -0,0 +1,123 @@
+# Load ToIP glossary in weboftrust github page
+
+## Input
+
+1. The ToIP ACDC glossary locally (all the .md files pulled from [repo wiki](https://github.com/trustoverip/acdc/wiki))
+2. Terms WOT manage (xls or csv) table
+3. Excel or open source alternative
+5. Version control (git, Github or Gitlab)
+
+## Sync with origin ToIP glossary
+
+We use local repo's or PR to sync Weboftrust `WOT-terms.wiki` and TrustoverIP `acdc.wiki`. Note that the wiki pages of a github repo are manifest in a seperate repo. 
+### Why would we sync with ToIP glossary
+The main reason is interoperability. We want to join in the effort to create cross-referencing concepts, terms and glossary resources at WebofTrust.
+### Why sync with ToIP glossary nd not something else.
+From our WebofTrust view ToIP is our umbrella organisation that has similar objectives and principles. ToIP has good working relations with the European umbrella organisation eSSIF-lab too, who in 2023 can be considered as the global front runners of getting the terminology sorted out for Self-Sovereign Identity.
+
+** How our own repo [WebofTrust](https://github.com/WebOfTrust) came to be **
+In 2022 we reasoned:
+- we would to have to build similar Github Actions tooling like [ToIP](https://wiki.trustoverip.org/display/HOME/Terms+Wikis) already has.
+- we can't join the synchronization effort already taking place with [eSSIF-lab](https://essif-lab.github.io/framework)
+- we would have to maintain these auxiliary which keeps us off other important work
+In 2023 we experienced:
+-  lagtime by ToIP and Linux Foundation internal github governance rules
+- the knowledge and skills needed to "roll our own" had been acquired
+Mid 2023 we decided:
+- to start [Weboftrust wiki](https://github.com/WebOfTrust/WOT-terms/wiki)
+- to sync at will with [ToIP wiki](https://github.com/trustoverip/acdc/wiki)
+
+## Software environment
+
+For Github pages Docusaurus runs locally and remotely (Github Actions). **Be sure to**:
+
+1. Have the same version of Docusaurus installed locally as Github currently uses remotely
+2. study [this guide](https://docusaurus.io/docs/advanced/routing#file-paths-and-url-paths) to avoid frustration with paths.
+
+## Steps
+
+### Pull the WebofTrust wiki
+
+Because the glossary is maintained in Github wiki using Github userinterface here: [Weboftrust wiki](https://github.com/WebOfTrust/WOT-terms/wiki), the most recent version is a remote repo. We have to pull this wiki-repo (be sure to have the **wiki** repo not the "normal" WOT-terms repo!) to local to be able to create our own glossary and Docusaurus static site from this. The static site is then run as a github project page (branch _gh-pages_).
+
+#### Initial clone of the WOT-terms.wiki repo to local
+
+```
+git clone https://github.com/weboftrust/WOT-terms.wiki.git
+cd WOT-terms.wiki
+git remote get-url origin
+ls
+```
+
+<img src="./images/wiki-repo-ls.png" width="400" alt="wiki-repo-ls-result" />
+
+#### Refresh the WOT-terms.wiki repo to local
+
+```
+git pull origin master
+```
+
+### Copy the WebofTrust glossary resources into the Docusaurus file structure
+
+To able to generate a tailor made explanation site we use two inputs (see full list of inputs [here](#input)):
+
+1. The WebofTrust glossary locally (all the .md files pulled from [Weboftrust wiki](https://github.com/WebOfTrust/WOT-terms/wiki)
+2. Terms WOT manage (xls or csv) table, currently maintained in Google Sheets (mid 2023)
+
+
+Step into the Docusaurus dir structure to `WOT-terms/docs/terms` 
+and execute the command `cp ../../../WOT-terms.wiki/*  .` to finish what we'd like to achieve: Copy the glossary resources into the Docusaurus file structure.
+
+### Script YYYYYYY to put WOT-terms sheet into JSON structure
+
+| TBW by creator Kor |
+- it reads the input file (2.) per line.
+- each row describes a term and its resource file
+- we create a proper file name
+- we try to match the terms in the ToIP glossary resources and bind them
+
+Docusaurus takes care of
+- writing `.md` files with Front matter code and includes
+
+### Constraint on WOT-terms sheet
+Columns
+- key
+- (WWWWW-key) multiple foreign keys
+- term
+- text
+- level
+- link
+- (Cat-CCCC) multiple categories
+
+**key** needs to be unique and once established it should not change.
+**Term**s are words used in the resource, you can provide a **link** to more explanation, mainly to the [ACDC glossary](https://github.com/trustoverip/acdc/wiki/). Then the **level** of understanding at which this term might need explanation, and finally a _brief explanation_ in field **text** of the term in the first column.
+
+#### Level
+
+Since KERI and ACDC education start off at the level of SSI-expert, a _beginner_ is not a layman, but somebody with a good common understanding of IT and digital identity.
+
+- 1=general digital identity expert
+- 2=advanced self-sovereign identity expert
+- 3=autonomic identifier & KERI experts
+
+
+#### Github Repo
+
+Push the locally updated files to the remote WebofTrust repo:
+
+```
+git status
+git add .
+git commit -m "update the WebofTrust glossary"
+git push <remote> gh-pages
+```
+
+#### Static pages generator
+
+The push will activate Github Actions and the resources will be input to a static site generator.
+
+## Result
+
+This is the Github pages result from the step by step above
+
+https://weboftrust.github.io/WOT-terms/glossary.html
diff --git a/docs/Terms/glossary/GAR.md b/docs/Terms/glossary/GAR.md
diff --git a/docs/Terms/glossary/byzantine-agreement.md b/docs/Terms/glossary/byzantine-agreement.md
diff --git a/docs/Terms/glossary/cesride.md b/docs/Terms/glossary/cesride.md
diff --git a/docs/Terms/glossary/contingent-disclosure.md b/docs/Terms/glossary/contingent-disclosure.md
diff --git a/docs/Terms/glossary/credential.md b/docs/Terms/glossary/credential.md
diff --git a/docs/Terms/glossary/intro.md b/docs/Terms/glossary/intro.md
diff --git a/docs/Terms/glossary/run-off-the-crud.md b/docs/Terms/glossary/run-off-the-crud.md
diff --git a/docs/Terms/glossary/verifiable-data-structure.md b/docs/Terms/glossary/verifiable-data-structure.md
diff --git a/docs/Terms/glossary/ACDC.md → docs/glossary/ACDC.md b/docs/Terms/glossary/ACDC.md → docs/glossary/ACDC.md
diff --git a/docs/Terms/glossary/ADC.md → docs/glossary/ADC.md b/docs/Terms/glossary/ADC.md → docs/glossary/ADC.md
diff --git a/docs/Terms/glossary/AID.md → docs/glossary/AID.md b/docs/Terms/glossary/AID.md → docs/glossary/AID.md
diff --git a/docs/Terms/glossary/AN.md → docs/glossary/AN.md b/docs/Terms/glossary/AN.md → docs/glossary/AN.md
diff --git a/docs/Terms/glossary/APC.md → docs/glossary/APC.md b/docs/Terms/glossary/APC.md → docs/glossary/APC.md
diff --git a/docs/Terms/glossary/API.md → docs/glossary/API.md b/docs/Terms/glossary/API.md → docs/glossary/API.md
diff --git a/docs/Terms/glossary/AVR.md → docs/glossary/AVR.md b/docs/Terms/glossary/AVR.md → docs/glossary/AVR.md
diff --git a/docs/Terms/glossary/BADA.md → docs/glossary/BADA.md b/docs/Terms/glossary/BADA.md → docs/glossary/BADA.md
diff --git a/docs/Terms/glossary/BFT.md → docs/glossary/BFT.md b/docs/Terms/glossary/BFT.md → docs/glossary/BFT.md
diff --git a/docs/Terms/glossary/CESR.md → docs/glossary/CESR.md b/docs/Terms/glossary/CESR.md → docs/glossary/CESR.md
diff --git a/docs/Terms/glossary/CLC.md → docs/glossary/CLC.md b/docs/Terms/glossary/CLC.md → docs/glossary/CLC.md
diff --git a/docs/Terms/glossary/CRUD.md → docs/glossary/CRUD.md b/docs/Terms/glossary/CRUD.md → docs/glossary/CRUD.md
diff --git a/docs/Terms/glossary/CSPRNG.md → docs/glossary/CSPRNG.md b/docs/Terms/glossary/CSPRNG.md → docs/glossary/CSPRNG.md
diff --git a/docs/Terms/glossary/CT.md → docs/glossary/CT.md b/docs/Terms/glossary/CT.md → docs/glossary/CT.md
diff --git a/docs/Terms/glossary/DAG.md → docs/glossary/DAG.md b/docs/Terms/glossary/DAG.md → docs/glossary/DAG.md
diff --git a/docs/Terms/glossary/DAR.md → docs/glossary/DAR.md b/docs/Terms/glossary/DAR.md → docs/glossary/DAR.md
diff --git a/docs/Terms/glossary/DEL.md → docs/glossary/DEL.md b/docs/Terms/glossary/DEL.md → docs/glossary/DEL.md
diff --git a/docs/Terms/glossary/DHT.md → docs/glossary/DHT.md b/docs/Terms/glossary/DHT.md → docs/glossary/DHT.md
diff --git a/docs/Terms/glossary/DID.md → docs/glossary/DID.md b/docs/Terms/glossary/DID.md → docs/glossary/DID.md
diff --git a/docs/Terms/glossary/DKMI.md → docs/glossary/DKMI.md b/docs/Terms/glossary/DKMI.md → docs/glossary/DKMI.md
diff --git a/docs/Terms/glossary/DPKI.md → docs/glossary/DPKI.md b/docs/Terms/glossary/DPKI.md → docs/glossary/DPKI.md
diff --git a/docs/Terms/glossary/ECR.md → docs/glossary/ECR.md b/docs/Terms/glossary/ECR.md → docs/glossary/ECR.md
diff --git a/docs/Terms/glossary/FFI.md → docs/glossary/FFI.md b/docs/Terms/glossary/FFI.md → docs/glossary/FFI.md
diff --git a/docs/glossary/GAR.md b/docs/glossary/GAR.md
@@ -0,0 +1,3 @@
+## See
+[GLEIF authorized representative](gleif-authorized-representative)\
+[GLEIF Ecosystem Governance Framework v1.0 Glossary](https://www.gleif.org/media/pages/vlei/introducing-the-vlei-ecosystem-governance-framework/0349aa74c5-1678443743/2022-12-16_verifiable-lei-_vlei_-ecosystem-governance-framework-glossary_v1.0_final.pdf)
diff --git a/docs/Terms/glossary/GLEIF.md → docs/glossary/GLEIF.md b/docs/Terms/glossary/GLEIF.md → docs/glossary/GLEIF.md
diff --git a/docs/Terms/glossary/GLEIS.md → docs/glossary/GLEIS.md b/docs/Terms/glossary/GLEIS.md → docs/glossary/GLEIS.md
diff --git a/docs/Terms/glossary/GPG.md → docs/glossary/GPG.md b/docs/Terms/glossary/GPG.md → docs/glossary/GPG.md
diff --git a/docs/glossary/HSM.md b/docs/glossary/HSM.md
@@ -0,0 +1,2 @@
+## See
+[Hardware security model](hardware-security-module)
diff --git a/docs/Terms/glossary/Home.md → docs/glossary/Home.md b/docs/Terms/glossary/Home.md → docs/glossary/Home.md
diff --git a/docs/Terms/glossary/I-O.md → docs/glossary/I-O.md b/docs/Terms/glossary/I-O.md → docs/glossary/I-O.md
diff --git a/docs/Terms/glossary/IANA.md → docs/glossary/IANA.md b/docs/Terms/glossary/IANA.md → docs/glossary/IANA.md
diff --git a/docs/Terms/glossary/IPEX.md → docs/glossary/IPEX.md b/docs/Terms/glossary/IPEX.md → docs/glossary/IPEX.md
diff --git a/docs/Terms/glossary/JOSE.md → docs/glossary/JOSE.md b/docs/Terms/glossary/JOSE.md → docs/glossary/JOSE.md
diff --git a/docs/glossary/JSON.md b/docs/glossary/JSON.md
@@ -0,0 +1,3 @@
+## Definition
+JavaScript Object Notation. JSON is a [language-independent](https://en.wikipedia.org/wiki/Language-independent_specification) data format. It was derived from [JavaScript](https://en.wikipedia.org/wiki/JavaScript). It's an [open standard](https://en.wikipedia.org/wiki/Open_standard) [file format](https://en.wikipedia.org/wiki/File_format) and [data interchange](https://en.wikipedia.org/wiki/Electronic_data_interchange) format that uses [human-readable](https://en.wikipedia.org/wiki/Human-readable_medium) text to store and transmit data objects consisting of [attribute–value pairs](https://en.wikipedia.org/wiki/Attribute%E2%80%93value_pair) and [arrays](https://en.wikipedia.org/wiki/Array_data_type) (or other [serializable](https://en.wikipedia.org/wiki/Serialization) values).\
+More on [source](https://en.wikipedia.org/wiki/JSON) Wikipedia
diff --git a/docs/Terms/glossary/KA2CE.md → docs/glossary/KA2CE.md b/docs/Terms/glossary/KA2CE.md → docs/glossary/KA2CE.md
diff --git a/docs/Terms/glossary/KAACE.md → docs/glossary/KAACE.md b/docs/Terms/glossary/KAACE.md → docs/glossary/KAACE.md
diff --git a/docs/Terms/glossary/KEL.md → docs/glossary/KEL.md b/docs/Terms/glossary/KEL.md → docs/glossary/KEL.md
diff --git a/docs/Terms/glossary/KERI.md → docs/glossary/KERI.md b/docs/Terms/glossary/KERI.md → docs/glossary/KERI.md
diff --git a/docs/glossary/KERISSE.md b/docs/glossary/KERISSE.md
@@ -0,0 +1,2 @@
+## See
+[KERI suite search engine](keri-suite-search-engine)
diff --git a/docs/Terms/glossary/KERL.md → docs/glossary/KERL.md b/docs/Terms/glossary/KERL.md → docs/glossary/KERL.md
diff --git a/docs/Terms/glossary/KID.md → docs/glossary/KID.md b/docs/Terms/glossary/KID.md → docs/glossary/KID.md
diff --git a/docs/Terms/glossary/KRAM.md → docs/glossary/KRAM.md b/docs/Terms/glossary/KRAM.md → docs/glossary/KRAM.md
diff --git a/docs/Terms/glossary/LEI.md → docs/glossary/LEI.md b/docs/Terms/glossary/LEI.md → docs/glossary/LEI.md
diff --git a/docs/glossary/LLM.md b/docs/glossary/LLM.md
@@ -0,0 +1 @@
+## See [Large Language Model](large-language-model)
diff --git a/docs/Terms/glossary/LoA.md → docs/glossary/LoA.md b/docs/Terms/glossary/LoA.md → docs/glossary/LoA.md
diff --git a/docs/Terms/glossary/LoC.md → docs/glossary/LoC.md b/docs/Terms/glossary/LoC.md → docs/glossary/LoC.md
diff --git a/docs/Terms/glossary/NFT.md → docs/glossary/NFT.md b/docs/Terms/glossary/NFT.md → docs/glossary/NFT.md
diff --git a/docs/Terms/glossary/OOBI.md → docs/glossary/OOBI.md b/docs/Terms/glossary/OOBI.md → docs/glossary/OOBI.md
diff --git a/docs/Terms/glossary/OOR.md → docs/glossary/OOR.md b/docs/Terms/glossary/OOR.md → docs/glossary/OOR.md
diff --git a/docs/Terms/glossary/P2P.md → docs/glossary/P2P.md b/docs/Terms/glossary/P2P.md → docs/glossary/P2P.md
diff --git a/docs/Terms/glossary/PGP.md → docs/glossary/PGP.md b/docs/Terms/glossary/PGP.md → docs/glossary/PGP.md
diff --git a/docs/glossary/PID.md b/docs/glossary/PID.md
@@ -0,0 +1,2 @@
+## See
+[percolated information discovery](percolated-information-discovery)
diff --git a/docs/Terms/glossary/PKI.md → docs/glossary/PKI.md b/docs/Terms/glossary/PKI.md → docs/glossary/PKI.md
diff --git a/docs/Terms/glossary/PRNG.md → docs/glossary/PRNG.md b/docs/Terms/glossary/PRNG.md → docs/glossary/PRNG.md
diff --git a/docs/Terms/glossary/PTEL.md → docs/glossary/PTEL.md b/docs/Terms/glossary/PTEL.md → docs/glossary/PTEL.md
diff --git a/docs/Terms/glossary/QAR.md → docs/glossary/QAR.md b/docs/Terms/glossary/QAR.md → docs/glossary/QAR.md
diff --git a/docs/Terms/glossary/QVI.md → docs/glossary/QVI.md b/docs/Terms/glossary/QVI.md → docs/glossary/QVI.md
diff --git a/docs/Terms/glossary/RUN.md → docs/glossary/RUN.md b/docs/Terms/glossary/RUN.md → docs/glossary/RUN.md
diff --git a/docs/Terms/glossary/SAD.md → docs/glossary/SAD.md b/docs/Terms/glossary/SAD.md → docs/glossary/SAD.md
diff --git a/docs/Terms/glossary/SAID.md → docs/glossary/SAID.md b/docs/Terms/glossary/SAID.md → docs/glossary/SAID.md
diff --git a/docs/Terms/glossary/SATP.md → docs/glossary/SATP.md b/docs/Terms/glossary/SATP.md → docs/glossary/SATP.md
diff --git a/docs/Terms/glossary/SCID.md → docs/glossary/SCID.md b/docs/Terms/glossary/SCID.md → docs/glossary/SCID.md
diff --git a/docs/glossary/SKRAP.md b/docs/glossary/SKRAP.md
@@ -0,0 +1,2 @@
+## See
+[Signify/KERIA Request Authentication Protocol](signify-keria-request-authentication-protocol)
diff --git a/docs/Terms/glossary/SKWA.md → docs/glossary/SKWA.md b/docs/Terms/glossary/SKWA.md → docs/glossary/SKWA.md
diff --git a/docs/glossary/SPAC.md b/docs/glossary/SPAC.md
@@ -0,0 +1,2 @@
+## See
+[Secure Private Authentic Confidentiality](secure-private-authentic-confidentiality)
diff --git a/docs/Terms/glossary/SSI.md → docs/glossary/SSI.md b/docs/Terms/glossary/SSI.md → docs/glossary/SSI.md
diff --git a/docs/Terms/glossary/TCP.md → docs/glossary/TCP.md b/docs/Terms/glossary/TCP.md → docs/glossary/TCP.md
diff --git a/docs/Terms/glossary/TEL.md → docs/glossary/TEL.md b/docs/Terms/glossary/TEL.md → docs/glossary/TEL.md
diff --git a/docs/glossary/TOAD.md b/docs/glossary/TOAD.md
@@ -0,0 +1,2 @@
+## See
+[threshold of accountable duplicity](threshold-of-accountable-duplicity)
diff --git a/docs/Terms/glossary/UI.md → docs/glossary/UI.md b/docs/Terms/glossary/UI.md → docs/glossary/UI.md
diff --git a/docs/Terms/glossary/URL.md → docs/glossary/URL.md b/docs/Terms/glossary/URL.md → docs/glossary/URL.md
diff --git a/docs/Terms/glossary/VC-TEL.md → docs/glossary/VC-TEL.md b/docs/Terms/glossary/VC-TEL.md → docs/glossary/VC-TEL.md
diff --git a/docs/Terms/glossary/VC.md → docs/glossary/VC.md b/docs/Terms/glossary/VC.md → docs/glossary/VC.md
diff --git a/docs/Terms/glossary/VDS.md → docs/glossary/VDS.md b/docs/Terms/glossary/VDS.md → docs/glossary/VDS.md
diff --git a/docs/Terms/glossary/XBRL.md → docs/glossary/XBRL.md b/docs/Terms/glossary/XBRL.md → docs/glossary/XBRL.md
diff --git a/docs/Terms/glossary/agency.md → docs/glossary/agency.md b/docs/Terms/glossary/agency.md → docs/glossary/agency.md
@@ -1,2 +1,2 @@
 ## Definition
-Agents can be people, edge computers and the functionality within [wallets](https://github.com/trustoverip/acdc/wiki/_new#digital-identity-wallet). The service an agent offers is agency.
+Agents can be people, edge computers and the functionality within [wallets](https://github.com/trustoverip/acdc/wiki/_new#digital-identity-wallet). The service an agent offers is agency.
diff --git a/docs/Terms/glossary/agent.md → docs/glossary/agent.md b/docs/Terms/glossary/agent.md → docs/glossary/agent.md
diff --git a/docs/Terms/glossary/ambient-verifiability.md → docs/glossary/ambient-verifiability.md b/docs/Terms/glossary/ambient-verifiability.md → docs/glossary/ambient-verifiability.md
diff --git a/.../Terms/glossary/append-only-event-logs.md → docs/glossary/append-only-event-logs.md b/.../Terms/glossary/append-only-event-logs.md → docs/glossary/append-only-event-logs.md
diff --git a/...sary/application-programming-interface.md → ...sary/application-programming-interface.md b/...sary/application-programming-interface.md → ...sary/application-programming-interface.md
@@ -2,5 +2,6 @@
 An application programming interface (API) is a way for two or more [computer programs](https://en.wikipedia.org/wiki/Computer_program) to communicate with each other. It is a type of software [interface](https://en.wikipedia.org/wiki/Interface_(computing)), offering a service to other pieces of [software](https://en.wikipedia.org/wiki/Software). 
 
 ## API specification
-A document or standard that describes how to build or use such a connection or interface is called an API specification. A computer system that meets this standard is said to implement or expose an API. The term API may refer either to the specification or to the implementation.\
+A document or standard that describes how to build or use such a connection or interface is called an API specification. A computer system that meets this standard is said to implement or expose an API. The term API may refer either to the specification or to the implementation.
+
 More on [source](https://en.wikipedia.org/wiki/API) Wikipedia.
diff --git a/...ssary/authentic-chained-data-container.md → ...ssary/authentic-chained-data-container.md b/...ssary/authentic-chained-data-container.md → ...ssary/authentic-chained-data-container.md
diff --git a/...erms/glossary/authentic-data-container.md → docs/glossary/authentic-data-container.md b/...erms/glossary/authentic-data-container.md → docs/glossary/authentic-data-container.md
diff --git a/...ms/glossary/authentic-provenance-chain.md → docs/glossary/authentic-provenance-chain.md b/...ms/glossary/authentic-provenance-chain.md → docs/glossary/authentic-provenance-chain.md
diff --git a/docs/Terms/glossary/authentic-web.md → docs/glossary/authentic-web.md b/docs/Terms/glossary/authentic-web.md → docs/glossary/authentic-web.md
diff --git a/docs/Terms/glossary/authenticity.md → docs/glossary/authenticity.md b/docs/Terms/glossary/authenticity.md → docs/glossary/authenticity.md
diff --git a/docs/Terms/glossary/authoritative.md → docs/glossary/authoritative.md b/docs/Terms/glossary/authoritative.md → docs/glossary/authoritative.md
diff --git a/docs/Terms/glossary/authority.md → docs/glossary/authority.md b/docs/Terms/glossary/authority.md → docs/glossary/authority.md
diff --git a/docs/Terms/glossary/authorization.md → docs/glossary/authorization.md b/docs/Terms/glossary/authorization.md → docs/glossary/authorization.md
diff --git a/...lossary/authorized-vlei-representative.md → ...lossary/authorized-vlei-representative.md b/...lossary/authorized-vlei-representative.md → ...lossary/authorized-vlei-representative.md
diff --git a/...s/glossary/autonomic-computing-systems.md → docs/glossary/autonomic-computing-systems.md b/...s/glossary/autonomic-computing-systems.md → docs/glossary/autonomic-computing-systems.md
diff --git a/docs/Terms/glossary/autonomic-identifier.md → docs/glossary/autonomic-identifier.md b/docs/Terms/glossary/autonomic-identifier.md → docs/glossary/autonomic-identifier.md
diff --git a/...rms/glossary/autonomic-identity-system.md → docs/glossary/autonomic-identity-system.md b/...rms/glossary/autonomic-identity-system.md → docs/glossary/autonomic-identity-system.md
diff --git a/docs/Terms/glossary/autonomic-namespace.md → docs/glossary/autonomic-namespace.md b/docs/Terms/glossary/autonomic-namespace.md → docs/glossary/autonomic-namespace.md
diff --git a/docs/Terms/glossary/backer.md → docs/glossary/backer.md b/docs/Terms/glossary/backer.md → docs/glossary/backer.md
diff --git a/docs/Terms/glossary/base-media-type.md → docs/glossary/base-media-type.md b/docs/Terms/glossary/base-media-type.md → docs/glossary/base-media-type.md
diff --git a/docs/Terms/glossary/base64.md → docs/glossary/base64.md b/docs/Terms/glossary/base64.md → docs/glossary/base64.md
diff --git a/docs/glossary/bespoke-credential.md b/docs/glossary/bespoke-credential.md
@@ -0,0 +1,16 @@
+## Definition
+It's an [issuance](issuance) of the disclosure or presentation of other ACDCs. _Bespoke_ means _Custom_ or _tailor made_.
+A bespoke credential serves as an on-the-fly contract with the issuee; it's a self-referencing and self-contained contract between the issuer and the verifier. Mind you, here the issuer and issuee are merely the discloser and disclosee of another (set of) ACDC(s).
+
+## Example
+If I want consent terms attached to a presentation of an (set of) ACDC(s).\
+Consider a disclosure-specific ACDC, aka tailor made, custom or bespoke. The Issuer is the Discloser, the Issuee is the Disclosee. The rule section includes a context-specific (anti) assimilation clause that limits the use of the information to a single one-time usage purpose, that is for example, admittance to a restaurant. The ACDC includes an edge that references some other ACDC that may for example be a coupon or gift card. The attribute section could include the date and place of admittance.\
+For the code of this example, see this [section 11.1 in Github](https://weboftrust.github.io/ietf-acdc/draft-ssmith-acdc.html#section-11.1)
+
+## Advantage
+We can use all the tools available for issuance and presentation we already have.
+
+## How the process work
+Similar to a presentation exchange, a verifier will first be asked for what they are looking for, secondly the discloser creates the dataset and publishes only the structure and the fields. To accomplish this, thirdly a compact ACDC will be issued (you publish the fields, not the content) and then issuer asks to sign it first. After signing, the disclosee can get the content associated with the on-the-fly contract.
+
+More at [Github source](https://weboftrust.github.io/ietf-acdc/draft-ssmith-acdc.html#name-disclosure-specific-bespoke) 
diff --git a/...st-available-data-acceptance-mechanism.md → ...st-available-data-acceptance-mechanism.md b/...st-available-data-acceptance-mechanism.md → ...st-available-data-acceptance-mechanism.md
diff --git a/docs/Terms/glossary/binding.md → docs/glossary/binding.md b/docs/Terms/glossary/binding.md → docs/glossary/binding.md
diff --git a/docs/Terms/glossary/blake3.md → docs/glossary/blake3.md b/docs/Terms/glossary/blake3.md → docs/glossary/blake3.md
diff --git a/docs/Terms/glossary/blind-oobi.md → docs/glossary/blind-oobi.md b/docs/Terms/glossary/blind-oobi.md → docs/glossary/blind-oobi.md
diff --git a/...s/glossary/blinded-revocation-registry.md → docs/glossary/blinded-revocation-registry.md b/...s/glossary/blinded-revocation-registry.md → docs/glossary/blinded-revocation-registry.md
@@ -1,6 +1,7 @@
 ## Definition
+The current state of a [transaction event log](transaction-event-log) (TEL) **be hidden or blinded** such that _the only way_ for a potential verifier of the state to observe that state is _when the controller of a designated AID discloses it_ at the time of presentation.
 
-{BE CAREFUL, JUST TEXT SNIPPETS TYPED IN FROM A CONVERSATION }
+{BE CAREFUL WITH THE REST, JUST TEXT SNIPPETS TYPED IN FROM A CONVERSATION }
 
 No information can be obtained via a [rainbow table attack](rainbow-table-attack) because the hash has enough [entropy](entropy) added to it.
 

diff --git a/docs/Terms/glossary/branch.md → docs/glossary/branch.md b/docs/Terms/glossary/branch.md → docs/glossary/branch.md
diff --git a/docs/glossary/byzantine-agreement.md b/docs/glossary/byzantine-agreement.md
@@ -0,0 +1,13 @@
+## Definition
+(non PoW) Byzantine Agreement is [Byzantine fault tolerance](byzantine-fault-tolerance) of distributed computing systems that enable them to come to consensus despite arbitrary behavior from a fraction of the nodes in the network. BA consensus makes no assumptions about the behavior of nodes in the system. Practical Byzantine Fault Tolerance (pBFT) is the prototypical model for Byzantine agreement, and it can reach consensus fast and efficiently while concurrently decoupling consensus from resources (i.e., financial stake in PoS or electricity in PoW).
+
+## Stellar
+[More](https://blockonomi.com/stellar-consensus-protocol/) about the Stellar consensus protocol
+
+```
+"What if PBFT and Stellar had a baby?
+that was missing liveness and total ordering 
+but had safety and was completely decentralized, portable, and permission-less? 
+It would be named KERI."
+SamMSmith
+```
diff --git a/...rms/glossary/byzantine-fault-tolerance.md → docs/glossary/byzantine-fault-tolerance.md b/...rms/glossary/byzantine-fault-tolerance.md → docs/glossary/byzantine-fault-tolerance.md
@@ -1,5 +1,5 @@
 ## Definition
-A Byzantine fault (also interactive consistency, source congruency, error avalanche, Byzantine agreement problem, Byzantine generals problem, and Byzantine failure) is a condition of a computer system, particularly distributed computing systems, where components may fail and there is imperfect information on whether a component has failed. The term takes its name from an allegory, the "Byzantine Generals Problem", developed to describe a situation in which, in order to avoid catastrophic failure of the system, the system's actors must agree on a concerted strategy, but some of these actors are unreliable.
+A Byzantine fault (also interactive consistency, source congruency, error avalanche, [Byzantine agreement](byzantine-agreement) problem, Byzantine generals problem, and Byzantine failure) is a condition of a computer system, particularly distributed computing systems, where components may fail and there is imperfect information on whether a component has failed. The term takes its name from an allegory, the "Byzantine Generals Problem", developed to describe a situation in which, in order to avoid catastrophic failure of the system, the system's actors must agree on a concerted strategy, but some of these actors are unreliable.
 In a Byzantine fault, a component such as a server can inconsistently appear both failed and functioning to failure-detection systems, presenting different symptoms to different observers. It is difficult for the other components to declare it failed and shut it out of the network, because they need to first reach a consensus regarding which component has failed in the first place.
 Byzantine fault tolerance (BFT) is the dependability of a fault-tolerant computer system to such conditions.
 

diff --git a/...erms/glossary/certificate-transparency.md → docs/glossary/certificate-transparency.md b/...erms/glossary/certificate-transparency.md → docs/glossary/certificate-transparency.md
diff --git a/docs/Terms/glossary/cesr-proof-signatures.md → docs/glossary/cesr-proof-signatures.md b/docs/Terms/glossary/cesr-proof-signatures.md → docs/glossary/cesr-proof-signatures.md
diff --git a/docs/glossary/cesride.md b/docs/glossary/cesride.md
@@ -0,0 +1,23 @@
+## Definition
+is concerned with parsing CESR primitives.
+
+Cesride is built from cryptographic primitives that are named clearly and concisely. There are:
+* [Diger](diger)
+* [Verfer](verfer)
+* [Signer](signer) 
+* [Siger](siger)
+* [Cigar](cigar)
+* [Salter](salter)
+
+Each primitive will have methods attached to it that permit one to generate and parse the qualified base2 or [base64](base64) representation. Common methods you'll find:
+
+* `.qb64()` - qualified base-64 representation of cryptographic material as a string
+* `.qb64b()` - qualified base-64 representation of cryptographic material as octets (bytes)
+* `.qb2()` - qualified base-2 representation of cryptographic material as octets (bytes)
+* `.code()` - qualifying code (describes the type of cryptographic material)
+* `.raw()` - raw cryptographic material (unqualified) as octets (bytes)
+
+[Source](https://github.com/WebOfTrust/cesride#terminology) by Jason Colburne
+
+## Related
+[Parside](parside)
diff --git a/...ms/glossary/chain-link-confidentiality.md → docs/glossary/chain-link-confidentiality.md b/...ms/glossary/chain-link-confidentiality.md → docs/glossary/chain-link-confidentiality.md
@@ -6,3 +6,7 @@ This is the primary mechanism of granting digital data rights through binding in
 ## Contrast
 Disclosures via [Presentations Exchanges](presentation-exchange) may be contractually protected by Chain-Link Confidentiality (i.e. a Chain-Link Confidential disclosure). The chaining in this case is different from the chaining described above between Issuances in a [DAG](directed-acyclic-graph) of chained Issuances. Chain-link confidentiality, in contrast, chains together a sequence of Disclosees.\
 More info at [source](https://github.com/WebOfTrust/ietf-ipex/blob/main/draft-ssmith-ipex.md#chain-link-confidentiality)
+
+## Article Woodrow Hartzog
+An important article on the topic can be found here:\
+[Woodrow Hartzog “Chain-Link Confidentiality”](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2045818)
diff --git a/docs/Terms/glossary/chain-of-custody.md → docs/glossary/chain-of-custody.md b/docs/Terms/glossary/chain-of-custody.md → docs/glossary/chain-of-custody.md
diff --git a/docs/glossary/cigar.md b/docs/glossary/cigar.md
@@ -0,0 +1,3 @@
+## Definition
+An **_un_**[indexed signature](indexed-signature).\
+[Source](https://github.com/WebOfTrust/cesride#terminology) by Jason Colburne
diff --git a/docs/Terms/glossary/claim.md → docs/glossary/claim.md b/docs/Terms/glossary/claim.md → docs/glossary/claim.md
diff --git a/docs/Terms/glossary/clone.md → docs/glossary/clone.md b/docs/Terms/glossary/clone.md → docs/glossary/clone.md
diff --git a/docs/Terms/glossary/cloud-agent.md → docs/glossary/cloud-agent.md b/docs/Terms/glossary/cloud-agent.md → docs/glossary/cloud-agent.md
diff --git a/docs/Terms/glossary/code-table-selector.md → docs/glossary/code-table-selector.md b/docs/Terms/glossary/code-table-selector.md → docs/glossary/code-table-selector.md
diff --git a/docs/Terms/glossary/code-table.md → docs/glossary/code-table.md b/docs/Terms/glossary/code-table.md → docs/glossary/code-table.md
diff --git a/...rms/glossary/cold-start-stream-parsing.md → docs/glossary/cold-start-stream-parsing.md b/...rms/glossary/cold-start-stream-parsing.md → docs/glossary/cold-start-stream-parsing.md
diff --git a/docs/Terms/glossary/collective-signature.md → docs/glossary/collective-signature.md b/docs/Terms/glossary/collective-signature.md → docs/glossary/collective-signature.md
diff --git a/docs/Terms/glossary/collision.md → docs/glossary/collision.md b/docs/Terms/glossary/collision.md → docs/glossary/collision.md
diff --git a/docs/Terms/glossary/compact-variant.md → docs/glossary/compact-variant.md b/docs/Terms/glossary/compact-variant.md → docs/glossary/compact-variant.md
diff --git a/...y/complementary-integrity-verification.md → ...y/complementary-integrity-verification.md b/...y/complementary-integrity-verification.md → ...y/complementary-integrity-verification.md
diff --git a/docs/Terms/glossary/composability.md → docs/glossary/composability.md b/docs/Terms/glossary/composability.md → docs/glossary/composability.md
diff --git a/...posable-event-streaming-representation.md → ...posable-event-streaming-representation.md b/...posable-event-streaming-representation.md → ...posable-event-streaming-representation.md
diff --git a/docs/Terms/glossary/composable.md → docs/glossary/composable.md b/docs/Terms/glossary/composable.md → docs/glossary/composable.md
diff --git a/docs/Terms/glossary/concatenation.md → docs/glossary/concatenation.md b/docs/Terms/glossary/concatenation.md → docs/glossary/concatenation.md
diff --git a/...se-binary-object-representation-(CBOR).md → ...se-binary-object-representation-(CBOR).md b/...se-binary-object-representation-(CBOR).md → ...se-binary-object-representation-(CBOR).md
diff --git a/docs/Terms/glossary/configuration-files.md → docs/glossary/configuration-files.md b/docs/Terms/glossary/configuration-files.md → docs/glossary/configuration-files.md
diff --git a/docs/Terms/glossary/consensus-mechanism.md → docs/glossary/consensus-mechanism.md b/docs/Terms/glossary/consensus-mechanism.md → docs/glossary/consensus-mechanism.md
diff --git a/...erms/glossary/content-addressable-hash.md → docs/glossary/content-addressable-hash.md b/...erms/glossary/content-addressable-hash.md → docs/glossary/content-addressable-hash.md
diff --git a/.../Terms/glossary/contextual-linkability.md → docs/glossary/contextual-linkability.md b/.../Terms/glossary/contextual-linkability.md → docs/glossary/contextual-linkability.md
diff --git a/docs/glossary/contingent-disclosure.md b/docs/glossary/contingent-disclosure.md
@@ -0,0 +1,4 @@
+## Definition
+[Chain link confidentiality](chain-link-confidentiality) is a form of contingent disclosure.
+
+{TBW prio 1}
diff --git a/...ary/contractually-protected-disclosure.md → ...ary/contractually-protected-disclosure.md b/...ary/contractually-protected-disclosure.md → ...ary/contractually-protected-disclosure.md
diff --git a/docs/Terms/glossary/control-authority.md → docs/glossary/control-authority.md b/docs/Terms/glossary/control-authority.md → docs/glossary/control-authority.md
@@ -13,4 +13,4 @@ How these events are ordered and their dependence on previous operations is impo
 ## Change control authority
 In the 2022 implementation of [KeriPy](keripy) two [rotations](key-rotation) were required to _change_ control authority.
 In new rotation rules, you can rotate to new keys that aren't in the prior next key [digests](digest). You just need to reach the appropriate thresholds of [prior next threshold](prior-next-threshold) and [current signing threshold](current-signing-threshold). So you now only need one rotation to change control authority.\
-**Note**: This change was the forcing function to require [dual index codes](dual-index-codes) in CESR.
+**Note**: This change was the forcing function to require [dual indexed codes](dual-indexed-codes) in CESR.
diff --git a/docs/Terms/glossary/controller.md → docs/glossary/controller.md b/docs/Terms/glossary/controller.md → docs/glossary/controller.md
diff --git a/docs/Terms/glossary/coroutines.md → docs/glossary/coroutines.md b/docs/Terms/glossary/coroutines.md → docs/glossary/coroutines.md
diff --git a/docs/Terms/glossary/correlation.md → docs/glossary/correlation.md b/docs/Terms/glossary/correlation.md → docs/glossary/correlation.md
diff --git a/docs/Terms/glossary/count-code.md → docs/glossary/count-code.md b/docs/Terms/glossary/count-code.md → docs/glossary/count-code.md
diff --git a/docs/glossary/credential.md b/docs/glossary/credential.md
@@ -0,0 +1,9 @@
+## Definition
+
+Evidence of authority, status, rights, entitlement to privileges, or the like.\
+([source](https://github.com/trustoverip/tswg-acdc-specification/blob/main/draft-ssmith-acdc.md#introduction)) \
+A credential has its current state and a history, which is captured in a doc or a graph.
+
+## ACDC specific
+The credential is the whole graph.\
+The pointers in the doc that contain the whole graph are universally globally distributable references via the SAIDs. Whereas in other credential systems pointers are only local in a credential doc.
diff --git a/docs/Terms/glossary/crypto-libraries.md → docs/glossary/crypto-libraries.md b/docs/Terms/glossary/crypto-libraries.md → docs/glossary/crypto-libraries.md
diff --git a/docs/Terms/glossary/cryptocurrency.md → docs/glossary/cryptocurrency.md b/docs/Terms/glossary/cryptocurrency.md → docs/glossary/cryptocurrency.md
diff --git a/...ossary/cryptographic-commitment-scheme.md → ...ossary/cryptographic-commitment-scheme.md b/...ossary/cryptographic-commitment-scheme.md → ...ossary/cryptographic-commitment-scheme.md
diff --git a/...Terms/glossary/cryptographic-primitive.md → docs/glossary/cryptographic-primitive.md b/...Terms/glossary/cryptographic-primitive.md → docs/glossary/cryptographic-primitive.md
diff --git a/.../Terms/glossary/cryptographic-strength.md → docs/glossary/cryptographic-strength.md b/.../Terms/glossary/cryptographic-strength.md → docs/glossary/cryptographic-strength.md
diff --git a/docs/Terms/glossary/cryptonym.md → docs/glossary/cryptonym.md b/docs/Terms/glossary/cryptonym.md → docs/glossary/cryptonym.md
diff --git a/docs/Terms/glossary/custodial-agent.md → docs/glossary/custodial-agent.md b/docs/Terms/glossary/custodial-agent.md → docs/glossary/custodial-agent.md
diff --git a/docs/Terms/glossary/custodial-rotation.md → docs/glossary/custodial-rotation.md b/docs/Terms/glossary/custodial-rotation.md → docs/glossary/custodial-rotation.md
diff --git a/docs/Terms/glossary/data-anchor.md → docs/glossary/data-anchor.md b/docs/Terms/glossary/data-anchor.md → docs/glossary/data-anchor.md
diff --git a/docs/glossary/dead-drop.md b/docs/glossary/dead-drop.md
@@ -0,0 +1,5 @@
+## Definition
+| TBW | 
+the presenter controls the disclosure so you can't re-identify the data
+
+Tech meet KERI [recording]() from minute 55, date June 29 2023
diff --git a/...erms/glossary/decentralized-identifier.md → docs/glossary/decentralized-identifier.md b/...erms/glossary/decentralized-identifier.md → docs/glossary/decentralized-identifier.md
diff --git a/.../Terms/glossary/decentralized-identity.md → docs/glossary/decentralized-identity.md b/.../Terms/glossary/decentralized-identity.md → docs/glossary/decentralized-identity.md
diff --git a/...tralized-key-management-infrastructure.md → ...tralized-key-management-infrastructure.md b/...tralized-key-management-infrastructure.md → ...tralized-key-management-infrastructure.md
diff --git a/docs/Terms/glossary/delegated-identifier.md → docs/glossary/delegated-identifier.md b/docs/Terms/glossary/delegated-identifier.md → docs/glossary/delegated-identifier.md
diff --git a/docs/Terms/glossary/delegation.md → docs/glossary/delegation.md b/docs/Terms/glossary/delegation.md → docs/glossary/delegation.md
diff --git a/docs/Terms/glossary/derivation-code.md → docs/glossary/derivation-code.md b/docs/Terms/glossary/derivation-code.md → docs/glossary/derivation-code.md
diff --git a/...y/designated-authorized-representative.md → ...y/designated-authorized-representative.md b/...y/designated-authorized-representative.md → ...y/designated-authorized-representative.md