resources
17 rows where type = "specification" sorted by date descending
This data as json, CSV (advanced)
Suggested facets: maintainer, last_checked, authors, via, has_abstract, has_summary, last_checked (date), date (date)
status 4
level 3
- normative 12
- implementer 3
- practitioner 2
evidence 2
type 1
- Specifications and glossaries · 17 ✖
access 1
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| kerione-verifiable-voice-protocol | Specifications and glossaries specification | Verifiable Voice Protocol | https://datatracker.ietf.org/doc/draft-hardman-verifiable-voice-protocol/ | Daniel Hardman (Provenant, Inc.) | changed within the last six months, or a live service active | 2026-10-14 | 2026-10-05 | 2026 | normative | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | An individual Internet-Draft (not adopted or endorsed by the IETF) defining the Verifiable Voice Protocol (VVP), which authenticates and authorizes organizations and individuals making or receiving telephone calls. A caller's signed passport travels in a SIP INVITE through STIR and cites a dossier of evidence built as ACDCs issued by KERI identifiers; the draft gives the roles, the passport fields and the verification algorithm. For implementers in telecommunications and verifiable calling. | Daniel Hardman (Provenant, Inc.) | draft-hardman-verifiable-voice-protocol-08 | keri.one KERI Resources page keri-one-resources | Verifiable Voice Protocol specifications/verifiable-voice-protocol | 1 | 1 | |||||||||||||||||
| hardman-canonical-quoted-text-cqt | Specifications and glossaries specification | Canonical Quoted Text (CQT) | https://dhh1128.github.io/canonical-quoted-text | Daniel Hardman | changed within the last six months, or a live service active | 2026-10-15 | 2026-08-24 | 2026 | normative | a specification or a requirement in one normative | anyone with the link public | A specification of an algorithm (cqt3.17) that puts text moving through chat, copy and paste, email and similar channels into a canonical form before hashing or signing, so that two copies can be judged the same if their outputs match byte for byte. It defines protected content (code, URIs) that passes through untouched, conformance vectors, and implementations in several languages. For developers who sign or verify quoted text. | Daniel Hardman | 3.17 | Codecraft Papers (Daniel Hardman's paper archive) hardman-papers | 1 | 0 | ||||||||||||||||||
| hardman-entviz-algorithm-specification | Specifications and glossaries specification | entviz: Algorithm Specification | https://dhh1128.github.io/entviz/spec | Daniel Hardman | changed within the last six months, or a live service active | 2026-10-15 | 2026-05-27 | 2026 | normative | a specification or a requirement in one normative | anyone with the link public | A specification for entviz, a way to render high-entropy values (cryptographic keys, signatures, identifiers, post-quantum keys) as images so that an untrained person can tell visually whether two values are the same. It covers input normalization, fingerprinting, grid and palette rules, overlays and conformance tiers. For implementers of key and identifier comparison in user interfaces. | Daniel Hardman | 18 | Codecraft Papers (Daniel Hardman's paper archive) hardman-papers | 1 | 0 | ||||||||||||||||||
| papers-keri-request-authentication-mechanism-kram | Specifications and glossaries specification | Keri Request Authentication Mechanism (KRAM) | https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/kram.md | Samuel M. Smith (attributed by the repository; the document names no author) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-03 | 2026 | implementer | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | A working design document for KRAM, a non-interactive method of authenticating requests signed with a KERI identifier's current key state, protecting against replay with datetime stamps and timeliness caches. It covers simple KRAM, as implemented in keripy, and a redesigned full KRAM with multi-signature support, cache types, databases and processing logic. For keripy implementers. | Samuel M. Smith (attributed by the repository; the document names no author) | 0.7.6 | SmithSamuelM/Papers (whitepapers and presentations) smith-papers | Keri Request Authentication Mechanism (KRAM) research/papers/papers-keri-request-authentication-mechanism-kram | 1 | 1 | |||||||||||||||||
| hardman-conventions-for-opaque-identifier-aliases-coia | Specifications and glossaries specification | COIA 2.0: Conventions for Opaque Identifier Aliases | https://dhh1128.github.io/coia | Daniel Hardman | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-08-28 | 2025 | normative | a specification or a requirement in one normative | anyone with the link public | A specification of a convention for human-readable labels (aliases) for opaque identifiers such as decentralized identifiers (DIDs), KERI autonomic identifiers (AIDs), keys and account numbers. It defines alias generation from three fields (who, role, scope), normalization, a flag registry for safety warnings, and matching. For developers of wallets, key managers and other tools that label identifiers. | Daniel Hardman | 2.0 | Codecraft Papers (Daniel Hardman's paper archive) hardman-papers | 1 | 0 | ||||||||||||||||||
| papers-tsp-cesr-implementation-details | Specifications and glossaries specification | TSP CESR Implementation Details | https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/TSP_CESR_Implementation.md | Samuel M. Smith (attributed by the repository; the document names no author) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-07 | 2025 | implementer | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | A technical proposal for encoding Trust Spanning Protocol (TSP) wrappers and payloads as Composable Event Streaming Representation (CESR) primitives and groups: open and closed modes for verifiable identifiers, the head, body and tail of the wrapper, hop and relationship formation payloads, and a proposed table for tunneling KERI and ACDC messages. For TSP and CESR implementers. | Samuel M. Smith (attributed by the repository; the document names no author) | SmithSamuelM/Papers (whitepapers and presentations) smith-papers | TSP CESR Implementation Details research/papers/papers-tsp-cesr-implementation-details | 1 | 1 | ||||||||||||||||||
| papers-acdc-specification-draft-0-3-2 | Specifications and glossaries specification | ACDC Specification | https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/ACDC_Spec.md | Samuel M. Smith | replaced by a named successor; kept for history superseded | 2026-10-15 | 2022-04 | 2022 | implementer | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | An early working draft (version 0.3.2) of the Authentic Chained Data Container (ACDC) specification, kept as a non-HackMD version: ACDC fields, compact and private variants, schema, disclosure mechanisms, the three-party exploitation model, chain-link confidentiality, and attribute, edge and rule sections. For readers tracing the history of the ACDC specification. | Samuel M. Smith | 0.3.2 | SmithSamuelM/Papers (whitepapers and presentations) smith-papers | 1 | 0 | ||||||||||||||||||
| keri-spec | Specifications and glossaries specification | KERI specification v1.0 | https://trustoverip.github.io/kswg-keri-specification/ | ToIP KERI Suite Working Group | changed within the last six months, or a live service active | 2026-11-04 | normative | a specification or a requirement in one normative | anyone with the link public | 0 | 0 | ||||||||||||||||||||||||
| acdc-spec | Specifications and glossaries specification | ACDC specification v1.0 | https://trustoverip.github.io/kswg-acdc-specification/ | ToIP KERI Suite Working Group | changed within the last six months, or a live service active | 2026-11-04 | normative | a specification or a requirement in one normative | anyone with the link public | The GitHub repository holding the Trust Over IP specification of Authentic Chained Data Containers (ACDC), rendered at trustoverip.github.io/kswg-acdc-specification. For implementers who need the normative ACDC text and its issue history. | keri.one KERI Resources page keri-one-resources | 1 | 0 | ||||||||||||||||||||||
| cesr-spec | Specifications and glossaries specification | CESR specification v1.0 | https://trustoverip.github.io/kswg-cesr-specification/ | ToIP KERI Suite Working Group | changed within the last six months, or a live service active | 2026-11-04 | normative | a specification or a requirement in one normative | anyone with the link public | 0 | 0 | ||||||||||||||||||||||||
| did-webs-spec | Specifications and glossaries specification | did:webs method specification | https://github.com/trustoverip/kswg-did-method-webs-specification | ToIP KSWG did:webs task force; editors Feairheller, Hardman, Smith, Byrd, Rayback, Bull | changed within the last six months, or a live service active | 2026-11-04 | normative | a specification or a requirement in one normative | anyone with the link public | 0 | 0 | ||||||||||||||||||||||||
| dossier-spec | Specifications and glossaries specification | Verifiable Dossiers | https://trustoverip.github.io/kswg-dossier-specification/ | ToIP KERI Suite Working Group | changed within the last six months, or a live service active | 2026-11-04 | normative | a specification or a requirement in one normative | anyone with the link public | 0 | 0 | ||||||||||||||||||||||||
| kerisuite-glossary | Specifications and glossaries specification | KERI Suite glossary (Spec-Up-T) | https://trustoverip.github.io/kerisuite-glossary/ | KSWG; editors Smith, Reed, van Cann | changed within the last six months, or a live service active | 2026-11-04 | normative | a specification or a requirement in one normative | anyone with the link public | 0 | 0 | ||||||||||||||||||||||||
| 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 | ||||||||||||||||||||
| kf-vlei-glossary | Specifications and glossaries specification | vLEI glossary, the KERI Foundation's repository (Spec-Up-T) | https://github.com/keri-foundation/vlei-glossary | KERI Foundation | not checked, or the page gives no date unknown | 2026-11-04 | practitioner | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | A KERI Foundation repository holding a Spec-Up-T glossary of 26 vLEI terms (the roles QVI (qualified vLEI issuer), QAR (qualified vLEI issuer authorized representative), GAR (legal entity authorized representative), DAR (designated authorized representative), OOR (official organizational role) and ECR (engagement context role), the credential governance frameworks, the issuer qualification terms), each pointing to the extended KERI glossary; its generated site still carries the Spec-Up-T starter pack's title and demo text. For readers who want the Foundation's own copy of the vLEI vocabulary; Henk van Cann's vlei-glossary repository (115 terms, author GLEIF.org in its configuration) is the fuller one. | 2025 | vlei.wiki vlei-wiki | 1 | 0 | |||||||||||||||||||||
| ietf-drafts | Specifications and glossaries specification | The IETF drafts (historical): ietf-keri, ietf-acdc, ietf-cesr-proof, ietf-said, ietf-oobi, ietf-ipex | https://github.com/WebOfTrust/ietf-keri | WebOfTrust | replaced by a named successor; kept for history superseded | 2026-11-04 | normative | a specification or a requirement in one normative | anyone with the link public | 0 | 0 | ||||||||||||||||||||||||
| ietf-did-keri | Specifications and glossaries specification | WebOfTrust/ietf-did-keri: the did:keri method draft | https://github.com/WebOfTrust/ietf-did-keri | WebOfTrust | no change in six to eighteen months; still correct quiet | 2026-11-02 | normative | a specification or a requirement in one normative | anyone with the link public | The WebOfTrust repository of the KERI DID method draft (draft-pfeairheller-did-keri). Its issues ask how the method relates to did:web, how DID resolution metadata is structured, and how a domain is anchored in an event log to track control. | 2022 | KERISSE, the KERI Suite Search Engine kerisse | 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);