resources
1 row where via = "keridoc" sorted by date descending
This data as json, CSV (advanced)
Suggested facets: last_checked (date)
type 1
level 1
access 1
year 0
| id | type | name | url | maintainer | status | last_checked | date ▲ | year | level | evidence | access | abstract | authors | series | chair | minutes | recording | media | decisions | version | language | license | release | pushed | depends | since | via | summary | note | has_abstract | has_summary | kind | sector | country | products |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| keriglos | Specifications and glossaries specification | KERIGlos, the WOT-terms glossary | https://weboftrust.github.io/WOT-terms/docs/category/glossary | Kor Dwarshuis and Henk van Cann, WebOfTrust | changed within the last six months, or a live service active | 2026-11-04 | practitioner | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | The glossary section of the WOT-terms site, which its repository titles KERIGlos: about 560 term pages on the KERI Suite, each with a definition, its source and an explanation, linked to the Trust over IP specifications and read by the Kerific extension; Apache 2.0 with the repository. For readers who want the extended, community-written definition behind a term in the suite glossary (kerisuite-glossary). | Apache-2.0 | 2022 | KERIDoc, the documentation site keridoc | 1 | 0 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE resources (id TEXT PRIMARY KEY, type TEXT REFERENCES types(id), name TEXT, url TEXT, maintainer TEXT,
status TEXT REFERENCES statuses(id), last_checked TEXT, date TEXT, year INTEGER, level TEXT REFERENCES levels(id),
evidence TEXT REFERENCES evidence(id), access TEXT REFERENCES access(id), abstract TEXT, authors TEXT, series TEXT,
chair TEXT, minutes TEXT, recording TEXT, media TEXT, decisions TEXT, version TEXT, language TEXT, license TEXT,
release TEXT, pushed TEXT, depends TEXT, since TEXT, via TEXT REFERENCES resources(id),
summary TEXT REFERENCES notes(path), note TEXT, has_abstract INTEGER, has_summary INTEGER,
kind TEXT REFERENCES kinds(id), sector TEXT REFERENCES sectors(id), country TEXT, products TEXT);