§ KERI Suite Glossary

Specification Status: Public Review Draft 01 (PR1)

Latest Draft:

Editors:

Contributors:

Kor Dwarshuis, Blockchainbird

Contributors:

Participate:

§ Status

This is the first public review draft of the KERI Main Glossary. It is also the first version published using the Spec-Up-T specification editing utility based on Spec-Up specification editing utility developed by the Decentralized Identity Foundation.

§ Copyright Notice

This specification is subject to the OWF Contributor License Agreement 1.0 - Copyright available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owf-contributor-license-agreement-1-0-copyright.

These terms are inherited from the KERI Suite Working Group at the Trust over IP (ToIP) Foundation. Working Group Charter

§ Terms of Use

These materials are made available under and are subject to the OWF CLA 1.0 - Copyright & Patent license. Any source code is made available under the Apache 2.0 license.

THESE MATERIALS ARE PROVIDED “AS IS.” The Trust Over IP Foundation, established as the Joint Development Foundation Projects, LLC, Trust Over IP Foundation Series (“ToIP”), and its members and contributors (each of ToIP, its members and contributors, a “ToIP Party”) expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to the materials. The entire risk as to implementing or otherwise using the materials is assumed by the implementer and user.

IN NO EVENT WILL ANY ToIP PARTY BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THESE MATERIALS, ANY DELIVERABLE OR THE ToIP GOVERNING AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

§ Introduction

The KERI Main Glossary is a deliverable of the ToIP KERI Suite Working Group (KSWG). Its purpose is to promote shared understanding of terms and concepts across the many different working groups, communities, enterprises, and ecosystems who are collaborating to develop and deploy decentralized digital trust infrastructure.

Contributions and feedback are encouraged from any stakeholder in this area of terminology.

§ Linking to this Glossary

This glossary is designed to be both human and machine readable. All terms are listed alphabetically; acronyms are listed separately and linked to the fully expanded terms. Document authors can link directly to any term using standard web links and anchors following this syntax:

https://trustoverip.github.io/kerisuite-glossary#term:xxxxx

Where xxxxx is the term as it appears in the glossary, with any spaces are replaced by en-dashes (hyphens). For example, a link to the term self-certifying identifer would be:

https://trustoverip.github.io/kerisuite-glossary#self-certifiying-identifier

A specification document written using the Trustoverip’s open source Spec-Up-T environment documented in the Spec-Up-T manual, originally based on Decentralized Identity Foundation’s open source Spec-Up editor.

The tool may create special external references to terms in this glossary using the Spec-Up xref and the tref tags following this syntax:

[ [xref: glossary, xxxxx] ] and [ [tref: glossary, xxxxx] ]

Note: we’ve put spaces between brackets to be able to present this literally; remove the spaces in use.

Where glossary is the text label the document author assigns to the URL of a Web-accessible glossary, and xxxxx is the term as it appears in that glossary, with any spaces are replaced by en-dashes (hyphens). For example, a Spec-Up external reference to the term self-certifying identifer using the label toip for this glossary would look like this:

[[xref: toip1, self-certifying-identifier]]

An item borrowed from an other glossary might look like this:

[[xref: toip2, hash]]

An alias is used to the generate the preferred spelling on the receiving end: [ [tref: glossary, xxx-xx, Xxx Xx] ]

leads to ‘Xxx Xx’ as the term in the glossary that’s collected via the key ‘xxx-xx’

§ Referenced Glossaries

These glossaries have been interlinked using tref and xref tags. We show both test and production environments. The specs.json is for proficient users to inspect the production settings.

§ Interlinked glossary summary

Glossary	TEST repo	Live TEST Glossary	Production repo	Live PRODUCTION Glossary	Specs.json PROD
KERIsuite	HenkvanCann	TEST	WebofTrust	PRODUCTION	Specs.json
vLEI	HenkvanCann
ToIP Main	HenkvanCann	TEST	ToIP	PRODUCTION	Specs.json
ToIP General IT	HenkvanCann	TEST	ToIP	PRODUCTION	Specs.json

The following glossaries were used as sources for some of the definitions in the ToIP General Glossary. All source glossaries are cited in the definitions of each term.

Short Name	Source Glossary	URL
Wikipedia	Wikipedia	https://www.wikipedia.org/
eSSIF-Lab	eSSIF-Lab Glossary	https://essif-lab.github.io/framework/docs/essifLab-glossary
NIST-CSRC	NIST Computer Security Resource Center Glossary	https://csrc.nist.gov/glossary/
W3C DID	W3C Decentralized Identifiers (DIDs) 1.0	https://www.w3.org/TR/did-core/#terminology
W3C VC	W3C VC Data Model 1.1	https://www.w3.org/TR/vc-data-model/#terminology

§ Terms and Definitions

abandoned-identifier

An AID is abandoned when either the inception-event or a subsequent rotation-event rotates to an empty next key digest list (which means the next threshold must also be 0).

Table of Contents