# Spec-Up-T Demo

# Intro

This is a default Spec-Up-T installation. Find information on the Spec-Up-T documentation website.

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

# Terms and Definitions Intro

# Demo terms, definitions and external definitions

A demo of terms and definitions, and references to external definitions.


ACDC

authentic-chained-data-container

More in extended KERI glossary

ADC

authentic-data-container

More in extended KERI glossary

ADR

architectural-decision-record

More in extended KERI glossary

AID

autonomic-identifier

More in extended KERI glossary

APC

authentic-provenance-chain

More in extended KERI glossary

API

application-programming-interface

More in extended KERI glossary

AVR

authorized-vlei-representative

More in extended KERI glossary

BADA

best-available-data-acceptance-mechanism

More in extended KERI glossary

BFT

byzantine-fault-tolerance

More in extended KERI glossary

BOLA

broken-object-level-authorization

More in extended KERI glossary

CBOR

concise-binary-object-representation

More in extended KERI glossary

CESR-version

the CESR Version is provided by a special Count Code that specifies the Version of all the CESR code tables in a given Stream or Stream section.

Source: Dr. S. Smith

More in extended KERI glossary

CESR

composable-event-streaming-representation

More in extended KERI glossary

CLC

chain-link-confidentiality

More in extended KERI glossary

CRUD

Is acronym for the traditional client-server database update policy is CRUD (Create, Read, Update, Delete).

CRUD as opposed to RUN which is the acronym for the new peer-to-peer end-verifiable monotonic update policy.

More in extended KERI glossary

CSPRNG

means “Cryptographically Secure Pseudorandom Number Generator,” which means that a sequence of numbers (bits, bytes…) that is produced from an algorithm that is deterministic (the sequence is generated from some unknown internal state), hence pseudorandom is also cryptographically secure, or not.

(Source: https://crypto.stackexchange.com/questions/12436/what-is-the-difference-between-csprng-and-prng)

More in extended KERI glossary

CT

certificate-transparency

More in extended KERI glossary

DAG

directed-acyclic-graph

More in extended KERI glossary

DAR

designated-authorized-representative

More in extended KERI glossary

DEL

duplicitous-event-log

More in extended KERI glossary

DHT

distributed-hash-table

More in extended KERI glossary

DID

Decentralized Identifier

More in extended KERI glossary

DKMI

decentralized-key-management-infrastructure

More in extended KERI glossary

DPKI

decentralized-key-management-infrastructure

More in extended KERI glossary

E2E

end-to-end

More in extended KERI glossary

ECR

engagement-context-role

More in extended KERI glossary

ESSR

Encrypt‐Sender‐Sign‐Receiver

More in extended KERI glossary

FFI

foreign-function-interface

More in extended KERI glossary

GAR

gleif-authorized-representative

More in extended KERI glossary

GLEIF

Global Legal Entity Identifier Foundation

More in extended KERI glossary

GLEIS

Global Legal Entity Identifier System

More in extended KERI glossary

GPG

gnu-privacy-guard

More in extended KERI glossary

HSM

hardware-security-module

More in extended KERI glossary

I-O

input-output

More in extended KERI glossary

IANA

internet-assigned-numbers-authority

More in extended KERI glossary

IPEX

issuance-and-presentation-exchange-protocol

More in extended KERI glossary

ITPS

information-theoretic-security

More in extended KERI glossary

JOSE

javascript-object-signing-and-encryption

More in extended KERI glossary

JSON

javascript-object-notation

More in extended KERI glossary

KA2CE

keri-agreement-algorithm-for-control-establishment

More in extended KERI glossary

KAACE

keri-agreement-algorithm-for-control-establishment

More in extended KERI glossary

KAPI

Application programmer interfaces (APIs) for the various components in the KERI ecosystem such as Controllers, Agents, Witnesses, Watchers, Registrars etc need by which they can share information. The unique properties of the KERI protocol require APIs that preserve those properties. We call the set of APIs the KERI API.

Source Kapi Repo

More in extended KERI glossary

KAWA

keri’s-algorithm-for-witness-agreement

More in extended KERI glossary

KEL

A Key Event Log.

key-event-log

More in extended KERI glossary

KERI

key-event-receipt-infrastructure

More in extended KERI glossary

KERIA-agent

An agent in keria terms, is an instance of a keystore (hab) that runs in a given instance of the KERIA agent server.

More in extended KERI glossary

KERIA

KERI Agent in the cloud. The KERIA service will expose 3 separate HTTP endpoints on 3 separate network interfaces.

  1. Boot Interface - Exposes one endpoint for Agent Worker initialization.
  1. Admin Interface - The REST API for command and control operations from the Signify Client.
  1. KERI Protocol Interface - CESR over HTTP endpoint for KERI protocol interactions with the rest of the world.

More at Source Github repo

More in extended KERI glossary

KERIMask

A wallet similar to MetaMask, the manifestation will be a browser extension and it will connect to KERIA servers in order for a person to control AIDs from their browser.

More in extended KERI glossary

KERISSE

keri-suite-search-engine

More in extended KERI glossary

KERL

key-event-receipt-log

More in extended KERI glossary

KID

keri-improvement-doc

More in extended KERI glossary

KRAM

keri-request-authentication-method

More in extended KERI glossary

LEI

Legal Entity Identifier

More in extended KERI glossary

LID

legitimized-human-meaningful-identifier

More in extended KERI glossary

LLM

large-language-model

More in extended KERI glossary

LoA

levels-of-assurance

More in extended KERI glossary

LoC

loci-of-control

More in extended KERI glossary

MFA

multi-factor-authentication

More in extended KERI glossary

MIME-type

media-type

More in extended KERI glossary

NFT

non-fungible-token

More in extended KERI glossary

OOBI

out-of-band-introduction

More in extended KERI glossary

OOR

official-organizational-role

More in extended KERI glossary

P2P

peer-to-peer

More in extended KERI glossary

PGP

pretty-good-privacy

More in extended KERI glossary

PID

percolated-information-discovery

More in extended KERI glossary

PKI

public-key-infrastructure

More in extended KERI glossary

PRNG

means “Pseudorandom Number Generator” which means that a sequence of numbers (bits, bytes…) is produced from an algorithm which looks random, but is in fact deterministic (the sequence is generated from some unknown internal state), hence pseudorandom.

Such pseudorandomness can be cryptographically secure, or not. It is cryptographically secure if nobody can reliably distinguish the output from true randomness, even if the PRNG algorithm is perfectly known (but not its internal state). A non-cryptographically secure PRNG would fool basic statistical tests but can be distinguished from true randomness by an intelligent attacker.

(Source: https://crypto.stackexchange.com/questions/12436/what-is-the-difference-between-csprng-and-prng)

More in extended KERI glossary

PTEL

public-transaction-event-log

More in extended KERI glossary

QAR

qvi-authorized-representative

More in extended KERI glossary

QVI

qualified-vlei-issuer

More in extended KERI glossary

RID

root-autonomic-identifier

More in extended KERI glossary

RUN

The acronym for the new peer-to-peer end-verifiable monotonic update policy is RUN (Read, Update, Nullify).

RUN as opposed to CRUD which is the traditional client-server database update policy.

More in extended KERI glossary

SAD

self-addressing-data

More in extended KERI glossary

SAID

self-addressing-identifier

More in extended KERI glossary

SATP

secure-asset-transfer-protocol

More in extended KERI glossary

SCID

self-certifying-identifier

More in extended KERI glossary

SKRAP

signify-keria-request-authentication-protocol

More in extended KERI glossary

SKWA

simple-keri-for-web-auth

More in extended KERI glossary

SPAC

secure-private-authentic-confidentiality

More in extended KERI glossary

SSI

self-sovereign-identity

More in extended KERI glossary

TCP

transmission-control-protocol

More in extended KERI glossary

TEE

trusted-execution-environment

More in extended KERI glossary

TEL

transaction-event-log

More in extended KERI glossary

TOAD

threshold-of-accountable-duplicity

More in extended KERI glossary

TPM

trusted-platform-module

More in extended KERI glossary

TSP

trust-spanning-protocol

More in extended KERI glossary

UI

user-interface

More in extended KERI glossary

URL

uniform-resource-locator

More in extended KERI glossary

VC

verifiable-credential

More in extended KERI glossary

VCTEL

virtual-credential-transaction-event-log

More in extended KERI glossary

VDS

verifiable-data-structure

More in extended KERI glossary

VID

verifiable-identifier

More in extended KERI glossary

XBRL

extensible-business-reporting-language

More in extended KERI glossary

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).

More in extended KERI glossary

access-controlled-interaction

Access controlled actions like submitting a report. If you already have that report then load balancer needs a mechanism to drop repeated requests.

Source: Samuel Smith / Daniel Hardman / Lance Byrd - Zoom meeting KERI Suite Jan 16 2024; discussion minute 30-60 min

More in extended KERI glossary

agency

Agents can be people, edge computers and the functionality within wallets. The service an agent offers is agency.

More in extended KERI glossary

agent

A representative for an identity. MAY require the use of a wallet. MAY support transfer.

More in extended KERI glossary

ambient-verifiability

Verifiable by anyone, anywhere, at anytime. Although this seems a general term, it was first used in the context of KERI by Sam Smith.

Ambient Duplicity Detection is an example of ambient verifiability that describes the possibility of detecting duplicity by anyone, anywhere, anytime.

More in extended KERI glossary

ample

The minimum required number of participants in an event to have a supermajority so that one and only one agreement or consensus on an event may be reached. This is a critical part of the KAACE agreement algorithm (consensus) in KERI for establishing consensus between witnesses on the key state of a KERI identifier.

More in extended KERI glossary

append-only-event-logs

Append-only is a property of computer data storage such that new data can be appended to the storage, but where existing data is immutable.

A blockchain is an example of an append-only log. The events can be transactions. Bitcoin is a well-known Append only log where the events are totally ordered and signed transfers of control over unspent transaction output.

More on Wikipedia

More in extended KERI glossary

application-programming-interface

An application programming interface (API) is a way for two or more computer programs to communicate with each other. It is a type of software interface, offering a service to other pieces of software.

More in extended KERI glossary

architectural-decision-record

Is a justified software design choice that addresses a functional or non-functional requirement that is architecturally significant.

Source adr.github.io

More in extended KERI glossary

attribute

a top-level field-map within an ACDC that provides a property of an entity that is inherent or assigned to the entity.

Source: Dr. S. Smith

More in extended KERI glossary

attributional-trust

KERI offers cryptographic root-of-trust to establish attributional trust. In the real world you’d also need reputational-trust. You can’t have reputation without attributional trust.

Read more in source Universal Identifier Theory

More in extended KERI glossary

authentic-chained-data-container

a directed acyclic graph with properties to provide a verifiable chain of proof-of-authorship. See the full specification

Source: Dr. S.Smith, 2024

Explained briefly, an ACDC or authentic-data-container proves digital data consistency and authenticity in one go. An ACDC cryptographically secures commitment to the data contained, and its identifiers are self-addressing, which means they point to themselves and are also contained in the data.

More in extended KERI glossary

authentic-data-container

A mechanism for conveying data that allows the authenticity of its content to be proved.

Instance

A Verifiable Credential is an authentic-chained-data-container.

More in extended KERI glossary

authentic-data

integrity and provenance data.

Source: Timothy Ruff, #IIW37

More in extended KERI glossary

authentic-provenance-chain

Interlinked presentation-exchange of evidence that allow data to be tracked back to its origin in an objectively verifiable way.

More in extended KERI glossary

authentic-web

The authentic web is the internet as a whole giant verifiable data structure. Also called Web5. The web will be one big graph. That’s the mental model of the ‘authentic web’.

More in extended KERI glossary

authenticity

The quality of having an objectively verifiable origin ; contrast veracity. When a newspaper publishes a story about an event, every faithful reproduction of that story may be authentic — but that does not mean the story was true (has veracity).

Authenticity is strongly related to digital security. Ideally it should be verifiable (to a root-of-trust). The future picture therein is the authentic-web.

More in extended KERI glossary

authoritative

Established control authority over an identifier, that has received attestations to it, e.g. control over the identifier has been verified to its root-of-trust. So the (control over the) identifier is ‘authoritative’ because it can be considered accurate, renowned, honourable and / or respected.

Also used to describe PKI key pairs that have this feature.

More in extended KERI glossary

authority

https://glossary.trustoverip.org/#term:authority

More in extended KERI glossary

authorization

Is the function of specifying access rights/privileges to resources, which is related to general information security and computer security, and to access control in particular.

More formally, “to authorize” is to define an access policy.

More in extended KERI glossary

authorized-vlei-representative

Also ‘AVR’. This a representative of a Legal Entity that are authorized by the DAR of a Legal Entity to request issuance and revocation of:

  • vLEI Legal Entity Credentials

Paraphrased by @henkvancann from source Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

autonomic-computing-systems

Self managing computing systems using algorithmic governance, from the 90’s way way way before DAOs. KERI creator Sam Smith worked at funded Navy research in the 90’s on autonomic survivable systems as in “self-healing” systems: “We called them autonomic way back then”.

More in extended KERI glossary

autonomic-identifier

a self-managing cryptonymous identifier that must be self-certifying (self-authenticating) and must be encoded in CESR as a qualified Cryptographic primitive.

Source: Dr. S.Smith, 2024

An identifier that is self-certifying-identifier and self-sovereign-identity (or self-managing).

More in extended KERI glossary

autonomic-identity-system

an identity system that includes a primary root-of-trust in self-certifying identifiers that are strongly bound at issuance to a cryptographic signing (public, private) key pair. An AIS enables any entity to establish control over an AN in an independent, interoperable, and portable way.

Source: Dr. S.Smith, 2024

More in extended KERI glossary

autonomic-namespace

a namespace that is self-certifying and hence self-administrating. An AN has a self-certifying prefix that provides cryptographic verification of root control authority over its namespace. All derived AIDs in the same AN share the same root-of-trust, source-of-truth, and locus-of-control (RSL). The governance of the namespace is, therefore, unified into one entity, that is, the controller who is/holds the root authority over the namespace.

Source: Dr. S.Smith, 2024

Namespaces are, therefore, portable and truly self-sovereign.

More in extended KERI glossary

autonomic-trust-basis

When we use an AID as the root-of-trust we form a so-called autonomic trust basis. This is diagrammed as follows:

More in extended KERI glossary

backer

an alternative to a traditional KERI based Witness commonly using Distributed Ledger Technology (DLT) to store the KEL for an identifier.

Source: Dr. S.Smith, 2024

More in extended KERI glossary

base-media-type

credential plus ld plus json.

Other media types of credentials are allowed by must provide either unidirectional or bidirectional transformations. So, for example, we would create credential+acdc+json and provide a unidirectional transformation to credential+ld+json.

More in extended KERI glossary

base64

In computer programming, Base64 is a group of binary-to-text encoding schemes that represent binary data (more specifically, a sequence of 8-bit bytes) in sequences of 24 bits that can be represented by four 6-bit Base64 digits.

More on source Wikipedia

More in extended KERI glossary

bespoke-credential

It’s an issuance-event 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).

More in extended KERI glossary

best-available-data-acceptance-mechanism

The BADA security model provides a degree of replay-attack protection. The attributate originator (issuer, author, source) is provided by an attached signature couple or quadruple. A single reply could have multiple originators. When used as an authorization the reply attributes may include the identifier of the authorizer and the logic for processing the associated route may require a matching attachment.

BADA is part of KERI's Zero Trust Computing Architecture for Data Management: How to support Secure Async Data Flow Routing in KERI enabled Applications.

More in extended KERI glossary

bexter

The class variable length text that is used in CESR and preserves the round-trip transposability using Base64 URL safe-only encoding even though the text variable length.

More in extended KERI glossary

binding

The technique of connecting two data elements together. In the context of key-event-receipt-infrastructure it’s the association of data or an identifier with another identifier or a subject (a person, organization or machine), thereby lifting the privacy of the subject through that connection, i.e. binding.

More in extended KERI glossary

bis

bis = backed vc issue, registry-backed transaction event log credential issuance

More in extended KERI glossary

bivalent

A nested set of layered delegations in a delegation tree, wraps each layer with compromise recovery protection of the next higher layer. This maintains the security of the root layer for compromise recovery all the way out to the leaves in spite of the leaves using less secure key management methods.

bivalent-key-management-infrastructure

More in extended KERI glossary

blake3

BLAKE3 is a relatively young (2020) cryptographic hash function based on Bao and BLAKE2.

More in extended KERI glossary

blind-oobi

A blind OOBI means that you have some mechanisms in place for verifying the AID instead of via the OOBI itself. A blind OOBI is essentially a URL. It’s called “blind” because the witness is not in the OOBI itself. You haves other ways of verifying the AID supplied.

More in extended KERI glossary

blinded-revocation-registry

The current state of a transaction-event-log (TEL) may 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.

More in extended KERI glossary

bran

A cryptographic string used as a primary input, a seed, for creating key material for and autonomic-identifier.

More in extended KERI glossary

branch

In software development a ‘branch’ refers to the result of branching: the duplication of an object under version control for further separate modification.

More in extended KERI glossary

broken-object-level-authorization

Refers to security flaws where users can access data they shouldn’t, due to inadequate permission checks on individual (sub)objects.

More in extended KERI glossary

brv

brv = backed vc revoke, registry-backed transaction event log credential revocation

More in extended KERI glossary

byzantine-agreement

(non PoW) Byzantine Agreement is 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).

More in extended KERI glossary

byzantine-fault-tolerance

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.

More in extended KERI glossary

canonicalization

In computer science, canonicalization (sometimes standardization or normalization) is a process for converting data that has more than one possible representation into a “standard,” “normal,” or canonical form.

This can be done to compare different representations for equivalence, to count the number of distinct data structures, to improve the efficiency of various algorithms by eliminating repeated calculations, or to make it possible to impose a meaningful sorting order.

More on source Wikipedia

More in extended KERI glossary

certificate-transparency

Certificate Transparency (CT) is an Internet security standard and open source framework for monitoring and auditing digital certificates. The standard creates a system of public logs that seek to eventually record all certificates issued by publicly trusted certificate authorities, allowing efficient identification of mistakenly or maliciously issued certificates. As of 2021, Certificate Transparency is mandatory for all SSL/TLS certificates.

More in extended KERI glossary

cesr-proof-signatures

CESR Proof Signatures is an extension to the Composable Event Streaming Representation [CESR] that provides transposable cryptographic signature attachments on self-addressing data SAD. Any SAD, such as an Authentic Chained Data Container (ACDC) Verifiable Credential [ACDC], for example, may be signed with a CESR Proof Signature and streamed along with any other CESR content. In addition, a signed SAD can be embedded inside another SAD, and the CESR proof signature attachment can be transposed across envelope boundaries and streamed without losing any cryptographic integrity.

(Philip Feairheller, IETF-cesr-proof)

More in extended KERI glossary

cesride

is concerned with parsing CESR primitives.

Cesride is built from cryptographic primitives that are named clearly and concisely. There are:

Each primitive will have methods attached to it that permit one to generate and parse the qualified base2 or base64 representation.

More in extended KERI glossary

chain-link-confidential-disclosure

contractual restrictions and liability imposed on a recipient of a disclosed ACDC that contractually link the obligations to protect the disclosure of the information contained within the ACDC to all subsequent recipients as the information moves downstream. The Chain-link Confidential Disclosure provides a mechanism for protecting against un-permissioned exploitation of the data disclosed via an ACDC.

Source: Dr. S.Smith

More in extended KERI glossary

chain-link-confidentiality

Chains together a sequence of disclosee which may also include a set of constraints on data usage by both second and third parties expressed in legal language such that the constraints apply to all recipients of the disclosed data thus the phrase “chain link” confidentiality. Each Disclosee in the sequence in turn is the discloser to the next Disclosee.

This is the primary mechanism of granting digital data rights through binding information exchange to confidentiality laws. Confidentiality is dynamically negotiated on a per-event, per-data exchange basis according to the data that is being shared in a given exchange.

More in extended KERI glossary

chain-of-custody

From Wikipedia (Source):

Chain of custody (CoC), in legal contexts, is the chronological documentation or paper trail that records the sequence of custody, control, transfer, analysis, and disposition of materials, including physical or electronic evidence. Of particular importance in criminal cases, the concept is also applied in civil litigation and more broadly in drug testing of athletes and in supply chain management, e.g. to improve the traceability of food products, or to provide assurances that wood products originate from sustainably managed forests.

More in extended KERI glossary

cigar

An unindexed-signature.

Source by Jason Colburne

More in extended KERI glossary

claim

An assertion of the truth of something, typically one which is disputed or in doubt. A set of claims might convey personally identifying information: name, address, date of birth and citizenship, for example. (Source).

More in extended KERI glossary

clone

A copy of a system that is - and works exactly as the original

More in extended KERI glossary

cloud-agent

Cloud agent is software that is installed on the cloud server instances in order to provide security, monitoring, and analysis solutions for the cloud. They actually provide information and helps to provide control over cloud entities.

Paraphrased by @henkvancann based on source.

Also see agent.

More in extended KERI glossary

code-table-selector

the first character in the text code of composable-event-streaming-representation that determines which code-table to use, either a default code table or a code table selector character when not the default code table. Thus the 1 character text code table must do double duty. It must provide selectors for the different text code tables and also provide type codes for the most popular primitives that have a pad size of 1 that appear is the default code table.

More in extended KERI glossary

code-table

a code table is the Internet’s most comprehensive yet simple resource for browsing and searching for alt codes, ascii codes, entities in html, unicode characters, and unicode groups and categories.

Source

More in extended KERI glossary

cold-start-stream-parsing

After a reboot (or cold start), a stream processor looks for framing information to know how to parse groups of elements in the stream.

If that framing information is ambiguous then the parser may become confused and require yet another cold start. While processing a given stream a parser may become confused especially if a portion of the stream is malformed in some way. This usually requires flushing the stream and forcing a cold start to resynchronize the parser to subsequent stream elements.

More in extended KERI glossary

collective-signature

a group signature scheme, that (i) is shared by a set of signing groups and (ii) combined collective signature shared by several signing groups and several individual signers. The protocol of the first type is constructed and described in detail. It is possible to modify the described protocol which allows transforming the protocol of the first type into the protocol of the second type. The proposed collective signature protocols have significant merits, one of which is connected with possibility of their practical using on the base of the existing public key infrastructures.

Source

Collective signature have a variable length as a function of the number of signers.

More in extended KERI glossary

collision

In cryptography and identity collision generally refers to something going wrong because an identical result has been produced but it refers to - or points to - different sources or assets backing this result.

E.g. two hashes collide, meaning two different digital sources produce the same hash.

Another example is name(space) collision.

More in extended KERI glossary

compact-disclosure

a disclosure of an ACDC that discloses only the SAID(s) of some or all of its field maps. Both Partial and Selective Disclosure rely on Compact Disclosure.

Source: Dr. S. Smith

More in extended KERI glossary

compact-variant

Either a most-compact version of an ACDC or the fully-compact version of an ACDC. An issuer commitment via a signature to any variant of ACDC (compact, full, etc) makes a cryptographic commitment to the top-level section fields shared by all variants of that ACDC because the value of a top-level-section is either the SAD or the SAID of the SAD of the associated section.

More in extended KERI glossary

complementary-integrity-verification

A mechanism that can verify integrity independent of needing access to a previous instance or reference version of the information for comparison.

Source: Neil Thomson

More in extended KERI glossary

composability

short for text-binary concatenation composability. An encoding has Composability when any set of Self-Framing concatenated Primitives expressed in either the Text domain or Binary domain may be converted as a group to the other Domain and back again without loss.

Source: Dr. S.Smith

More in extended KERI glossary

composable-event-streaming-representation

Also called ‘CESR’. This compact encoding scheme fully supports both textual and binary streaming applications of attached crypto material of all types. This approach includes composability in both the textual and binary streaming domains. The primitive may be the minimum possible but still composable size.

Making composability a guaranteed property allows future extensible support of new compositions of streaming formats based on pre-existing core primitives and compositions of core primitives. This enables optimized stream processing in both the binary and text domains.

More in extended KERI glossary

composable

composability

More in extended KERI glossary

concatenation

In formal language theory and computer programming, string concatenation is the operation of joining character strings end-to-end. For example, the concatenation of “snow” and “ball” is “snowball”.

More on source Wikipedia page

More in extended KERI glossary

concise-binary-object-representation

a binary serialization format, similar in concept to JSON but aiming for greater conciseness. Defined in [RFC7049].

Source: Dr. S.Smith, 2024

More in extended KERI glossary

confidentiality

All statements in a conversation are only known by the parties to that conversation.

Source: Samuel Smith, at IIW-37, Oct 2023.

More in extended KERI glossary

configuration-files

In computing, configuration files (commonly known simply as config files) are files used to configure the parameters and initial settings for some computer programs. They are used for user applications, server processes and operating system settings.

More on source Wikipedia

More in extended KERI glossary

configuration-traits

a list of specially defined strings representing a configuration of a KEL. See (Configuration traits field)[#configuration-traits-field].

Source: Dr. S.Smith, 2024

More in extended KERI glossary

consensus-mechanism

How groups of entitities come to decisions. In general to learn about consensus mechanisms read any textbook on decision making, automated reasoning, multi-objective decision making, operations research etc.

More in extended KERI glossary

content-addressable-hash

Finding content by a hash of this content, generated by a one-way hash function applied to the content.

Content addressing is a way to find data in a network using its content rather than its location. The way we do is by taking the content of the content and hashing it. Try uploading an image to IPFS and get the hash using the below button.

More in extended KERI glossary

contextual-linkability

Refers to the condition where vendors or other data capture points provide enough context at point of capture to be able to use statistical correlation with existing data sets to link any of a person’s disclosed attributes to a set of already known data points about a given person.

More in extended KERI glossary

contingent-disclosure

Contingent disclosure is a privacy-preserving mechanism where only specific information or attributes are disclosed under defined conditions. It enables the selective sharing of data such that only the required information is revealed to a relying party, without exposing other unrelated or sensitive details. chain-link-confidentiality is a form of contingent disclosure.

More in extended KERI glossary

contractually-protected-disclosure

a discloser of an ACDC that leverages a Graduated Disclosure so that contractual protections can be put into place to minimize the leakage of information that can be correlated. A Contractually Protected Disclosure partially or selectively reveals the information contained within the ACDC in the initial interaction with the recipient and discloses further information only after the recipient agrees to the terms established by the discloser. More information may be progressively revealed as the recipient agrees to additional terms.

Source: Dr. S. Smith

More in extended KERI glossary

control-authority

In identity systems Control Authority is who controls what and that is the primary factor in determining the basis for trust in them. The entity with control authority takes action through operations that affect the

  • creation (inception)
  • updating
  • rotation
  • revocation
  • deletion
  • and delegation of the authentication factors and their relation to the identifier.

More in extended KERI glossary

controller

an entity that can cryptographically prove the control authority over an AID and make changes on the associated KEL. A controller of a multi-sig AID may consist of multiple controlling entities.

Source: Dr. S.Smith, 2024

More in extended KERI glossary

cooperative-delegation

The way KERI addresses the security-cost-performance-architecture-trade-off is via delegation of identifier prefixes. Delegation includes a delegator and a delegate. For this reason we may call this a cooperative delegation. This is a somewhat novel form of delegation.

More in extended KERI glossary

coroutines

Computer programs that can be suspended and resumed at will.

More in extended KERI glossary

correlation

In our scope this is an identifier used to indicate that external parties have observed how wallet contents are related.

More in extended KERI glossary

count-code

group-framing-code

More in extended KERI glossary

credential

Evidence of authority, status, rights, entitlement to privileges, or the like.

(source)

A credential has its current state and a history, which is captured in a doc or a graph.

More in extended KERI glossary

crypto-libraries

Cryptography libraries deal with cryptography algorithms and have API function calls to each of the supported features.

More in extended KERI glossary

cryptocurrency

A digital asset designed to work as a medium of exchange wherein individual coin ownership records are stored in a digital ledger or computerized database using strong cryptography to secure transaction record entries, to control the creation of additional digital coin records.

See more on source Wikipedia.

More in extended KERI glossary

cryptographic-commitment-scheme

is a cryptographic primitive that allows one to commit to a chosen value (or chosen statement) while keeping it hidden to others, with the ability to reveal the committed value later.

Commitment schemes are designed so that a party cannot change the value or statement after they have committed to it: that is, commitment schemes are binding.

More on wikipedia

More in extended KERI glossary

cryptographic-primitive

the serialization of a value associated with a cryptographic operation including but not limited to a digest (hash), a salt, a seed, a private key, a public key, or a signature.

Source: Dr. S.Smith, 2024

More in extended KERI glossary

cryptographic-strength

The term “cryptographically strong” is often used to describe an encryption algorithm, and implies, in comparison to some other algorithm (which is thus cryptographically weak), greater resistance to attack. But it can also be used to describe hashing and unique identifier and filename creation algorithms.

More on Wikipedia

More in extended KERI glossary

cryptonym

a cryptographic pseudonymous identifier represented by a string of characters derived from a random or pseudo-random secret seed or salt via a one-way cryptographic function with a sufficiently high degree of cryptographic strength (e.g., 128 bits, see appendix on cryptographic-strength. A cryptonym is a type of primitive.

More in extended KERI glossary

current-threshold

represents the number or fractional weights of signatures from the given set of current keys required to be attached to a Message for the Message to be considered fully signed.

Source: Dr. S.Smith, 2024

More in extended KERI glossary

custodial-agent

An agent owned by an individual who has granted signing-authority to a custodian who is usually also the host of the running agent software. Using partial-rotation to facilitate custodial key management the owner of the identifier retains rotation-authority and thus the ability to “fire” the custodian at any time without requiring the cooperation of the custodian.

More in extended KERI glossary

custodial-rotation

Rotation is based on control authority that is split between two key sets. The first for signing authority and the second (pre-rotated) for rotation authority, the associated thresholds and key list can be structured so that a designated custodial agent can hold signing authority, while the original controller can hold exclusive rotation authority.

partial-rotation supports the vital use case of custodial key rotation to authorize a custodial-agent.

Paraphrased by @henkvancann based on the IETF-KERI draft 2022 by Samual Smith.

More in extended KERI glossary

data-anchor

Data anchors are digest of digital data, that uniquely identify this data. The digest is the anchor and can be used to identify - and point to the data at the same time.

More in extended KERI glossary

dead-attack

an attack on an establishment-event that occurs after the Key-state for that event has become stale because a later establishment event has rotated the sets of signing and pre-rotated keys to new sets.

More in extended KERI glossary

dead-drop

In cybersecurity or digital privacy scenarios, the term “dead drop” refers to encrypted or secure virtual spaces where information can be deposited or retrieved anonymously. In the credentials field, the presenter controls the disclosure, so you can’t re-identify the data.

Discussed in tech meet KERI recording, date June 27 2023.

More in extended KERI glossary

decentralized-identifier

Decentralized identifiers (DID) are a new type of identifier that enables verifiable, decentralized digital identity. A DID refers to any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) as determined by the controller of the DID.

Source W3C.org.

More in extended KERI glossary

decentralized-identity

is a technology that uses cryptography to allow individuals to create and control their own unique identifiers. They can use these identifiers to obtain Verifiable Credentials from trusted organizations and, subsequently, present elements of these credentials as proof of claims about themselves. In this model, the individual takes ownership of their own identity and does not need to cede control to centralized service providers or companies.

More in extended KERI glossary

decentralized-key-management-infrastructure

a key management infrastructure that does not rely on a single entity for the integrity and security of the system as a whole. Trust in a DKMI is decentralized through the use of technologies that make it possible for geographically and politically disparate entities to reach an agreement on the key state of an identifier DPKI.

Source: Dr. S.Smith, 2024

More in extended KERI glossary

delegated-identifier

Matches the act of delegation with the appropriate digital twin. Consequently when applied recursively, delegation may be used to compose arbitrarily complex trees of hierarchical (delegative) key management event streams. This is a most powerful capability that may provide an essential building block for a generic universal decentralized key management infrastructure (DKMI) that is also compatible with the demand of generic event streaming applications.

More in the whitepaper

More in extended KERI glossary

delegation

A person or group of persons officially elected or appointed to represent another or others.

More in extended KERI glossary

derivation-code

To properly extract and use the public-key-infrastructure embedded in a self-certifying-identifier we need to know the cryptographic signing scheme used by the key-pair. KERI includes this very compactly in the identifier, by replacing the pad character (a character used to fill a void to able to always end up with a fixed length public key) with a special character that encodes the derivation process. We call this the derivation code.

More in extended KERI glossary

designated-aliases

An AID controller can designate aliases which are AID controlled identifiers such as a did:keri, did:webs, etc. The AID controller issues a designated aliases attestation (no issuee) that lists the identifiers and manages the status through a registry anchored to their KEL. See the designated aliases docs

More in extended KERI glossary

designated-authorized-representative

Also ‘DAR’. These are representatives of a Legal Entity that are authorized by the Legal Entity to act officially on behalf of the Legal Entity. DARs can authorize:

  1. vLEI Issuer Qualification Program Checklists
  1. execute the vLEI Issuer Qualification Agreement
  1. provide designate/replace Authorized vLEI Representatives (authorized-vlei-representatives).

Paraphrased by @henkvancann from source Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

diger

A primitive that represents a digest. It has the ability to verify that an input hashes to its raw value.

Source by Jason Colburne

More in extended KERI glossary

digest

verifiable cryptographic commitment. It’s a collision-resistant hash of content.

More in extended KERI glossary

digital-signature

A digital signature is a mathematical scheme for verifying the authenticity of digital messages or documents. A valid digital signature, where the prerequisites are satisfied, gives a recipient very strong reason to believe that the message was created by a known sender (authentication), and that the message was not altered in transit (integrity).

More in extended KERI glossary

dip

dip = delcept, delegated inception

More in extended KERI glossary

direct-mode

Two primary trust modalities motivated the KERI design, One of these is the direct (one-to-one) mode, in which the identity controller establishes control via verified signatures of the controlling key-pair. The direct mode doesn’t use witnesses nor key-event-receipt-logs, but has direct (albeit intermittent) network contact with the validator.

More in extended KERI glossary

directed-acyclic-graph

From Wikipedia (source):

In mathematics, particularly graph theory, and computer science, a directed acyclic graph (DAG /ˈdæɡ/ (listen)) is a directed graph with no directed cycles. That is, it consists of vertices and edges (also called arcs), with each edge directed from one vertex to another.

A directed acyclic graph (DAG)

More in extended KERI glossary

disclosee

a role of an entity that is a recipient to which an ACDC is disclosed. A Disclosee may or may not be the Issuee of the disclosed ACDC.

Source: Dr. S. Smith

More in extended KERI glossary

discloser

a role of an entity that discloses an authentic-chained-data-container. A Discloser may or may not be the Issuer of the disclosed ACDC.

Source: Dr. S. Smith

More in extended KERI glossary

discovery

A mechanism that helps systems or devices find each other automatically, often used in networks to identify services or resources. In decentralized identifier systems it helps to locate and verify digital identities without relying on a central authority.

More in extended KERI glossary

distributed-hash-table

It is a distributed system that provides a lookup service similar to a hash table: key-value pairs are stored in a DHT, and any participating node can efficiently retrieve the value associated with a given key. The main advantage of a DHT is that nodes can be added or removed with minimum work around re-distributing keys.

More in extended KERI glossary

dnd

Do Not Delegate is a flag/attribute for an AID, and this is default set to “you can delegate.”

More in extended KERI glossary

domain-name

A domain name is a string that identifies a realm of administrative autonomy, authority or control within the Internet. Domain names are used in various networking contexts and for application-specific naming and addressing purposes.

More on Source Wikipedia.

More in extended KERI glossary

domain

a representation of a primitive either Text (T), Binary (B) or Raw binary ®.

Source: Dr. S. Smith

Beware: outside of CESR but within the internet world, the term ‘domain’ mostly refers to the concept of a domain name.

More in extended KERI glossary

double-spend-proof

Total global ordering of transactions so that value can’t be spent twice at the same time from the unit of value. Or in everyday language: you can’t spend your money twice.

More in extended KERI glossary

drt

drt = deltate, delegated rotation

More in extended KERI glossary

dual-indexed-codes

a context-specific coding scheme, for the common use case of thresholded multi-signature schemes in CESR.

More in extended KERI glossary

dual-text-binary-encoding-format

An encoding format that allows for both text and binary encoding format, which is fully interchangeable. The composability property enables the round trip conversion en-masse of concatenated primitives between the text domain and binary domain while maintaining the separability of individual primitives.

Read more in source of Samuel Smith

More in extended KERI glossary

duplicitous-event-log

This is a record of inconsistent event messages produced by a given controller or witness with respect to a given key-event-receipt-log. The duplicitous events are indexed to the corresponding event in a KERL.

More in extended KERI glossary

duplicity-detection

A mechanism to detect duplicity in cryptographically secured event logs.

More in extended KERI glossary

duplicity

the existence of more than one version of a Verifiable key-event-log for a given AID.

Source: Dr. S.Smith, 2024

More in extended KERI glossary

eclipse-attack

An eclipse attack is a peer-to-peer network-based attack. Eclipse attack can only be performed on nodes that accept incoming connections from other nodes, and not all nodes accept incoming connections.

In a bitcoin network, by default, there are a maximum of 117 incoming TCP connections and 8 outgoing TCP connections.

Source

More in extended KERI glossary

edge

a top-level field map within an ACDC that provides edges that connect to other ACDCs, forming a labeled property graph (LPG).

Source: Dr. S. Smith

More in extended KERI glossary

electronic-signature

An electronic signature, or e-signature, refers to data in electronic form, which is logically associated with other data in electronic form and which is used by the signatory to sign. This type of signature has the same legal standing as a handwritten signature as long as it adheres to the requirements of the specific regulation under which it was created (e.g., eIDAS in the European Union, NIST-DSS in the USA or ZertES in Switzerland).

More in extended KERI glossary

encrypt-sender-sign-receiver

An authenticated encryption approach, using PKI. It covers authenticity and confidentiality.

More in extended KERI glossary

end-role

An end role is an authorization for one AID to serve in a role for another AID.

For example, declaring that your agent AID is serving in the role of agent for your business AIDs.

Source: Phil Feairheller

More in extended KERI glossary

end-to-end

Inter-host communication and data flow transformations, considered in motion and at rest.

  1. E2E Security. Inter-host communication must be end-to-end signed/encrypted and data must be stored signed/encrypted. Data is signed/encrypted in motion and at rest.
  1. E2E Provenance. Data flow transformations must be end-to-end provenanced using verifiable data items (verifiable data chains or VCs). Every change shall be provenanced.

Paraphrased from source Universal Identifier Theory by Samuel Smith

More in extended KERI glossary

end-verifiability

a data item or statement may be cryptographically securely attributable to its source (party at the source end) by any recipient verifier (party at the destination end) without reliance on any infrastructure not under the verifier’s ultimate control.

Source: Dr. S.Smith, 2024

end-verifiable

More in extended KERI glossary

end-verifiable

When a log is end verifiable, it means that the log may be verified by any end user that receives a copy. No trust in intervening infrastructure is needed to verify the log and validate the content.

More in extended KERI glossary

engagement-context-role

A person that represents the legal-entity in a functional or in another context role and is issued an ECR vlei-credential.

More in extended KERI glossary

entity

entity in the #essiflab glossary.

More in extended KERI glossary

entropy

Unpredictable information. Often used as a secret or as input to a key generation algorithm.

More in extended KERI glossary

ephemeral

Lasting for a markedly brief time. Having a short lifespan.

In the context of identifiers is often referred to as identifiers for one time use; or throw-away identifiers.

More in extended KERI glossary

escrow-state

The current state of all the temporary storage locations (what events are waiting for what other information) that KERI protocol needs to keep track of, due to its fully asynchronous nature.

More in extended KERI glossary

escrow

‘Escrow’ as a noun is a (legal) arrangement in which a third party temporarily holds money or property until a particular condition has been met.

‘Escrow’ as a verb: we use it in protocol design to handle out of order events. Store the event and wait for the other stuff to show up and then continue processing of the event. So escrowing is the process of storing this event. We root back to the event later.

More in extended KERI glossary

establishment-event

a key-event that establishes or changes the key state which includes the current set of authoritative keypairs (key state) for an AID.

Source: dr. S.Smith

More in extended KERI glossary

exn

exn = exchange

More in extended KERI glossary

exp

exp = expose, sealed data exposition

More in extended KERI glossary

extensible-business-reporting-language

XBRL is the open international standard for digital business reporting, managed by a global not for profit consortium, XBRL International.

More in extended KERI glossary

field-map

A traditional key:value pair renamed to avoid confusing with the cryptographic use of the term ‘key’.

More in extended KERI glossary

first-seen

refers to the first instance of a message received by any witness or watcher. The first-seen event is always seen, and can never be unseen. It forms the basis for duplicity detection in KERI-based systems.

Source: Dr. S.Smith

More in extended KERI glossary

foreign-function-interface

Is a mechanism by which a program written in one, usually an interpreted (scripted), programming language that can call routines or make use of services written or compiled in another one.

More on Source: https://en.wikipedia.org/wiki/Foreign_function_interface

More in extended KERI glossary

frame-code

framing-code

More in extended KERI glossary

framing-code

a code that delineates a number of characters or bytes, as appropriate, that can be extracted atomically from a stream.

Source: Dr. S. Smith

More in extended KERI glossary

full-disclosure

a disclosure of an ACDC that discloses the full details of some or all of its field maps. In the context of selective-disclosure, Full Disclosure means detailed disclosure of the selectively disclosed attributes, not the detailed disclosure of all selectively disclosable attributes. In the context of partial-disclosure, Full Disclosure means detailed disclosure of the field map that was so far only partially disclosed.

Source: Dr. S. Smith

More in extended KERI glossary

fully-compact

The most compact form of an ACDC. This is the only signed variant of an ACDC and this signature is anchored in a transaction-event-log (TEL) for the ACDC.

This is one valid choice for an ACDC schema.

This form is part of the graduated-disclosure mechanism in ACDCs.

More in extended KERI glossary

fully-expanded

The most user-friendly version of an ACDC credential. It doesn’t need to be signed and typically is not signed since the most compact version which is signed can be computed from this form and then the signature can be looked up in the TEL of the ACDC in question.

Regarding the graduated disclosure objective this form is the one with the highest amount of disclosure for a given node of an ACDC graph.

More in extended KERI glossary

ghost-credential

Is a valid credential within in a 90 days grace period (the revocation transaction time frame before it’s booked to revocation registry).

More in extended KERI glossary

gleif-authorized-representative

A representative of GLEIF authorized to perform the identity verifications requirements needed to issue the QVI vLEI Credential.

Source: GLEIF Ecosystem Governance Framework v1.0 Glossary

More in extended KERI glossary

gnu-privacy-guard

also GnuPG; is a free-software replacement for Symantec’s PGP cryptographic software suite. It is compliant with RFC 4880, the IETF standards-track specification of OpenPGP. Modern versions of PGP are interoperable with GnuPG and other OpenPGP-compliant systems.

More on wikipedia

See more about the closely related and often-confusing term PGP.

More in extended KERI glossary

governance-framework

Also called ‘Governance structure’. Governance frameworks are the structure of a government and reflect the interrelated relationships, factors, and other influences upon the institution. Governance frameworks structure and delineate power and the governing or management roles in an organization. They also set rules, procedures, and other informational guidelines.

More in source Wikipedia.

More in extended KERI glossary

graduated-disclosure

a disclosure of an ACDC that does not reveal its entire content in the initial interaction with the recipient and, instead, partially or selectively reveals only the information contained within the ACDC necessary to further a transaction with the recipient. A Graduated disclosure may involve multiple steps where more information is progressively revealed as the recipient satisfies the conditions set by the discloser. compact-disclosure, partial-disclosure, selective-disclosure, and full-disclosure are all Graduated disclosure mechanisms.

Source: Dr. S. Smith

More in extended KERI glossary

graph-fragment

An ACDC is a verifiable data structure and part of a graph, consisting of a node property and one or two edge proporties.

More in extended KERI glossary

group-code

group-framing-code

More in extended KERI glossary

group-framing-code

special Framing Codes that can be specified to support groups of Primitives which make them pipelinable. Self-framing grouping using Count Codes is one of the primary advantages of composable encoding.

Source: Dr. S. Smith

More in extended KERI glossary

hab

A Hab is a keystore for one identifier. The Python implementation in keripy, also used by keria uses LMDB to store key material and all other data.

Many Habs are included within and managed by a habery.

More in extended KERI glossary

habery

‘Hab’ comes from ‘Habitat’. It’s a place where multi-sigs and AIDs are linked. Habery manages a collection of hab. A Hab is a data structure (a Python object).

More in extended KERI glossary

hardware-security-module

A HSM is a physical computing device that safeguards and manages secrets (most importantly digital keys), performs encryption and decryption functions for digital signatures, strong authenticity and other cryptographic functions.

More in source Wikipedia

More in extended KERI glossary

hierarchical-asynchronous-coroutines-and-input-output

HIO is an acronym which stands for ‘Weightless hierarchical asynchronous coroutines and I/O in Python’.

It’s Rich Flow Based Programming Hierarchical Structured Concurrency with Asynchronous IO. That mouthful of terms has been explained further on Github.

HIO builds on very early work on hierarchical structured concurrency with lifecycle contexts from ioflo, ioflo github, and ioflo manuals.

More in extended KERI glossary

hierarchical-composition

Encoding protocol that is composable in a hierarchy and enables pipelining (multiplexing and de-multiplexing) of complex streams in either text or compact binary. This allows management at scale for high-bandwidth applications.

More in extended KERI glossary

hierchical-deterministic-keys

An HDK type is a deterministic Bitcoin wallet derived from a known seed that allows child keys to be created from the parent key. Because the child key is generated from a known seed, a relationship between the child and parent keys is invisible to anyone without that seed.

More in extended KERI glossary

hio

Weightless hierarchical asynchronous coroutines and I/O in Python.

Rich Flow Based Programming Hierarchical Structured Concurrency with Asynchronous IO.

More in extended KERI glossary

icp

icp = incept, inception

More in extended KERI glossary

identifier-system

a system for uniquely identifying (public) identities

More in extended KERI glossary

identifier

Something to uniquely identify (public) identities; pointing to something or someone else.

More in extended KERI glossary

identity-assurance

The heavy-lifting to be done by a trusted (middle-man) party to establish - and then offer reputational trust. An example of such a party is GLEIF. Instead, KERI is for attributional-trust. In the real world you need both.

Read more in source Universal Identifier Theory

More in extended KERI glossary

identity

A unique entity. Typically represented by a unique identifier.

More in extended KERI glossary

inception-event

an establishment-event that provides the incepting information needed to derive an AID and establish its initial Key state.

Source Sam Smith

More in extended KERI glossary

inception

The operation of creating an AID by binding it to the initial set of authoritative keypairs and any other associated information. This operation is made verifiable and duplicity evident upon acceptance as the inception event that begins the AID’s KEL.

Source Sam Smith

More in extended KERI glossary

inconsistency

If a reason, idea, opinion, etc. is inconsistent, different parts of it do not agree, or it does not agree with something else. Data inconsistency occurs when similar data is kept in different formats in more than one file. When this happens, it is important to match the data between files.

More in extended KERI glossary

indexed-signature

Also called siger. An indexed signature attachment is used when signing anything with a multi-key autonomic identifier. The index is included as part of the attachment, so a verifier knows which of the multiple public keys was used to generate a specific signature.

Source:Philip Feairheller

More in extended KERI glossary

indirect-mode

Two primary trust modalities motivated the KERI design, One of these is the indirect (one-to-many) mode, which depends on witnessed key event receipt logs (KERL) as a secondary root-of-trust for validating events. This gives rise to the acronym KERI for key event receipt infrastructure.

More in extended KERI glossary

information-theoretic-security

the highest level of cryptographic security concerning a cryptographic secret (seed, salt, or private key).

Source: Dr. S. Smith

More in extended KERI glossary

input-output

In computing, input/output (I/O, or informally io or IO) is the communication between an information processing system, such as a computer, and the outside world, possibly a human or another information processing system. Inputs are the signals or data received by the system and outputs are the signals or data sent from it. The term can also be used as part of an action; to “perform I/O” is to perform an input or output operation.

More in extended KERI glossary

inquisitor

In the ACDC context it’s a general term for someone (in a validating role) that launches an inquiry at some KERI witness.

More in extended KERI glossary

integrity

Integrity (of a message or data) means that the information is whole, sound, and unimpaired (not necessarily correct). It means nothing is missing from the information; it is complete and in intended good order.

Source: Neil Thomson

More in extended KERI glossary

interaction-event

Non-establishment Event that anchors external data to the key-state as established by the most recent prior establishment event.

Source Sam Smith

More in extended KERI glossary

interactive-authentication-design

A group of approaches having an interactive mechanism that requires a set of requests and responses or challenge responses with challenge response replies for secure authentication.

More in source Keri Request Authentication Mechanism (KRAM) by Samuel Smith

More in extended KERI glossary

interceptor

a keria class that allows to push events that are happening inside the cloud agent to other backend processes.

It is similar to the notifier class but it is used to “notify” other web services.

More in extended KERI glossary

interleaved-serialization

Serializations of different types interleaved in an overarching format

More in extended KERI glossary

internal-inconsistency

Internal is used to describe things that exist or happen inside an entity. In our scope of digital identifier its (in)consistency is considered within the defining data structures and related data stores.

In key-event-receipt-infrastructure, you are protected against internal inconsistency by the hash chain data structure of the key-event-log because the only authority that can sign the log is the controller itself.

More in extended KERI glossary

internet-assigned-numbers-authority

is the organization that oversees the allocation of IP addresses to internet service providers (ISPs).

Source

More in extended KERI glossary

interoperability

Interoperability is a characteristic of a product or system to work with other products or systems. While the term was initially defined for information technology or systems engineering services to allow for information exchange.

More on source Wikipedia

More in extended KERI glossary

interoperable

interoperability

More in extended KERI glossary

ip-address

An Internet Protocol address (IP address) is a numerical label such as ‘192.0.2.1’ that is connected to a computer network that uses the Internet Protocol for communication. An IP address serves two main functions: network interface identification and location addressing.

Much more on source Wikipedia

More in extended KERI glossary

iss

iss = vc issue, verifiable credential issuance

More in extended KERI glossary

issuance-and-presentation-exchange-protocol

provides a uniform mechanism for the issuance and presentation of ACDCs in a securely attributable manner.

More in extended KERI glossary

issuance-event

The initial transaction event log event anchored to the issuing AID’s key event log that represents the issuance of an ACDC credential.

Source: Philip Feairheller.

It’s a sort of “inception-event” of a verifiable credential.

More in extended KERI glossary

issuance-exchange

A special case of a presentation-exchange where the discloser is the issuer of the origin (Primary) ACDC of the directed-acyclic-graph formed by the set of chained authentic-chained-data-containers so disclosed.

In an issuance exchange, when the origin ACDC has an issuee, the disclosee MAY also be the origin ACDC’s Issuee.

More in extended KERI glossary

issuee

a role of an entity to which the claims of an ACDC are asserted.

Source: Dr. S. Smith

More in extended KERI glossary

issuer

a role of an entity that asserts claims and creates an ACDC from these claims.

Source: Dr. S. Smith

More in extended KERI glossary

ixn

JSON field name (attribute) for Interaction Event; its content (value) contains a hash pointer. All transaction-event-log events are anchored in a key-event-log in either ixn (interaction-event) or rot (rotation-events). This is the foundation enabling a verifiable credential protocol to be built on top of KERI.

Source Kent Bull 2023

More in extended KERI glossary

javascript-object-notation

JSON (JavaScript Object Notation, pronounced /ˈdʒeɪsən/; also /ˈdʒeɪˌsɒn/) is an open standard file format and data interchange format that uses human-readable text to store and transmit data objects consisting of attribute–value pairs and arrays (or other serializable values). It is a common data format with diverse uses in electronic data interchange, including that of web applications with servers.

More in extended KERI glossary

javascript-object-signing-and-encryption

is a framework intended to provide a method to securely transfer claims (such as authorization information) between parties. The JOSE framework provides a collection of specifications to serve this purpose.

More in extended KERI glossary

judge

A judge is an entity or component that examines the entries of one or more key-event-receipt-log and DELs of a given identifier to validate that the event history is from a non-duplicity controller and has been witnessed by a sufficient number of non-duplicitous witness such that it may be trusted or conversely not-trusted by a validator.

More in extended KERI glossary

juror

A juror has the basic task of performing duplicity detection on events and event receipts.

More in extended KERI glossary

jury

The jury is the set of entities or components acting as juror.

More in extended KERI glossary

keep

Is KERI’s and ACDC’s user interface that uses the keripy agent for its backend. It uses the REST API exposed from the keripy agent.

Source: Philip Feairheller

More in extended KERI glossary

keri-agreement-algorithm-for-control-establishment

Agreement on an event in a key event log KEL means each witness has observed the exact version of the event and each witness’ receipt has been received by every other witness.

Control establishment means that the set of agreeing witnesses, along with the controller of the identifier and associated keypairs, create a verifiable way to establish control authority for an identifier by reading all of the events in the KEL that have been agreed upon by the witnesses and the controller.

More in extended KERI glossary

keri-command-line-interface

Command line tool used to create identifiers, manage keys, query for KELs and participate in delegated identifiers or multi-signature group identifiers. It also includes operations for running witnesses, watchers and cloud agents to establish a cloud presence for any identifier.

Most commands require a “name” parameter which references a named Habitat (think wallet) for performing the operation.

More in extended KERI glossary

keri-event-stream

A stream of verifiable KERI data, consisting of the key-event-log and other data such as a transaction-event-log. This data is a CESR event stream (TODO: link to IANA application/cesr media type) and may be serialized in a file using composable-event-streaming-representation encoding. We refer to these CESR stream resources as KERI event streams to simplify the vocabulary.

Source did:webs ToIP specification

More in extended KERI glossary

keri-improvement-doc

These docs are modular so teams of contributors can independently work and create PRs of individual KIDs; KIDs answer the question “how we do it”. We add commentary to the indivudual KIDs that elaborate on the why. It has been split from the how to not bother implementors with the why.

More in extended KERI glossary

keri-ox

The RUST programming-language implementation of the KERI protocol.

More in extended KERI glossary

keri-request-authentication-method

All requests from a web client must use KRAM (KERI Request Authentication Method) for replay attack protection. The method is essentially based on each request body needing to include a date time string field in ISO-8601 format that must be within an acceptable time window relative to the server’s date time. See the KRAM Github repo

Source SKWA GitHub repo, more info in HackMD.io write-up

More in extended KERI glossary

keri-suite-search-engine

KERISSE is the Docusaurus self-education site of Web-of-Trust GitHub repo with Typesense search facilities. Because of its focus on well-versed developers in the field of SSI and the support of their journey to understand the structure of the code and how things work in the keri-suite it’s more a search engine that drills down on documentation.

More in extended KERI glossary

keri-suite

The KERI suite is the set of inter-related developments (KERI, ACDC, OOBI, CESR, IPEX, etc) under the Web-of -Trust user on Github

More in extended KERI glossary

keride

is a Rust programming language library for key-event-receipt-infrastructure. Among its features

is CESR, signing, prefixing, pathing, and parsing.

More on Github repo

More in extended KERI glossary

keridemlia

It is a contraction of key-event-receipt-infrastructure and Kademlia. It’s the distributed database of Witness IP-addresses based on a distributed-hash-table. It also does the CNAME - stuff that domain-name Services (DNS) offers for KERI: the mapping between an identifier and it’s controller AID stored in the KEL to its current wittness AID and the wittness AID to the IP address.

(@henkvancann)

More in extended KERI glossary

kerific

kerific is a front plugin or extension that currently only works for Chrome and Brave. It matches words in any text on the web that is parseable for kerific and offers buttons to various glossaries and definitions in the self-sovereign-identity field.

More in extended KERI glossary

keripy

The Python programming-language implementation of the KERI protocol.

More in extended KERI glossary

keri’s-algorithm-for-witness-agreement

a type of Byzantine Fault Tolerant (byzantine-fault-tolerance) algorithm.

Source: Dr. S.Smith

More in extended KERI glossary

kever

Kever is a key event verifier.

More in extended KERI glossary

key-compromise

Basically there are three infrastructures that are included in “key management” systems that must be protected:

  • Key pair creation and storage
  • Event signing
  • Event signature verification

So when we say “key compromise” we really mean compromise of one of those three things.

More in extended KERI glossary

key-event-log

a Verifiable data structure that is a backward and forward chained, signed, append-only log of key events for an AID. The first entry in a KEL must be the one and only Inception event of that AID.

Source Sam Smith

More in extended KERI glossary

key-event-message

Message whose body is a key event and whose attachments may include signatures on its body.

Source Sam Smith

More in extended KERI glossary

key-event-receipt-infrastructure

or the KERI protocol, is an identity system-based secure overlay for the Internet.

Source: Dr. S.Smtih

More in extended KERI glossary

key-event-receipt-log

a key event receipt log is a kel that also includes all the consistent key event receipt messages created by the associated set of witnesses. See annex key-event-receipt-log.

Source: Dr. S.Smith

More in extended KERI glossary

key-event-receipt

message whose body references a Key event and whose attachments must include one or more signatures on that Key event.

Source Sam Smith

More in extended KERI glossary

key-event

Concretely, it is the serialized data structure of an entry in the Key event log (KEL) for an AID. Abstractly, the data structure itself. Key events come in different types and are used primarily to establish or change the authoritative set of keypairs and/or anchor other data to the authoritative set of keypairs at the point in the KEL actualized by a particular entry.

Source Sam Smith

More in extended KERI glossary

key-management

management of cryptographic keys in a crypto-system. This includes dealing with the generation, exchange, storage, use, crypto-shredding (destruction) and replacement of keys (also #key-rotation). It includes cryptographic protocol design, key servers, user procedures, and other relevant protocols.

More in extended KERI glossary

key-pair

is a private key and its corresponding public key resulting from a one-way crypto-graphical function; a key pair is used with an asymmetric-key (public-key) algorithm in a so called public-key-infrastructure (PKI).

More in extended KERI glossary

key-state

a set of currently authoritative keypairs for an AID and any other information necessary to secure or establish control authority over an AID. This includes current keys, prior next key digests, current thresholds, prior next thresholds, witnesses, witness thresholds, and configurations.

More in extended KERI glossary

key-stretching

In cryptography, key stretching techniques are used to make a possibly weak key, typically a password or passphrase, more secure against a brute-force attack by increasing the resources (time and possibly space) it takes to test each possible key.

More in extended KERI glossary

key-transparency

provides a lookup service for generic records and a public, tamper-proof audit log of all record changes. While being publicly auditable, individual records are only revealed in response to queries for specific IDs.

More in extended KERI glossary

key

In our digital scope it’s a mechanism for granting or restricting access to something. MAY be used to issue and prove, MAY be used to transfer and control over identity and cryptocurrency. More

More in extended KERI glossary

keystore

A keystore in KERI is the encrypted data store that hold the private keys for a collection of AIDs.

Source: Philip Feairheller.

More in extended KERI glossary

kli

keri-command-line-interface

More in extended KERI glossary

ksn

ksn = state, key state notice

More in extended KERI glossary

large-language-model

A large language model (LLM) is a language model consisting of a neural network with many parameters (typically billions of weights or more), trained on large quantities of unlabeled text using self-supervised learning or semi-supervised learning.

More on Source Wikipedia

More in extended KERI glossary

lead-bytes

In order to avoid confusion with the use of the term pad character, when pre-padding with bytes that are not replaced later, we use the term lead bytes. So lead-bytes are added “pre-conversion”.

More in extended KERI glossary

ledger-backer

A witness in KERI that is ledger-registered. It’s a type of backer that proof its authenticity by a signing key anchored to the public key of a data item on a (public) blockchain.

More in extended KERI glossary

legal-entity-engagement-context-role-vlei-credential-governance-framework

A document that details the requirements for vlei-role-credential issued to representatives of a Legal Entity in other than official roles but in functional or other context of engagement.

Source: Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

legal-entity-official-organizational-role-vlei-credential-governance-framework

A document that details the requirements for vlei-role-credential issued to official representatives of a Legal Entity.

Source: Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

legal-entity-vlei-credential-governance-framework

A document that details the requirements for vLEI Credential issued by a qualified-vlei-issuer to a legal-entity.

More in extended KERI glossary

legal-entity

Unique parties that are legally or financially responsible for the performance of financial transactions or have the legal right in their jurisdiction to enter independently into legal contracts.

More in extended KERI glossary

legitimized-human-meaningful-identifier

An AID and its associated self-certifying trust basis gives rise to a trust domain for associated cryptographically verifiable non-repudiable statements. Every other type of identifier including human meaningful identifiers may then be secured in this resultant trust domain via an end-verifiable authorization. This authorization legitimizes that human meaningful identifier as an LID through its association with an AID. The result is a secured trust domain specific identifier couplet of aid|lid.

More in extended KERI glossary

levels-of-assurance

Identity and other trust decisions are often not binary. They are judgement calls. Any time that judgement is not a simple “Yes/No” answer, you have the option for levels of assurance. Also ‘LoA’.

More in extended KERI glossary

listed-identifier

Is a list in an authentic-chained-data-container of authorised did:webs identifier + method; the list appears in the metadata of the did:webs DID-doc.

Source: paraphrased Samuel Smith, Zoom meeting KERI dev Thursday Nov 9 2023

More in extended KERI glossary

live-attack

an attack that compromises either the current signing keys used to sign non-establishment events or the current pre-rotated keys needed to sign a subsequent establishment event. See (Security Properties of Prerotation)[#live-attacks].

Source: Dr. S.Smith

More in extended KERI glossary

liveness

Liveness refers to a set of properties of concurrent systems, that require a system to make progress despite the fact that its concurrently executing components (“processes”) may have to “take turns” in critical sections, parts of the program that cannot be simultaneously run by multiple processes.

More in extended KERI glossary

loci-of-control

Locus of control is the degree to which people believe that they, as opposed to external forces (beyond their influence), have control over the outcome of events in their lives. Also ‘LoC’.

More on wikipedia

More in extended KERI glossary

locked-state

The default status a KERI data store is in once it has been created using a passcode; it is by default encrypted.

More in extended KERI glossary

management-TEL

management-transaction-event-log

More in extended KERI glossary

management-transaction-event-log

A ‘management transaction-event-log’ will signal the creation of the Virtual Credential Registry VCR and track the list of Registrars that will act as backer for the individual _ transaction event logs (TELs)_ for each virtual-credential (VC).

More in extended KERI glossary

media-type

A Media type (formerly known as MIME type) is a standard way to indicate the nature and format of a file, in the same way as ‘image/jpeg’ for JPEG images, used on the internet.

It is a two-part identifier for file formats and format contents transmitted on the internet. Their purpose is somewhat similar to file extensions in that they identify the intended data format.

More in extended KERI glossary

message

a serialized data structure that comprises its body and a set of serialized data structures that are its attachments. Attachments may include but are not limited to signatures on the body.

Source: Dr. S.Smith

More in extended KERI glossary

messagepack

MessagePack is a computer data interchange format. It is a binary form for representing simple data structures like arrays and associative arrays. MessagePack aims to be as compact and simple as possible. The official implementation is available in a variety of languages

More in extended KERI glossary

moobi

Multi OOBI would allow to share a bunch of different end-points (oobis) all at once. A way for a single store to share multiple endpoints for that store.

More in extended KERI glossary

most-compact

An ACDC that, for a given level of disclosure, is as compact as it can be, which means

  • it has the SAIDs for each section that are not disclosed
  • it has expanded sections that are disclosed

More in extended KERI glossary

multi-factor-authentication

Authentication by combining multiple security factors. Well-known factors are what you know, what you have and what you are.

More in extended KERI glossary

multi-valent

A delegator may have multiple delegate, thereby enabling elastic horizontal scalability. Multiple delegates from a single delegator. Furthermore, each delegate may act as a delegator for its own delegates to form a nested delegation tree.

More in extended KERI glossary

multicodec

Is a self-describing multi-format, it wraps other formats with a tiny bit of self-description. A multi-codec identifier is both a variant (variable length integer) and the code identifying data.

See more at GitHub Multi-codec

More in extended KERI glossary

multiplexing

In telecommunications and computer networking, multiplexing (sometimes contracted to muxing) is a method by which multiple analog or digital signals are combined into one signal over a shared medium. The aim is to share a scarce resource - a physical transmission medium.

More on source Wikipedia-page

More in extended KERI glossary

multisig

also multi-signature or multisignature; is a digital signature scheme which allows a group of users to sign a single piece of digital data.

Paraphrased by @henkvancann from Wikipedia source

More in extended KERI glossary

naive-conversion

Non-CESR Base64 conversion. How people are used to using the Base64 encode and decode. Without pre-padding etc all the stuff CESR does to ensure aligns on 24 bit boundaries so CESR never uses the ‘=’ pad character. But naive base64 will pad if the length is not 24 bit aligned.

Source: Samuel Smith in issue 34

More in extended KERI glossary

namespace

In an identity system, an identifier can be generalized to a namespace to provide a systematic way of organizing identifiers for related resources and their attributes. A namespace is a grouping of symbols or identifiers for a set of related objects.

More in extended KERI glossary

ndigs

Digests of public keys, not keys themselves. The reason to use ndigs is to prove control over public keys or to hide keys. It’s used in Keripy and consists of a list of qualified base64 digests of public rotation key derivations.

More in extended KERI glossary

nested-cooperative-delegated-identifiers

In KERI delegations are cooperative, this means that both the delegator and delegate must contribute to a delegation. The delegator creates a cryptographic commitment in either a rotation or interaction event via a seal in a delegated establishment event. The delegate creates a cryptographic commitment in its establishment event via a seal to the delegating event.

More in extended KERI glossary

next-threshold

represents the number or fractional weights of signatures from the given set of next keys required to be attached to a Message for the Message to be considered fully signed.

More in extended KERI glossary

non-establishment-event

a Key event that does not change the current Key state for an AID. Typically, the purpose of a Non-establishment event is to anchor external data to a given Key state as established by the most recent prior Establishment event for an AID.

Source: Dr. S. Smith

More in extended KERI glossary

non-fungible-token

A non-fungible token (NFT) is a financial security consisting of digital data stored in a blockchain, a form of distributed ledger.

More in extended KERI glossary

non-interactive-authentication-design

A group of approaches having non-interactive mechanisms that pose unique problems because they do not allow a challenge response reply handshake. A request is submitted that is self-authenticating without additional interaction.

More in extended KERI glossary

non-normative

A theory is called non-normative if it does not do what has described under ‘normative’. In general, the purpose of non-normative theories is not to give answers, but rather to describe possibilities or predict what might happen as a result of certain actions.

Source.

More in extended KERI glossary

non-repudiable

Non-repudiation refers to a situation where a statement’s author cannot successfully dispute its authorship or the validity of an associated contract, signature or commitment.

The term is often seen in a legal setting when the authenticity of a signature is being challenged. In such an instance, the authenticity is being “repudiated”.

More in extended KERI glossary

non-transferable-identifier

Controlling keys over this identifier cannot be rotated and therefore this identifier is non-transferable to other control.

An identifier of this type has specific positive features like short-lived, peer to peer, one-time use, discardable, etc. that are very practical in certain use cases. Moreover non-transferable identifiers are much easier to govern than persistent identifiers that are transferable.

More in extended KERI glossary

non-transferable

No transferable (the control over) a certain digital asset in an unobstructed or loss-less manner. As opposed to transferable.

For example not legally transferable to the ownership of another entity.

More in extended KERI glossary

normative

a theory is “normative” if it, in some sense, tells you what you should do - what action you should take. If it includes a usable procedure for determining the optimal action in a given scenario.

Source.

More in extended KERI glossary

official-organizational-role

Also ‘OOR’. A person that represents the Legal Entity in an official organizational role and is issued an OOR vLEI Credential.

Source Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

one-way-function

In computer science, a one-way function is a function that is easy to compute on every input, but hard to invert given the image of a random input. Here, “easy” and “hard” are to be understood in the sense of computational complexity theory, specifically the theory of polynomial time problems.

More on Wikipedia

More in extended KERI glossary

opcode

Opcodes are meant to provide stream processing instructions that are more general and flexible than simply concatenated primitives or groups of primitives.

More in extended KERI glossary

operator

an optional field map in the Edge section that enables expression of the edge logic on edge subgraph as either a unary operator on the edge itself or an m-ary operator on the edge group.

Source: Dr. S.Smith

More in extended KERI glossary

out-of-band-introduction

Out-of-band Introductions (OOBIs) are discovery and validation of IP resources for key-event-receipt-infrastructure autonomic identifiers. Discovery via URI, trust via KERI.

The simplest form of a KERI OOBI is a namespaced string, a tuple, a mapping, a structured message, or structured attachment that contains both a KERI AID and a URL. The OOBI associates the URL with the AID.

More in extended KERI glossary

owner

Owner in ToIP glossary

More in extended KERI glossary

ownership

Ownership in ToIP glossary

More in extended KERI glossary

pad

is a character used to fill empty space, because many applications have fields that must be a particular length.

Source

More in extended KERI glossary

parside

is a bunch of generators. Responsible for pulling out a stream of bits from a CESR stream and parse it.

Sam Smith suggested for Parside to not iterate stuff, only parse chunks delimited by the count-code. (Source Cesride: meeting Feb 2 2023)

More in extended KERI glossary

partial-disclosure

a disclosure of an ACDC that partially discloses its field maps using Compact Disclosure. The Compact Disclosure provides a cryptographically equivalent commitment to the yet-to-be-disclosed content, and the later exchange of the uncompacted content is verifiable to an earlier Partial Disclosure. Unlike Selective disclosure, a partially disclosable field becomes correlatable to its encompassing block after its Full Disclosure.

Source: Dr. S. Smith

More in extended KERI glossary

partial-pre-rotation

partial-rotation

More in extended KERI glossary

partial-rotation

The pre-rotation mechanism supports partial pre-rotation or more exactly partial rotation of pre-rotated keypairs. It’s a rotation operation on a set of pre-rotated keys that may keep some keys in reserve (i.e unexposed) while exposing others as needed.

More in extended KERI glossary

party

An entity who participates or is concerned in an action, proceeding, plan, etc.

Source: ToIP

More in extended KERI glossary

passcode

A password, sometimes called a passcode (for example in Apple devices), is secret data, typically a string of characters, usually used to confirm a user’s identity.

More on source Wikipedia

More in extended KERI glossary

pathing

It was designed to sign portions of a credential aimed at complex cases like

  • a credential embedded in another credential
  • multiple signers, only signing portions of a credential (partial signing)

More in extended KERI glossary

payload

The term ‘payload’ is used to distinguish between the ‘interesting’ information in a chunk of data or similar and the overhead to support it. The payload refers to the interesting part.

More in extended KERI glossary

peer-to-peer

Peer-to-peer (P2P) computing or networking is a distributed application architecture that partitions tasks or workloads between peers. Peers are equally privileged, equipotent participants in the network. They are said to form a peer-to-peer network of nodes

More on source Wikipedia

More in extended KERI glossary

percolated-discovery

a discovery mechanism for information associated with an AID or a SAID, which is based on Invasion Percolation Theory. Once an entity has discovered such information, it may in turn share what it discovers with other entities. Since the information so discovered is end-verifiable, the percolation mechanism and percolating intermediaries do not need to be trusted.

Source: Dr. S. Smith

percolated-information-discovery

More in extended KERI glossary

percolated-information-discovery

In the OOBI protocol, a discovery mechanism for the KERI and the ACDC protocols is provided by a bootstrap that enables Percolated Information Discovery (PID), which is based on Invasion Percolation Theory.

After related information for discovery and verification is bootstrapped from the OOBI, subsequent authorization is non-interactive, thus making it highly scalable. This provides what we call zero-trust percolated discovery or speedy percolated discovery.

More in extended KERI glossary

perfect-security

a special case of Information theoretic security itps.

Source: Dr. S. Smith

More in extended KERI glossary

persistent-data-structure

An append only verifiable data structure. What we sign may not change.

More in extended KERI glossary

persistent-identifier

transferable-identifier

More in extended KERI glossary

pii

personally identifiable information

More in extended KERI glossary

pipelining

In computing, a pipeline, also known as a data pipeline, is a set of data processing elements connected in series, where the output of one element is the input of the next one. The elements of a pipeline are often executed in parallel or in time-sliced fashion. Some amount of buffer storage is often inserted between elements.

More on source Wikipedia-page

More in extended KERI glossary

post-pad

the action and / or result of extending a string with trailing pad characters to align to a certain length in bits or bytes.

More in extended KERI glossary

post-quantum

In cryptography, post-quantum cryptography (PQC) (sometimes referred to as quantum-proof, quantum-safe or quantum-resistant) refers to cryptographic algorithms (usually public-key algorithms) that are thought to be secure against a cryptanalytic attack by a quantum computer.

More on source Wikipedia

More in extended KERI glossary

pre-pad

the action and / or result of prepending a string with leading pad characters to align to a certain length in bits or bytes.

More in extended KERI glossary

pre-rotation

Cryptographic commitment to next rotated key set in previous rotation or inception-event.

More in extended KERI glossary

prefix

A prefix that is composed of a basic Base-64 (URL safe) derivation code pre-pended to Base-64 encoding of a basic public digital signing key.

Including the derivation code in the prefix binds the derivation process along with the public key to the resultant identifier.

More in extended KERI glossary

presentation-exchange

An exchange that provides disclosure of one or more authentic-chained-data-containers between a Discloser and a Disclosee.

A presentation exchange is the process by which authenticity information may be exchanged between two parties, namely, the discloser and disclosee.

More in extended KERI glossary

pretty-good-privacy

Is an encryption program that provides cryptographic privacy and authentication for data communication. PGP is used for signing, encrypting, and decrypting texts, e-mails, files, directories, and whole disk partitions and to increase the security of e-mail communications. Phil Zimmermann developed PGP in 1991.

More on wikipedia

So also the often confusing GPG term.

More in extended KERI glossary

primary-root-of-trust

In KERI a root-of-trust that is cryptographically verifiable all the way to its current controlling key pair in a PKI.

The characteristic primary is one-on-one related to the entropy used for the creation of (the seed of) the private keys.

More in extended KERI glossary

primitive

a serialization of a unitary value. All Primitives in KERI must be expressed in composable-event-streaming-representation.

Source: Dr. S.Smith

More in extended KERI glossary

privacy-washing

De-identification so that it provides a personal data safe harbour and could be legally acceptable forwarded.

More in extended KERI glossary

privacy

Privacy is the ability of an individual or group to seclude themselves or information about themselves, and thereby express themselves selectively.

The domain of privacy partially overlaps with security, which can include the concepts of appropriate use and protection of information. Privacy may also take the form of bodily integrity.

More on source Wikipedia

More in extended KERI glossary

proem

A “proem” is an introductory statement, preamble, or preface. It sets the stage for the content that follows, often providing context, framing the discussion, or outlining the purpose and scope of the material.

More in extended KERI glossary

promiscuous-mode

It is the mode a watcher runs in. A watcher uses the same code as a witness. However a watcher does so “lacking standards of selection; acting without careful judgment; indiscriminate”. Or “Showing little forethought or critical judgment; casual.”

Source

More in extended KERI glossary

proof-of-authority

Proof that somebody or something has certain rights or permissions. It’s about data. Whereas proof-of-authorship is about data and its original creator.

A proof-of-authority provides verifiable authorizations or permissions or rights or credentials.

More in extended KERI glossary

proof-of-authorship

Proof that somebody or something has originally created certain content. It’s about data’s inception. Whereas proof-of-authority is about rights attached to this data.

More in extended KERI glossary

protocol

Generic term to describe a code of correct conduct. Also called “etiquette”: a code of personal behavior.

More in extended KERI glossary

provenance

From Wikipedia (Source):

Provenance (from the French provenir, ‘to come from/forth’) is the chronology of the ownership, custody or location of a historical object. The term was originally mostly used in relation to works of art but is now used in similar senses in a wide range of fields, including archaeology, paleontology, archives, manuscripts, printed books, the circular economy, and science and computing.

More in extended KERI glossary

provenanced

The act of verifying authenticity or quality of documented history or origin of something.

More in extended KERI glossary

pseudo-random-number

A (set of) value(s) or element(s) that is statistically random, but it is derived from a known starting point and is typically repeated over and over.

More in extended KERI glossary

public-key-infrastructure

Is a set of roles, policies, hardware, software and procedures needed to create, manage, distribute, use, store and revoke digital certificates and manage public-key encryption.

Public Private Key caveat to KERI

More on Wikipedia

More in extended KERI glossary

public-transaction-event-log

is a public hash-linked data structure of transactions that can be used to track state anchored to a key-event-log.

More in extended KERI glossary

public-verifiable-credential-registry

is a form of a Verifiable Data Registry that tracks the issuance/revocation state of credentials issued by the controller of the key-event-log. Two types of TELs will be used for this purpose: management-transaction-event-log and virtual-credential-transaction-event-log.

More in extended KERI glossary

qry

qry = query

More in extended KERI glossary

quadlet

a group of 4 characters in the T domain and equivalently in triplets of 3 bytes each in the B domain used to define variable size.

Source: Dr. S. Smith

More in extended KERI glossary

qualified-vlei-issuer-vlei-credential-governance-framework

A document that details the requirements to enable this Credential to be issued by GLEIF to qualified-vlei-issuer which allows the Qualified vLEI Issuers to issue, verify and revoke legal-entity-vlei-credential-governance-framework, legal-entity-official-organizational-role-vlei-credential-governance-framework, and legal-entity-engagement-context-role-vlei-credential-governance-framework.

More in extended KERI glossary

qualified-vlei-issuer

The contracting party to the vLEI Issuer Qualification Agreement that has been qualified by GLEIF as a Qualified vLEI Issuer.

Source: Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

qualified

When qualified, a cryptographic primitive includes a prepended derivation code (as a proem), that indicates the cryptographic algorithm or suite used for that derivation.

More in extended KERI glossary

qvi-authorized-representative

A designated representative of a QVI authorized, to conduct QVI operations with GLEIF and legal-entity. Also referring to a person in the role of a QAR.

Paraphrased by @henkvancann from source Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

race-condition

A race condition or race hazard is the condition of an electronics, software, or other system where the system’s substantive behavior is dependent on the sequence or timing of other uncontrollable events. It becomes a bug when one or more of the possible behaviors is undesirable.

Source.

More in extended KERI glossary

rainbow-table-attack

A rainbow table attack is a password-cracking method that uses a special table (a “rainbow table”) to crack the password hashes in a database.

More in extended KERI glossary

rct

rct = receipt

More in extended KERI glossary

read-update-nullify

Read, update, nullify are a set of actions you (or a server) can take on data. “Read” means to view it, “update” means to change it, and “nullify” means to invalidate it, but not “Delete” it. Mind you, there’s also no “Create”.

More in extended KERI glossary

receipt-log

ordered record of all key event receipts for a given set of witnesses.

More in extended KERI glossary

receipt

event message or reference with one or more witness signatures.

See Also:

key-event-receipt

More in extended KERI glossary

reconciliation

Reconciliation is the process in which you decide to accept a fork of the key-event-log or not.

Source: Samuel Smith, Zoom meeting Jan 2 2024.

More in extended KERI glossary

redundant-credential

Multiple credentials issued by the same issuer (e.g. a QVI). They do not have anything to do with each other. They are independently valid.

More in extended KERI glossary

registrar

identifiers that serve as backers for each transaction-event-log (TEL) under its provenance. This list of Registrars can be rotated with events specific to a certain type of TEL. In this way, a Registrar is analogous to a Backer in KERI KELs and Registrar lists are analogous to Backer lists in KERI KELs.

More in extended KERI glossary

registration-interaction

Setup/Registration interaction, new AID and authorization to establish access control. You present a (vLEI) credential. You don’t want that captured and misused. Narrowing the scope to a certain role (e.g. Document Submitter) is a pre-registration via delegation authority.

More in extended KERI glossary

registry

In our digital mental model it’s an official digital record book. When people refer to a registry, they usually mean a specific instance, within a multi-tenant registry. E.g. Docker Hub is a multi-tenant registry, where there’s a set of official / public images.

More in extended KERI glossary

replay-attack

A replay attack occurs when a cybercriminal eavesdrops on a secure network communication, intercepts it, and then fraudulently delays or resends it to misdirect the receiver into doing what the hacker wants.

More in extended KERI glossary

repo

Software is our line of work. In this, ‘repo’ is the short hand for ‘Repository’, mostly referring to a software repo(sitory) on Github.com, Gitlab (https://gitlab.com) or other software repository hosting services.

More in extended KERI glossary

reputation

Consistent behaviour over time on the basis of which anyone else makes near-future decisions.

Source: Samuel Smith at IIW37.

More in extended KERI glossary

reputational-trust

Established by a trusted party offering identity-assurance.

More in extended KERI glossary

reserve-rotation

One important use case for partial-rotation is to enable pre-rotated key pairs designated in one establishment-event to be held in reserve and not exposed at the next (immediately subsequent) establishment event.

Source IETF-KERI draft 2022 by Samual Smith.

More in extended KERI glossary

rev

rev = vc revoke, verifiable credential revocation

More in extended KERI glossary

revocation-event

An event that revokes control-authority over an identifier. From that point in time the authoritative key-pairs at hand are not valid anymore.

More in extended KERI glossary

revocation

Revocation is the act of recall or annulment. It is the cancelling of an act, the recalling of a grant or privilege, or the making void of some deed previously existing.

More on source Wikipedia

More in extended KERI glossary

ricardian-contract

The Ricardian contract, as invented by Ian Grigg in 1996, is a method of recording a document as a contract at law, and linking it securely to other systems, such as accounting, for the contract as an issuance of value.

More in extended KERI glossary

root-autonomic-identifier

An entity may provide the root-of-trust for some ecosystem (with delegation )via its root AID. Let’s call this the RID for “root AID”. The RID must be protected using the highest level of security in its key-management.

More in extended KERI glossary

root-of-trust

A root-of-trust is some component of a system that is security by design and its security characteristics may be inherently trusted or relied upon by other components of the system.

More in extended KERI glossary

rot

JSON field name (attribute) for Rotation Event; its content (value) contains a hash pointer. All transaction-event-log events are anchored in a key-event-log in either ixn (interaction-event) or rot (rotation-events). This is the foundation enabling a verifiable credential protocol to be built on top of KERI.

Source Kent Bull 2023

More in extended KERI glossary

rotation-authority

The (exclusive) right to rotate the authoritative key pair and establish changed control authority.

More in extended KERI glossary

rotation-event

an Establishment Event that provides the information needed to change the Key state, which includes a change to the set of authoritative keypairs for an AID.

Source: Dr. S.Smith

More in extended KERI glossary

rotation

The operation of revoking and replacing the set of authoritative key-pair for an AID. This operation is made verifiable and duplicity evident upon acceptance as a rotation event that is appended to the AID’s KEL.

Source Sam Smith

More in extended KERI glossary

rpy

rpy = reply

More in extended KERI glossary

rules

a top-level field map within an ACDC that provides a legal language as a Ricardian Contract, which is both human and machine-readable and referenceable by a cryptographic digest.

Source: Dr. S. Smith

More in extended KERI glossary

run-off-the-crud

RUN off the CRUD is an alternative to the traditional CRUD approach to defining basic operations on resources in data management systems (e.g., databases, APIs). RUN stands for Read, Update, Nullify and bears a nuanced approach to deletion.

More in extended KERI glossary

sally

is an implementation of a verification service and acting as a reporting server. It is purpose-built software for the vLEI ecosystem to allow participants in the vLEI ecosystem present credentials, so the GLEIF Reporting API can show what vLEI are; issued to legal-entity.

More in extended KERI glossary

salt

random data fed as an additional input to a one-way function that hashes data.

Source: Dr. S. Smith

More in extended KERI glossary

salter

A primitive that represents a seed. It has the ability to generate new signers.

Source by Jason Colburne

More in extended KERI glossary

salty-nonce-blinding-factor

For ease of sharing a secret and hiding information with this secret of Blindable State TELs we use a Salty Nonce Blinding Factor. You’d like to hide the state of certain credentials to some verifiers in the future, while keeping the state verifiable for others.

More in extended KERI glossary

schema-namespace-registry

a centrally managed schema-registry where corporations or individuals reserve schemas within a specific namespace in order to have an interoperable schema that is labeled with a corporation-specific or individual-specific namespace.

More in extended KERI glossary

schema-registry

Central registry for credential schemas based on namespaces.

More in extended KERI glossary

schema

the said of a JSON schema that is used to issue and verify an ACDC.

Source: Dr. S.Smith

More in extended KERI glossary

seal

a seal is a cryptographic commitment in the form of a cryptographic digest or hash tree root (Merkle root) that anchors arbitrary data or a tree of hashes of arbitrary data to a particular event in the key event sequence.

Source: Dr. S. Smith

More in extended KERI glossary

secondary-root-of-trust

In KERI its a root-of-trust that, for its secure attribution, depends on another verifiable data structure (VDS) which MUST be a primary-root-of-trust.

By its nature and cryptographic anchoring via seal to a primary root-of-trust, a secondary root-of-trust still has a high level of trustability and can be automatically verified.

More in extended KERI glossary

secure-asset-transfer-protocol

An IETF protocol (and working group) in the making (as of mid 2022) for moving assets between blockchains.

More in extended KERI glossary

secure-attribution

Secure attribution is strongly related to making and proving statements. A controller makes statements to the a validator or verifier, who in turn validates the statements issued. A controllerowns” the statement: content and attribution via digital signatures. Secure attribution is “whodunit?!” in cyberspace.

More in extended KERI glossary

secure-private-authentic-confidentiality

ToIP Trust Spanning Layer Group realized we do have a secure authentication layer (KERI) but we don’t have a secure confidentiality and privacy mechanism. Sam Smith proposes SPAC paper to define this.

Related:

https://www.usenix.org/system/files/sec22-cohen.pdf

More in extended KERI glossary

secure

security

More in extended KERI glossary

security-cost-performance-architecture-trade-off

The degree of protection offered by a key management infrastructure usually forces a trade-off between security, cost, and performance.

Typically, key generation happens relatively infrequently compared to event signing. But highly secure key generation may not support highly performant signing. This creates an architecture trade-off problem.

Paraphrased from source Universal Identifier Theory by Samuel Smith

More in extended KERI glossary

security-overlay-properties-trillema

An identifier system has some degree of any combination of the three properties authenticity, privacy and confidentiality, but not all three completely.

More in extended KERI glossary

security

‘secure’ is free from or not exposed to danger or harm; safe. For identifiers security typically means secure from exploit or compromise. More specifically an identifier is secure with respect to an entity if there is a mechanism by which that entity may prove it has controller over the identifier.

More in extended KERI glossary

seed

In cryptography a ‘seed’ is a pseudorandomly generated number, often expressed in representation of a series of words.

Paraphrased from wikipedia

More in extended KERI glossary

selective-disclosure

a disclosure of an ACDC that selectively discloses its attributes using Compact Disclosure. The set of selectively disclosable attributes is provided as an array of blinded blocks where each attribute in the set has its own dedicated blinded block. Unlike Partial Disclosure, the selectively disclosed fields are not correlatable to the so far undisclosed but selectively disclosable fields in the same encompassing block.

Source: Dr. S. Smith

More in extended KERI glossary

self-addressed-data

a representation of data content from which a SAID is derived. The SAID is both cryptographically bound to (content-addressable) and encapsulated by (self-referential) its SAD said.

Source: Dr. S.Smith

More in extended KERI glossary

self-addressing-data

an identifier that is content-addressable and self-referential. A SAID is uniquely and cryptographically bound to a serialization of data that includes the SAID as a component in that serialization said.

Source: Dr. S. Smith

More in extended KERI glossary

self-addressing-identifier

any identifier that is deterministically generated out of the content, or a digest of the content.

Source: Dr. S. Smtih

More in extended KERI glossary

self-authenticating

self-certifying-identifier

More in extended KERI glossary

self-certifying-identifier

a type of Cryptonym that is uniquely cryptographically derived from the public key of an asymmetric signing keypair (public, private).

Source: Dr. S. Smith

More in extended KERI glossary

self-framing

a textual or binary encoding that begins with type, size, and value so that a parser knows how many characters (when textual) or bytes (when binary) to extract from the stream for a given element without parsing the rest of the characters or bytes in the element is Self-Framing.

More in extended KERI glossary

self-sovereign-identity

Self-Sovereign Identity (SSI) is a term that has many different interpretations, and that we use to refer to concepts/ideas, architectures, processes and technologies that aim to support (autonomous) parties as they negotiate and execute electronic transactions with one another.

Paraphrased by @henkvancann, sources eSSIF-lab and ToIP.

More in extended KERI glossary

self-sovereignty

Self sovereignty in Trust over IP wiki.

More in extended KERI glossary

semver

Semantic Versioning Specification 2.0. See also (https://semver.org/)[https://semver.org/].

Source: Dr. S.Smith

More in extended KERI glossary

server-sent-event

Mailbox notifications; a streaming service for the agent U/I, to get notifications from the KERI system itself.

More in extended KERI glossary

service-endpoint

In our context we consider a web service endpoint which is a uniform-resource-locator at which clients of specific service can get access to the service.

More in extended KERI glossary

siger

indexed-signature

More in extended KERI glossary

signed-digest

commitment to content, by digitally signing a digest of this content.

More in extended KERI glossary

signer

A primitive that represents a private key. It has the ability to create Sigers and Cigars (signatures).

Source by Jason Colburne

More in extended KERI glossary

signify-keria-request-authentication-protocol

SKRAP is a client to the KERIA server. Mobile clients will be using SKRAP to connect to KERI AIDs via agents in the new, multi-tenant Mark II Agent server, keria.

More in extended KERI glossary

signify

Signify is a web client key-event signing - and key pair creation app that minimizes the use of KERI on the client.

More in extended KERI glossary

signing-authority

The authority to sign on behalf of the controller of the authoritative key pair. Often in situation where delegation has taken place, e.g. a custodial agent. These are limited rights because rotation-authority is not included.

More in extended KERI glossary

signing-threshold

Is the minimum number of valid signatures to satisfy the requirement for successful verification in a threshold-signature-scheme.

More in extended KERI glossary

simple-keri-for-web-auth

A KERI implementation that sacrifices performance or other non-security feature for usability. In general a narrow application of KERI may not require all the features of KERI but those features that it does support must still be secure.

More on source Github Repo SKWA.

More in extended KERI glossary

single-signature-identifier

or single sig identifier; is an identifier controlled by a one-of-one signing key-pair

More in extended KERI glossary

sniffable

A stream is sniffable as soon as it starts with a group code or field map; in fact this is how our parser (parside) works. and detects if the CESR stream contains a certain datablock.

The datablock of CESR binary, CESR Text, JSON, CBOR, MGPK have an Object code or the Group code (binary or text) and it’s always a recognizable and unique three bit combination.

More in extended KERI glossary

sniffer

The sniffer is part of parside and detects if the CESR stream contains CESR binary, CESR Text, JSON, CBOR, MGPK.

More in extended KERI glossary

solicited-issuance

The issuance of a Legal Entity vLEI Credentials, OOR vLEI Credentials and ECR vLEI Credentials upon receipt by the QAR of a Fully Signed issuance request from the AVR(s) of the legal-entity.

Source: Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

source-of-truth

The source of truth is a trusted data source that gives a complete picture of the data object as a whole.

Source: LinkedIN.

More in extended KERI glossary

spanning-layer

An all encompassing layer horizontal layer in a software architecture. Each trust layer only spans platform specific applications. It bifurcates the internet trust map into domain silos (e.g. twitter.com), because there is no spanning trust layer.

More in extended KERI glossary

spurn

To reject. In KERI, “spurn” refers to a cryptographic or protocol-based act of rejecting an invalid or untrusted event. This rejection is deliberate and purposeful, ensuring the system’s integrity by disregarding information that does not meet the necessary validation criteria. The verb ‘spurn’ is first used in the IPEX specification.

More in extended KERI glossary

ssi-system

The SSI Infrastructure consists of the technological components that are deployed all over the world for the purpose of providing, requesting and obtaining data for the purpose of negotiating and/or executing electronic transactions.

Paraphrased by @henkvancann based on source eSSIF-lab

More in extended KERI glossary

stable

Refers to the state of cryptographic verifiability across a network or system. It generally implies that a particular identifier, event, or data set is consistent, fully verified, and cannot be contested within KERI.

More in extended KERI glossary

stale-event

A stale key event is an outdated or irrelevant (key) event involving an stale-key that may compromise security.

More in extended KERI glossary

stale-key

A stale key is an outdated or expired encryption key that should no longer be used for securing data

More in extended KERI glossary

stream

a CESR Stream is any set of concatenated Primitives, concatenated groups of Primitives, or hierarchically composed groups of primitives.

Source: Dr. S. Smith

More in extended KERI glossary

streamer

A convenience class for supporting stream parsing, including nested (tunneled, encrypted) CESR streams. Streams can be a mixture/combination of different primitive, including other streams. A stream is a concatenation of primitives.

Source: Kent Bull in chat Zoom meeting KERI Aug 6, 2024.

More in extended KERI glossary

strip-parameter

tells us what part of the CESR stream will be parsed by which code.

More in extended KERI glossary

sub-shell

A subshell is basically a new shell just to run a desired program. A subshell can access the global variables set by the ‘parent shell’ but not the local variables. Any changes made by a subshell to a global variable is not passed to the parent shell.

Source

More in extended KERI glossary

supermajority

Sufficient majority that is labeled immune from certain kinds of attacks or faults.

More in extended KERI glossary

targeted-acdc

an ACDC with the presence of the Issuee field in the attribute or attribute aggregate sections.

Source: Dr. S.Smith

untargeted-acdc

More in extended KERI glossary

tcp-endpoint

This is a service-endpoint of the web transmission-control-protocol

More in extended KERI glossary

text-binary-concatenation-composability

An encoding has composability when any set of self-framing concatenated primitives expressed in either the text domain or binary domain may be converted as a group to the other domain and back again without loss.

More in extended KERI glossary

tholder

t-holder object that supports fractionally-weighted signing-threshold

More in extended KERI glossary

threshold-of-accountable-duplicity

The threshold of accountable duplicity (TOAD) is a threshold number M that the controller declares to accept accountability for an event when any subset M of the N witnesses confirm that event. The threshold M indicates the minimum number of confirming witnesses the controller deems sufficient given some number F of potentially faulty witnesses, given that M >= N - F. This enables a controller to provide itself with any degree of protection it deems necessary given this accountability.

More in extended KERI glossary

threshold-signature-scheme

or TSS; is a type of digital signature protocol used by Mutli-party Computation (MPC) wallets to authorize transactions or key state changes.

Source Cryptoapis

More in extended KERI glossary

threshold-structure-security

A threshold structure for security allows for weaker key management or execution environment infrastructure individually, but achieve greater overall security by multiplying the number of attack surfaces that an attacker must overcome to compromise a system.

More in extended KERI glossary

top-level-section

The fields of an ACDC in compact-variant. The value of a top level section field is either the SAD or the SAID of the SAD of the associated section.

An Issuer commitment via a signature to any variant of ACDC (compact, full, etc) makes a cryptographic commitment to the top-level section fields shared by all variants of that ACDC.

Paraphrased by @henkvancann based on source.

More in extended KERI glossary

trans-contextual-value

Value that is transferrable between contexts. How do we recapture the value in our data? 1- Leverage cooperative network effects 2- Retake control of our data.

Source Samuel Smith

More in extended KERI glossary

transaction-event-log

The set of transactions that determine registry state form a log called a Transaction Event Log (TEL). The TEL provides a cryptographic proof of registry state by reference to the corresponding controlling key-event-log. Any validator may therefore cryptographically verify the authoritative of the registry.

More in extended KERI glossary

transfer-off-ledger

The act of transferring control authority over an identifier from a ledger (or blockchain) to the native verifiable KERI data structure Key Event Log.

More in extended KERI glossary

transferable-identifier

Control over the identifier transferable by rotation.

A synonym is ‘persistent identifier’.

More in extended KERI glossary

transferable

Capable of being transferred or conveyed from one place or person to another. Place can be its and bits.

The adjective transferable also means ‘Negotiable’, as a note, bill of exchange, or other evidence of property, that may be conveyed from one person to another by indorsement or other writing; capable of being transferred with no loss of value. As opposed to non-transferable.

Source

More in extended KERI glossary

transmission-control-protocol

One of the main protocols of the Internet protocol suite. It originated in the initial network implementation in which it complemented the Internet Protocol (IP).

More on source Wikipedia.

More in extended KERI glossary

tritet

3 bits. See Performant resynchronization with unique start bits.

Source: Dr. S. Smith

More in extended KERI glossary

trust-domain

A trust domain is the ecosystem of interactions that rely on a trust basis. A trust basis binds controllers, identifiers, and key-pairs. For example the Facebook ecosystem of social interactions is a trust domain that relies on Facebook’s identity system of usernames and passwords as its trust basis.

(Source whitepaper)

More in extended KERI glossary

trust-spanning-protocol

Protocol using verifiable-identifiers that signs every single message on the internet and makes them verifiable.

More in extended KERI glossary

trusted-execution-environment

Protected hardware/software/firmware security system. The controller may protect its key generation, key storage, and event signing infrastructure by running it inside a trusted execution environment (TEE).

More in extended KERI glossary

trusted-platform-module

A device that enhances the security and privacy (of identity systems) by providing hardware-based cryptographic functions.

# Functions

A TPM can generate, store, and protect encryption keys and authentication credentials that are used to verify the identity of a user or a device.

A TPM can also measure and attest the integrity of the software and firmware that are running on a system, to ensure that they have not been tampered with or compromised.

# Form

A TPM can be implemented as a physical chip, a firmware module, or a virtual device.

Source: Bing chat sept 2023

More in extended KERI glossary

ts-node

npm package that lets you run typescript from a shell

More in extended KERI glossary

uniform-resource-locator

A Uniform Resource Locator (URL), colloquially termed a web address, is a reference to a web resource that specifies its location on a computer network and a mechanism for retrieving it.

More in extended KERI glossary

univalent

In identifier systems, univalent means having a unique and non-ambiguous identifier for each entity or resource. This means that there is a one-to-one correspondence between the identifiers and the entities, and that no two different entities share the same identifier.

Source: Bing chat, Sept 2023

More in extended KERI glossary

unpermissioned-correlation

a correlation established between two or more disclosed ACDCs whereby the discloser of the ACDCs does not permit the disclosee to establish such a correlation.

Source: Dr. S. Smith

More in extended KERI glossary

unsolicited-issuance

Issuance of a Legal Entity vLEI Credential upon notice by a QAR to the AVR(s) of the Legal Entity that a Legal Entity vLEI Credential has been solicited on the legal-entity’s behalf.

Source: Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

untargeted-acdc

an ACDC without the presence of the Issuee field in the attribute or attribute aggregate sections.

Source: Dr. S. Smith

targeted-acdc

More in extended KERI glossary

user-interface

A user interface (UI or U/I) is the space where interactions between humans and machines occur.

More in extended KERI glossary

vLEI

verifiable-legal-entity-identifier

More in extended KERI glossary

validate

ESSIF-lab definition of validate. Although this definition is very general, in the KERI/ACDC vocabulary, ‘validate’ currently has extra diverse meanings extending the one of eSSIF-lab, such as

  • evaluate

More in extended KERI glossary

validator

any entity or agent that evaluates whether or not a given signed statement as attributed to an identifier is valid at the time of its issuance.

Source: Dr. S. Smith

More in extended KERI glossary

variable-length

a type of count code allowing for vaiable size signatures or attachments which can be parsed to get the full size.

Source: Dr. S. Smith

More in extended KERI glossary

vcp

vcp = vdr incept, verifiable data registry inception

More in extended KERI glossary

vdr

verifiable-data-registry

More in extended KERI glossary

veracity

The quality of being true; contrast authenticity. When a newspaper publishes a story about an event, every faithful reproduction of that story may be authentic — but that does not mean the story was true (has veracity).

More in extended KERI glossary

verfer

A primitive that represents a public key. It has the ability to verify signatures on data.

Source by Jason Colburne

More in extended KERI glossary

verifiable-credential

Verifiable credentials (VCs) are an open standard for digital credentials. They can represent information found in physical credentials, such as a passport or license, as well as new things that have no physical equivalent, such as ownership of a bank account.

More in extended KERI glossary

verifiable-data-registry

A role a system might perform by mediating issuance and verification of ACDCs. See verifiable data registry.

Source: Dr. S. Smith

More in extended KERI glossary

verifiable-data-structure

A verifiable data structure is a data structure that incorporates cryptographic techniques to ensure the integrity and authenticity of its contents. It allows users to verify the correctness of the data stored within the structure without relying on a trusted third party.

#Sources-Definition-ChatGPT

More in extended KERI glossary

verifiable-identifier

Cryptographically verifiable authentic decentralized identifier (verfiable DID)

More in extended KERI glossary

verifiable-legal-entity-identifier

Verifiable credentials are issued by authorized validation agents (QVI) under the governance of GLEIF, who delegate tasks to these agents. They provide cryptographic proof that the information about a legal entity, as linked to its Legal Entity Identifier (LEI), is verifiably authentic, accurate, and up-to-date.

More in extended KERI glossary

verifiable

a condition of a KEL: being internally consistent with the integrity of its backward and forward chaining digest and authenticity of its non-repudiable signatures.

Source: Dr. S. Smith

Explanation

Able to cryptographically verify a certain data structure on its inconsistency and its authenticity

More in extended KERI glossary

verification

An action an agent (of a principal) performs to determine the authenticity of a claim or other digital object using a cryptographic key.

Source: ToIP glossary, Jan 2024.

More in extended KERI glossary

verified-integrity

A mechanism that can unambiguously assess whether the information is/continues to be whole, sound and unimpaired

More in extended KERI glossary

verifier

any entity or agent that cryptographically verifies the signature(s) and digests on an event Message.

Source Dr. S. Smith

More in extended KERI glossary

verify-signature

Applying an algorithm that, given the message, public key and signature, either accepts or rejects the message’s claim to authenticity.

More in extended KERI glossary

verify

The act, by or on behalf of a party, of determining whether that data is authenticity (i.e. originates from the party that authored it), timely (i.e. has not expired), and conforms to other specifications that apply to its structure.

Source eSSIF-lab in eSSIF-lab glossary

More in extended KERI glossary

version-code

tells you which set of tables to load, it tells the table state. It’s a unique code. what version of the table is going to load.

More in extended KERI glossary

version-string

the first field in any top-level KERI field map in which it appears.

More in extended KERI glossary

version

an instance of a KEL for an AID in which at least one event is unique between two instances of the kel.

Source: Dr. S. Smith

More in extended KERI glossary

virtual-credential-transaction-event-log

will track the issued or revoked state of each virtual credential (VC) and will contain a reference to its corresponding management transaction event log (management TEL).

More in extended KERI glossary

virtual-credential

Digital representations of claims or identity attributes, often used in online environments.

More in extended KERI glossary

vlei-credential

Credential concerning a verifiable Legal Entity Identifier, residing in the GLEIS and compliant with one or more of the GLEIF governance-frameworks

More in extended KERI glossary

vlei-ecosystem-governance-framework

The Verifiable LEI (vLEI) Ecosystem governance-framework Information Trust Policies. It’s a document that defines the information security, privacy, availability, confidentiality and processing integrity policies that apply to all vLEI Ecosystem Members.

Paraphrased by @henkvancann from source Draft vLEI Ecosystem Governance Framework Glossary.

More in extended KERI glossary

vlei-role-credential

It is a vlei-credential that attests to a role within a legal entity to an individual or an entity. It cryptographically proves that the individual or entity is authorized to act in that role on behalf of the legal entity.

More in extended KERI glossary

vrt

vrt = vdr rotate, verifiable data registry rotation

More in extended KERI glossary

wallet

A crypto wallet is a device, physical medium, program or a service which stores the public and/or private keys for cryptocurrency transactions and digital identifiers.

Paraphrased by @henkvancann from source Wikipedia

More in extended KERI glossary

watcher

an entity or component that keeps a copy of a kerl for an identifier but that is not designated by the controller of the identifier as one of its witnesses. See annex watcher.

Source: Dr. S.Smith

More in extended KERI glossary

web-of-trust

In cryptography, a web of trust is a concept used in PGP, gnu-privacy-guard, and other OpenPGP-compatible systems to establish the authenticity of the binding between a public key and its owner.

More in extended KERI glossary

weight-of-weights

There are 2 levels in the multi-sign weighted thresholds of multisig in KERI because the solution only needs to focus on tightly cooperating teams.

  • An individual using split keys over devices
  • A team of teams

All other use cases can be solved by other means in KERI (e.g. delegation).

More in extended KERI glossary

weight

an optional field map in the Edge section that provides edge weight property that enables directed weighted edges and operators that use weights.

Source: Dr. S.Smith

More in extended KERI glossary

well-known-witnesses

Witness identifier creation by using salts to initialize their key stores so that you can predict what identifiers will be created. For testing purposes only!

More in extended KERI glossary

witness

a witness is an entity or component designated (trusted) by the controller of an identifier. The primary role of a witness is to verify, sign, and keep events associated with an identifier. A witness is the controller of its own self-referential identifier which may or may not be the same as the identifier to which it is a witness. See also keri’s-algorithm-for-witness-agreement.

Source: Dr. S. Smith

More in extended KERI glossary

xip

A XIP message allows a transaction set to be a mini peer to peer exchange to become a verifiable data structure. It makes the transaction become duplicity evident.

Source KERI meeting 2024-03-12

More in extended KERI glossary

zero-trust-computing

A security model centered on the principle of “never trust, always verify.” It assumes that threats can exist inside and outside the network, and thus, no entity — a device, user, or system — is inherently trusted. This approach requires continuous verification of all users and devices attempting to access network resources.

More in extended KERI glossary

zero-trust

a Zero Trust approach trusts no one.

More in extended KERI glossary

# Demo of example markup in Spec-Up-T and Markdown

# Blockquote

To be, or not to be, that is the question: Whether 'tis nobler in the mind to suffer The slings and arrows of outrageous fortune, Or to take arms against a sea of troubles And by opposing end them. To die—to sleep, No more;

# Notices

::: note Basic Note
  Check this out.
:::
NOTE

Check this out.

NOTE

Here’s another.

NOTE

And one more!

NOTE

One last note!!!

::: issue Issue Notice
  I take issue with that, kind sir.
:::
ISSUE

I take issue with that, kind sir.

::: warning Warning Notice
  Houston, I think we have a problem
:::
WARNING

Houston, I think we have a problem

::: todo Really Important
  Get this done!
:::
TODO

Get this done!

::: example Code Example
  Put your code block here
:::
EXAMPLE
// Some comment in JSON
{
  "foo": "bar",
  "baz": 2
}

# Content Insertion

Use the following format to pull in content from other files in your project:

This text has been inserted here from another file: [[insert: assets/test.text]]

This text has been inserted here from another file: Beam me in, Scotty!

You can even insert content within more complex blocks, like the JSON object below which is being pulled in and rendered in a syntax-highlighted example block:

::: example Code Example
```json
[[insert: assets/test.json]]
```
:::
EXAMPLE
{
  "foo": {
    "bar": 1
  }
}

# Tables

Stage | Direct Products | ATP Yields
----: | --------------: | ---------:
Glycolysis | 2 ATP ||
^^ | 2 NADH | 3--5 ATP |
Pyruvaye oxidation | 2 NADH | 5 ATP |
Citric acid cycle | 2 ATP ||
^^ | 6 NADH | 15 ATP |
^^ | 2 FADH2 | 3 ATP |
**30--32** ATP |||
[Net ATP yields per hexose]
Net ATP yields per hexose
Stage Direct Products ATP Yields
Glycolysis
2 NADH 3–5 ATP
Pyruvaye oxidation 2 NADH 5 ATP
Citric acid cycle
6 NADH 15 ATP
2 FADH2 3 ATP
|--|--|--|--|--|--|--|--|
|♜|  |♝|♛|♚|♝|♞|♜|
|  |♟|♟|♟|  |♟|♟|♟|
|♟|  |♞|  |  |  |  | |
|  |♗|  |  |♟|  |  | |
|  |  |  |  |♙|  |  | |
|  |  |  |  |  |♘|  | |
|♙|♙|♙|♙|  |♙|♙|♙|
|♖|♘|♗|♕|♔|  |  |♖|

# Sequence Diagrams

```mermaid
sequenceDiagram
  Alice ->> Bob: Hello Bob, how are you?
  Bob-->>John: How about you John?
  Bob--x Alice: I am good thanks!
  Bob-x John: I am good thanks!
  Note right of John: Bob thinks a long
long time, so long
that the text does
not fit on a row. Bob-->Alice: Checking with John... Alice->John: Yes... John, how are you? ```
sequenceDiagram Alice ->> Bob: Hello Bob, how are you? Bob-->>John: How about you John? Bob--x Alice: I am good thanks! Bob-x John: I am good thanks! Note right of John: Bob thinks a long
long time, so long
that the text does
not fit on a row. Bob-->Alice: Checking with John... Alice->John: Yes... John, how are you?

# Flows

```mermaid
graph TD
  A[Start] --> B{Is it?}
  B -->|Yes| C[OK]
  C --> D[Rethink]
  D --> B
  B -->|No| E[End]
```
graph TD A[Start] --> B{Is it?} B -->|Yes| C[OK] C --> D[Rethink] D --> B B -->|No| E[End]

# Charts

```js
{
  "type": "pie",
  "data": {
    "labels": [
      "Red",
      "Blue",
      "Yellow"
    ],
    "datasets": [
      {
        "data": [
          300,
          50,
          100
        ],
        "backgroundColor": [
          "#FF6384",
          "#36A2EB",
          "#FFCE56"
        ],
        "hoverBackgroundColor": [
          "#FF6384",
          "#36A2EB",
          "#FFCE56"
        ]
      }
    ]
  }
}
```
{
  "type": "pie",
  "data": {
    "labels": [
      "Red",
      "Blue",
      "Yellow"
    ],
    "datasets": [
      {
        "data": [
          300,
          50,
          100
        ],
        "backgroundColor": [
          "#FF6384",
          "#36A2EB",
          "#FFCE56"
        ],
        "hoverBackgroundColor": [
          "#FF6384",
          "#36A2EB",
          "#FFCE56"
        ]
      }
    ]
  }
}

# Syntax Highlighting

```json
{
  "@context": "https://www.w3.org/ns/did/v1",
  "id": "did:example:123456789abcdefghi",
  "authentication": [{
    "id": "did:example:123456789abcdefghi#keys-1",
    "type": "RsaVerificationKey2018",
    "controller": "did:example:123456789abcdefghi",
    "publicKeyPem": "-----BEGIN PUBLIC KEY...END PUBLIC KEY-----\r\n"
  }],
  "service": [{
    "id":"did:example:123456789abcdefghi#vcs",
    "type": "VerifiableCredentialService",
    "serviceEndpoint": "https://example.com/vc/"
  }]
}
```
{
  "@context": "https://www.w3.org/ns/did/v1",
  "id": "did:example:123456789abcdefghi",
  "authentication": [{ 
    "id": "did:example:123456789abcdefghi#keys-1",
    "type": "RsaVerificationKey2018",
    "controller": "did:example:123456789abcdefghi",
    "publicKeyPem": "-----BEGIN PUBLIC KEY...END PUBLIC KEY-----\r\n"
  }],
  "service": [{
    "id":"did:example:123456789abcdefghi#vcs",
    "type": "VerifiableCredentialService",
    "serviceEndpoint": "https://example.com/vc/"
  }]
}

# TeX Math Equations

When the katex option is enabled, the KaTeX math engine is used for TeX rendering. You can find a list of supported features and examples here: https://katex.org/docs/supported.html.

$$\begin{pmatrix}x_2 \ y_2 \end{pmatrix} = \begin{pmatrix} A & B \ C & D \end{pmatrix}\cdot \begin{pmatrix} x_1 \ y_1 \end{pmatrix}$$

$$\def\arraystretch{1.5} \begin{array}{c:c:c} a & b & c \ \hline d & e & f \ \hdashline g & h & i \end{array}$$

$$ \underbrace{a+b+c}_{\text{Note: such math, much wow.}} $$

# Tab Panels

{
  "foo": "foo",
  "baz": 1
}
{
  "foo": "bar",
  "baz": 2
}

Spec-Up automatically upgrades the links of certain sites, like GitHub. GitHub is the only supported site with Fancy Links right now, but we’ll be adding more as we go.

# GitHub

# Outro

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?

Table of Contents
["
AAL:
\n

See: authenticator assurance level.

\n
ABAC:
\n

See: attribute-based access control.

\n
access control:
\n

The process of granting or denying specific requests for obtaining and using information and related information processing services.

\n
ACDC
\n

See: Authentic Chained Data Container.

\n
action
\n

Something that is actually done (a ‘unit of work’ that is executed) by a single actor (on behalf of a given party), as a single operation, in a specific context.Source: eSSIF-Lab.

\n
actor
\n

An entity that can act (do things/execute actions), e.g. people, machines, but not organizations. A digital agent can serve as an actor acting on behalf of its principal.Source: eSSIF-Lab.

\n
address
\n

See: network address.

\n
administering authority:
\n

See: administering body.

\n
administering body:
\n

A legal entity delegated by a governing body to administer the operation of a governance framework and governed infrastructure for a digital trust ecosystem, such as one or more trust registries.

\n
agency:
\n

In the context of decentralized digital trust infrastructure, the empowering of a party to act independently of its own accord, and in particular to empower the party to employ an agent to act on the party’s behalf.

\n
agent:
\n

An actor that is executing an action on behalf of a party (called the principal of that actor). In the context of decentralized digital trust infrastructure, the term “agent” is most frequently used to mean a digital agent.

\n
AID:
\n

See autonomic identifier.

\n
anonymous
\n

An adjective describing when the identity of a natural person or other actor is unknown.

\n
anycast:
\n

Anycast is a network addressing and routing methodology in which a single IP-address is shared by devices (generally servers) in multiple locations. Routers direct packets addressed to this destination to the location nearest the sender, using their normal decision-making algorithms, typically the lowest number of BGP network hops. Anycast routing is widely used by content delivery networks such as web and name servers, to bring their content closer to end users.

\n
anycast address:
\n

A network address (especially an IP address) used for anycast routing of network transmissions.

\n
appraisability (of a communications endpoint):
\n

The ability for a communication endpoint identified with a verifiable identifier to be appraised for the set of its properties that enable a relying party or a verifier to make a trust decision about communicating with that endpoint.

\n
assurance level
\n

A level of confidence that may be relied on by others. Different types of assurance levels are defined for different types of trust assurance mechanisms. Examples include authenticator assurance level, federation assurance level, and identity assurance level.

\n
appropriate friction:
\n

A user-experience design principle for information systems (such as digital wallets) specifying that the level of attention required of the holder for a particular transaction should provide a reasonable opportunity for an informed choice by the holder.

\n
attestation:
\n

The issue of a statement, based on a decision, that fulfillment of specified requirements has been demonstrated. In the context of decentralized digital trust infrastructure, an attestation usually has a digital signature so that it is cryptographically verifiable.

\n
attribute:
\n

An identifiable set of data that describes an entity, which is the subject of the attribute.

\n
attribute-based access control:
\n

An access control approach in which access is mediated based on attributes associated with subjects (requesters) and the objects to be accessed. Each object and subject has a set of associated attributes, such as location, time of creation, access rights, etc. Access to an object is authorized or denied depending upon whether the required (e.g., policy-defined) correlation can be made between the attributes of that object and of the requesting subject.

\n
audit (of system controls):
\n

Independent review and examination of records and activities to assess the adequacy of system controls, to ensure compliance with established policies and operational procedures.

\n
audit log:
\n

An audit log is a security-relevant chronological record, set of records, and/or destination and source of records that provide documentary evidence of the sequence of activities that have affected at any time a specific operation, procedure, event, or device.

\n
auditor (of an entity):
\n

The party responsible for performing an audit. Typically an auditor must be accredited.

\n
authentication(of a user; process; or device):
\n

Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in an information system.

\n
authentication(of a user; process; or device):
\n

Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in an information system.

\n
authenticator
\n

Something the claimant possesses and controls (typically a cryptographic module or password) that is used to authenticate the claimant’s identity.

\n
authenticator assurance level
\n

A measure of the strength of an authentication mechanism and, therefore, the confidence in it.

\n
authenticator assurance level
\n

A measure of the strength of an authentication mechanism and, therefore, the confidence in it.

\n
Authentic Chained Data Container:
\n

A digital data structure designed for both cryptographic verification and chaining of data containers. ACDC may be used for digital credentials.

\n
authenticity:
\n

The property of being genuine and being able to be verified and trusted; confidence in the validity of a transmission, a message, or message originator.

\n
authorization
\n

The process of verifying that a requested action or service is approved for a specific entity.

\n
authorized organizational representative
\n

A person who has the authority to make claims, sign documents or otherwise commit resources on behalf of an organization.

\n
authorization graph:
\n

A graph of the authorization relationships between different entities in a trust-community. In a digital trust ecosystem, the governing body is typically the trust root of an authorization graph. In some cases, an authorization graph can be traversed by making queries to one or more trust registries.

\n
authoritative source:
\n

A source of information that a relying party considers to be authoritative for that information. In ToIP architecture, the trust registry authorized by the governance framework (#governance-framework) for a [trust community is typically considered an authoritative source by the members of that trust community. A system of record is an authoritative source for the data records it holds. A trust root is an authoritative source for the beginning of a trust chain.

\n
authority:
\n

A party of which certain decisions, ideas, rules etc. are followed by other parties.

\n
autonomic identifier:
\n

The specific type of self-certifying identifier specified by the KERI specifications.

\n
biometric:
\n

A measurable physical characteristic or personal behavioral trait used to recognize the AID, or verify the claimed identity, of an applicant. Facial images, fingerprints, and iris scan samples are all examples of biometrics.

\n
blockchain:
\n

A distributed digital ledger of cryptographically-signed transactions that are grouped into blocks. Each block is cryptographically linked to the previous one (making it tamper evident) after validation and undergoing a consensus decision. As new blocks are added, older blocks become more difficult to modify (creating tamper resistance). New blocks are replicated across copies of the ledger within the network, and any conflicts are resolved automatically using established rules.

\n
broadcast:
\n

In computer networking, telecommunication and information theory, broadcasting is a method of transferring a message to all recipients simultaneously. Broadcast delivers a message to all nodes in the network using a one-to-all association; a single datagram (or packet) from one sender is routed to all of the possibly multiple endpoints associated with the broadcast address. The network automatically replicates datagrams as needed to reach all the recipients within the scope of the broadcast, which is generally an entire network subnet.

\n
broadcast address:
\n

A broadcast address is a network address used to transmit to all devices connected to a multiple-access communications network. A message sent to a broadcast address may be received by all network-attached hosts. In contrast, a multicast address is used to address a specific group of devices, and a unicast address is used to address a single device. For network layer communications, a broadcast address may be a specific IP address.

\n
C2PA:
\n

See: Coalition for Content Provenance and Authenticity.

\n
CA:
\n

See: certificate authority.

\n
CAI:
\n

See: Content Authenticity Initiative.

\n
certification authority:
\n

See: certificate authority.

\n
certificate authority:
\n

The entity in a public key infrastructure (PKI) that is responsible for issuing public key certificates and exacting compliance to a PKI policy.

\n
certification (of a party):
\n

A comprehensive assessment of the management, operational, and technical security controls in an information system, made in support of security accreditation, to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the security requirements for the system.

\n
certification body:
\n

A legal entity that performs certification.

\n
chain of trust:
\n

See: trust chain.

\n
chained credentials:
\n

Two or more credentials linked together to create a trust chain between the credentials that is cryptographically verifiable.

\n
chaining:
\n

See: trust chain.

\n
channel:
\n

See: communication channel.

\n
ciphertext:
\n

Encrypted (enciphered) data. The confidential form of the plaintext that is the output of the encryption function.

\n
claim:
\n

An assertion about a subject, typically expressed as an attribute or property of the subject. It is called a “claim” because the assertion is always made by some party, called the issuer of the claim, and the validity of the claim must be judged by the verifier.

\n
Coalition for Content Provenance and Authenticity:
\n

C2PA is a Joint Development Foundation project of the Linux Foundation that addresses the prevalence of misleading information online through the development of technical standards for certifying the source and history (or provenance) of media content.

\n
communication:
\n

The transmission of information.

\n
communication endpoint:
\n

A type of communication network node. It is an interface exposed by a communicating party or by a communication channel. An example of the latter type of a communication endpoint is a publish-subscribe topic or a group in group communication systems.

\n
communication channel:
\n

A communication channel refers either to a physical transmission medium such as a wire, or to a logical connection over a multiplexed medium such as a radio channel in telecommunications and computer networking. A channel is used for information transfer of, for example, a digital bit stream, from one or several senders to one or several receivers.

\n
communication metadata:
\n

Metadata that describes the sender, receiver, routing, handling, or contents of a communication. Communication metadata is often observable even if the contents of the communication are encrypted.

\n
communication session:
\n

A finite period for which a communication channel is instantiated and maintained, during which certain properties of that channel, such as authentication of the participants, are in effect. A session has a beginning, called the session initiation, and an ending, called the session termination.

\n
complex password:
\n

A password that meets certain security requirements, such as minimum length, inclusion of different character types, non-repetition of characters, and so on.

\n
compliance:
\n

In the context of decentralized digital trust infrastructure, the extent to which a system, actor, or party conforms to the requirements of a governance framework or trust framework that pertains to that particular entity.

\n
concept:
\n

An abstract idea that enables the classification of entities, i.e., a mental construct that enables an instance of a class of entities to be distinguished from entities that are not an instance of that class. A concept can be identified with a term.

\n
confidential computing:
\n

Hardware-enabled features that isolate and process encrypted data in memory so that the data is at less risk of exposure and compromise from concurrent workloads or the underlying system and platform.

\n
confidentiality:
\n

In a communications context, a type of privacy protection in which messages use encryption or other privacy-preserving technologies so that only authorized parties have access.

\n
connection:
\n

A communication channel established between two communication endpoints. A connection may be ephemeral or persistent.

\n
Content Authenticity Initiative:
\n

The Content Authenticity Initiative (CAI) is an association founded in November 2019 by Adobe, the New York Times and Twitter. The CAI promotes an industry standard for provenance metadata defined by the C2PA. The CAI cites curbing disinformation as one motivation for its activities.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
consent management:
\n

A system, process or set of policies under which a person agrees to share personal data for specific usages. A consent management system will typically create a record of such consent.

\n
controlled document:
\n

A governance document whose authority is derived from a primary document.

\n
correlation privacy:
\n

In a communications context, a type of privacy protection in which messages use encryption, hashes, or other privacy-preserving technologies to avoid the use of identifiers or other content that unauthorized parties may use to correlate the sender and/or receiver(s).

\n
counterparty:
\n

From the perspective of one party, the other party in a transaction, such as a financial transaction.

\n
credential:
\n

A container of claims describing one or more subjects. A credential is generated by the issuer of the credential and given to the holder of the credential. A credential typically includes a signature or some other means of proving its authenticity. A credential may be either a physical credential or a digital credential.

\n
credential family:
\n

A set of related digital credentials defined by a governing body (typically in a governance framework) to empower transitive trust decisions among the participants in a digital trust ecosystem.

\n
credential governance framework:
\n

A governance framework for a credential family. A credential governance framework may be included within or referenced by an ecosystem governance framework.

\n
credential offer:
\n

A protocol request invoked by an issuer to offer to issue a digital credential to the  holder of a digital wallet. If the request is invoked by the holder, it is called an issuance request.

\n
credential request:
\n

See: issuance request.

\n
credential schema:
\n

A data schema describing the structure of a digital credential. The W3C Verifiable Credentials Data Model Specification defines a set of requirements for credential schemas.

\n
criterion:
\n

In the context of terminology, a written description of a concept that anyone can evaluate to determine whether or not an entity is an instance or example of that concept. Evaluation leads to a yes/no result.

\n
cryptographic binding:
\n

Associating two or more related elements of information using cryptographic techniques.

\n
cryptographic key:
\n

A key in cryptography is a piece of information, usually a string of numbers or letters that are stored in a file, which, when processed through a cryptographic algorithm, can encode or decode cryptographic data. Symmetric cryptography refers to the practice of the same key being used for both encryption and decryption. Asymmetric cryptography has separate keys for encrypting and decrypting. These keys are known as the public keys and private keys, respectively.

\n
cryptographic trust:
\n

A specialized type of technical trust that is achieved using cryptographic algorithms.

\n
cryptographic verifiability:
\n

The property of being cryptographically verifiable.

\n
cryptographically verifiable:
\n

A property of a data structure that has been digitally signed using a private key such that the digital signature can be verified using the public key. Verifiable data, verifiable messages, verifiable credentials, and verifiable data registries are all cryptographically verifiable. Cryptographic verifiability is a primary goal of the ToIP Technology Stack.

\n
cryptographically bound:
\n

A state in which two or more elements of information have a cryptographic binding.

\n
custodial wallet:
\n

A digital wallet that is directly in the custody of a principal, i.e., under the principal’s direct personal or organizational control. A digital wallet that is in the custody of a third party is called a non-custodial wallet.

\n
custodian:
\n

A third party that has been assigned rights and duties in a custodianship arrangement for the purpose of hosting and safeguarding a principal’s private keys, digital wallet and digital assets on the principal’s behalf. Depending on the custodianship arrangement, the custodian may act as an exchange and provide additional services, such as staking, lending, account recovery, or security features.

\n
custodianship arrangement:
\n

The informal terms or formal legal agreement under which a custodian agrees to provide service to a principal.

\n
dark pattern:
\n

A design pattern, mainly in user interfaces, that has the effect of deceiving individuals into making choices that are advantageous to the designer.

\n
data:
\n

In the pursuit of knowledge, data is a collection of discrete values that convey information, describing quantity, quality, fact, statistics, other basic units of meaning, or simply sequences of symbols that may be further interpreted. A datum is an individual value in a collection of data.

\n
datagram:
\n

See: data packet.

\n
data packet:
\n

In telecommunications and computer networking, a network packet is a formatted unit of data carried by a packet-switched network such as the Internet. A packet consists of control information and user data; the latter is also known as the payload. Control information provides data for delivering the payload (e.g., source and destination network addresses, error detection codes, or sequencing information). Typically, control information is found in packet headers and trailers.

\n
data schema:
\n

A description of the structure of a digital document or object, typically expressed in a machine-readable language in terms of constraints on the structure and content of documents or objects of that type. A credential schema is a particular type of data schema.

\n
data subject:
\n

The natural person that is described by personal data. Data subject is the term used by the EU General Data Protection Regulation.

\n
data vault:
\n

See: digital vault.

\n
decentralized identifier:
\n

A globally unique persistent identifier that does not require a centralized registration authority and is often generated and/or registered cryptographically. The generic format of a DID is defined in section 3.1 DID Syntax of the W3C Decentralized Identifiers (DIDs) 1.0 specification. A specific DID scheme is defined in a DID method specification.

\n
decentralized identifier:
\n

A globally unique persistent identifier that does not require a centralized registration authority and is often generated and/or registered cryptographically. The generic format of a DID is defined in section 3.1 DID Syntax of the W3C Decentralized Identifiers (DIDs) 1.0 specification. A specific DID scheme is defined in a DID method specification.

\n
decentralized identifier:
\n

A globally unique persistent identifier that does not require a centralized registration authority and is often generated and/or registered cryptographically. The generic format of a DID is defined in section 3.1 DID Syntax of the W3C Decentralized Identifiers (DIDs) 1.0 specification. A specific DID scheme is defined in a DID method specification.

\n
decentralized identifier:
\n

A globally unique persistent identifier that does not require a centralized registration authority and is often generated and/or registered cryptographically. The generic format of a DID is defined in section 3.1 DID Syntax of the W3C Decentralized Identifiers (DIDs) 1.0 specification. A specific DID scheme is defined in a DID method specification.

\n
decentralized identity:
\n

A digital identity architecture in which a digital identity is established via the control of a set of cryptographic keys in a digital wallet so that the controller is not dependent on any external identity provider or other third party.

\n
Decentralized Identity Foundation:
\n

A non-profit project of the Linux Foundation chartered to develop the foundational components of an open, standards-based, decentralized identity ecosystem for people, organizations, apps, and devices.

\n
Decentralized Web Node:
\n

A decentralized personal and application data storage and message relay node, as defined in the DIF Decentralized Web Node specification. Users may have multiple nodes that replicate their data between them.

\n
deceptive pattern:
\n

See: dark pattern.

\n
decryption:
\n

The process of changing ciphertext into plaintext using a cryptographic algorithm and key. The opposite of encryption.

\n
deep link:
\n

In the context of the World Wide Web, deep linking is the use of a hyperlink that links to a specific, generally searchable or indexed, piece of web content on a website (e.g. “https://example.com/path/page”), rather than the website’s home page (e.g., “https://example.com”). The URL contains all the information needed to point to a particular item. Deep linking is different from mobile deep linking, which refers to directly linking to in-app content using a non-HTTP URI.

\n
definition:
\n

A textual statement defining the meaning of a term by specifying criterion that enable the concept identified by the term to be distinguished from all other concepts within the intended scope.

\n
delegation:
\n

TODO

\n
delegation credential:
\n

TODO

\n
dependent:
\n

An entity for the caring for and/or protecting/guarding/defending of which a guardianship arrangement has been established with a guardian.

\n
device controller:
\n

The controller of a device capable of digital communications, e.g., a smartphone, tablet, laptop, IoT device, etc.

\n
dictionary:
\n

A dictionary is a listing of lexemes (words or terms) from the lexicon of one or more specific languages, often arranged alphabetically, which may include information on definitions, usage, etymologies, pronunciations, translation, etc. It is a lexicographical reference that shows inter-relationships among the data. Unlike a glossary, a dictionary may provide multiple definitions of a term depending on its scope or context.

\n
DID controller:
\n

An entity that has the capability to make changes to a DID document. A DID might have more than one DID controller. The DID controller(s) can be denoted by the optional controller property at the top level of the DID document. Note that a DID controller might be the DID subject.

\n
DID document:
\n

A set of data describing the DID subject, including mechanisms, such as cryptographic public keys, that the DID subject or a DID delegate can use to authenticate itself and prove its association with the DID. A DID document might have one or more different representations as defined in section 6 of the W3C Decentralized Identifiers (DIDs) 1.0 specification.

\n
DID method:
\n

A definition of how a specific DID method scheme is implemented. A DID method is defined by a DID method specification, which specifies the precise operations by which DIDs and DID documents are created, resolved, updated, and deactivated.

\n
DID subject:
\n

The entity identified by a DID and described by a DID document. Anything can be a DID subject: person, group, organization, physical thing, digital thing, logical thing, etc.

\n
DID URL:
\n

A DID plus any additional syntactic component that conforms to the definition in section 3.2 of the W3C Decentralized Identifiers (DIDs) 1.0 specification. This includes an optional DID path (with its leading / character), optional DID query (with its leading ? character), and optional DID fragment (with its leading # character).

\n
digital agent:
\n

In the context of ​​decentralized digital trust infrastructure, an agent (specifically a type of software agent) that operates in conjunction with a digital wallet.

\n
digital asset:
\n

A digital asset is anything that exists only in digital form and comes with a distinct usage right. Data that do not possess that right are not considered assets.

\n
digital certificate:
\n

See: public key certificate.

\n
digital credential:
\n

A credential in digital form that is signed with a digital signature and held in a digital wallet. A digital credential is issued to a holder by an issuer; a proof of the credential is presented by the holder to a verifier.

\n
digital ecosystem:
\n

A digital ecosystem is a distributed, adaptive, open socio-technical system with properties of self-organization, scalability and sustainability inspired from natural ecosystems. Digital ecosystem models are informed by knowledge of natural ecosystems, especially for aspects related to competition and collaboration among diverse entities.

\n
digital identity:
\n

An identity expressed in a digital form for the purpose representing the identified entity within a computer system or digital network.

\n
digital rights management:
\n

Digital rights management (DRM) is the management of legal access to digital content. Various tools or technological protection measures (TPM) like access control technologies, can restrict the use of proprietary hardware and copyrighted works. DRM technologies govern the use, modification and distribution of copyrighted works (e.g. software, multimedia content) and of systems that enforce these policies within devices.

\n
digital trust ecosystem:
\n

A digital ecosystem in which the participants are one or more interoperating trust communities. Governance of the various roles of governed parties within a digital trust ecosystem (e.g., issuers, holders, verifiers, certification bodies, auditors) is typically managed by a governing body using a governance framework as recommended in the ToIP Governance Stack. Many digital trust ecosystems will also maintain one or more trust lists and/or trust registries.

\n
digital trust utility:
\n

An information system, network, distributed database, or blockchain designed to provide one or more supporting services to higher level components of decentralized digital trust infrastructure. In the ToIP stack, digital trust utilities are at Layer 1. A verifiable data registry is one type of digital trust utility.

\n
digital signature:
\n

A digital signature is a mathematical scheme for verifying the authenticity of digital messages or documents. A valid digital signature, where the prerequisites are satisfied, gives a recipient very high confidence that the message was created by a known sender (authenticity), and that the message was not altered in transit (integrity).

\n
digital vault:
\n

A secure container for data whose controller is the principal. A digital vault is most commonly used in conjunction with a digital wallet and a digital agent. A digital vault may be implemented on a local device or in the cloud; multiple digital vaults may be used by the same principal across different devices and/or the cloud; if so they may use some type of synchronization. If the capability is supported, data may flow into or out of the digital vault automatically based on subscriptions approved by the controller.

\n
digital wallet:
\n

A user agent, optionally including a hardware component, capable of securely storing and processing cryptographic keys, digital credentials, digital assets and other sensitive private data that enables the controller to perform cryptographically verifiable operations. A non-custodial wallet is directly in the custody of a principal. A custodial wallet is in the custody of a third party. Personal wallets are held by individual persons; enterprise wallets are held by organizations or other legal entities.

\n
distributed ledger:
\n

A distributed ledger (also called a shared ledger or distributed ledger technology or DLT) is the consensus of replicated, shared, and synchronized digital data that is geographically spread (distributed) across many sites, countries, or institutions. In contrast to a centralized database, a distributed ledger does not require a central administrator, and consequently does not have a single (central) point-of-failure. In general, a distributed ledger requires a peer-to-peer (P2P) computer network and consensus algorithms so that the ledger is reliably replicated across distributed computer nodes (servers, clients, etc.). The most common form of distributed ledger technology is the blockchain, which can either be on a public or private network.

\n
domain:
\n

See: security domain.

\n
DRM:
\n

See: digital rights management.

\n
DWN:
\n

See: Decentralized Web Node.

\n
ecosystem:
\n

See: digital ecosystem.

\n
ecosystem governance framework:
\n

A governance framework for a digital trust ecosystem. An ecosystem governance framework may incorporate, aggregate, or reference other types of governance frameworks such as a credential governance framework or a utility governance framework.

\n
ecosystem governance framework:
\n

A governance framework for a digital trust ecosystem. An ecosystem governance framework may incorporate, aggregate, or reference other types of governance frameworks such as a credential governance framework or a utility governance framework.

\n
eIDAS:
\n

eIDAS (electronic IDentification, Authentication and trust Services) is an EU regulation with the stated purpose of governing “electronic identification and trust services for electronic transactions”. It passed in 2014 and its provisions came into effect between 2016-2018.

\n
encrypted data vault:
\n

See: digital vault.

\n
encryption:
\n

Cryptographic transformation of data (called plaintext) into a form (called ciphertext) that conceals the data’s original meaning to prevent it from being known or used. If the transformation is reversible, the corresponding reversal process is called decryption, which is a transformation that restores encrypted data to its original state.

\n
end-to-end encryption:
\n

Encryption that is applied to a communication before it is transmitted from the sender’s communication endpoint and cannot be decrypted until after it is received at the receiver’s communication endpoint. When end-to-end encryption is used, the communication cannot be decrypted in transit no matter how many intermediaries are involved in the routing process.

\n
End-to-End Principle:
\n

The end-to-end principle is a design framework in computer networking. In networks designed according to this principle, guaranteeing certain application-specific features, such as reliability and security, requires that they reside in the communicating end nodes of the network. Intermediary nodes, such as gateways and routers, that exist to establish the network, may implement these to improve efficiency but cannot guarantee end-to-end correctness.

\n
endpoint:
\n

See: communication endpoint.

\n
endpoint system:
\n

The system that operates a communications endpoint. In the context of the ToIP stack, an endpoint system is one of three types of systems defined in the ToIP Technology Architecture Specification.

\n
enterprise data vault:
\n

A digital vault whose controller is an organization.

\n
enterprise wallet:
\n

A digital wallet whose holder is an organization.

\n
entity:
\n

Someone or something that is known to exist.

\n
entity:
\n

Someone or something that is known to exist.

\n
ephemeral connection:
\n

A connection that only exists for the duration of a single communication session or transaction.

\n
expression language:
\n

A language for creating a computer-interpretable (machine-readable) representation of specific knowledge.

\n
FAL:
\n

See: federation assurance level.

\n
federated identity:
\n

A digital identity architecture in which a digital identity established on one computer system, network, or trust domain is linked to other computer systems, networks, or trust domains for the purpose of identifying the same entity across those domains.

\n
federation:
\n

A group of organizations that collaborate to establish a common trust framework or governance framework for the exchange of identity data in a federated identity system.

\n
federation assurance level:
\n

A category that describes the federation protocol used to communicate an assertion containing authentication) and attribute information (if applicable) to a relying party, as defined in NIST SP 800-63-3 in terms of three levels: FAL 1 (Some confidence), FAL 2 (High confidence), FAL 3 (Very high confidence).

\n
fiduciary:
\n

A fiduciary is a person who holds a legal or ethical relationship of trust with one or more other parties (person or group of persons). Typically, a fiduciary prudently takes care of money or other assets for another person. One party, for example, a corporate trust company or the trust department of a bank, acts in a fiduciary capacity to another party, who, for example, has entrusted funds to the fiduciary for safekeeping or investment. In a fiduciary relationship, one person, in a position of vulnerability, justifiably vests confidence, good faith, reliance, and trust in another whose aid, advice, or protection is sought in some matter.

\n
first party:
\n

The party who initiates a trust relationship, connection, or transaction with a second party.

\n
foundational identity:
\n

A set of identity data, such as a credential, issued by an authoritative source for the legal identity of the subject. Birth certificates, passports, driving licenses, and other forms of government ID documents are considered foundational identity documents. Foundational identities are often used to provide identity binding for functional identities.

\n
fourth party:
\n

A party that is not directly involved in the trust relationship between a first party and a second party, but provides supporting services exclusively to the first party (in contrast with a third party, who in most cases provides supporting services to the second party). In its strongest form, a fourth party has a fiduciary relationship with the first party.

\n
functional identity:
\n

A set of identity data, such as a credential, that is issued not for the purpose of establishing a foundational identity for the subject, but for the purpose of establishing other attributes, qualifications, or capabilities of the subject. Loyalty cards, library cards, and employee IDs are all examples of functional identities. Foundational identities are often used to provide identity binding for functional identities.

\n
gateway:
\n

A gateway is a piece of networking hardware or software used in telecommunications networks that allows data to flow from one discrete network to another. Gateways are distinct from routers or switches in that they communicate using more than one protocol to connect multiple networks[1][2] and can operate at any of the seven layers of the open systems interconnection model (OSI).

\n
GDPR:
\n

See: General Data Protection Regulation.

\n
General Data Protection Regulation:
\n

The General Data Protection Regulation (Regulation (EU) 2016/679, abbreviated GDPR) is a European Union regulation on information privacy in the European Union (EU) and the European Economic Area (EEA). The GDPR is an important component of EU privacy law and human rights law, in particular Article 8(1) of the Charter of Fundamental Rights of the European Union. It also governs the transfer of personal data outside the EU and EEA. The GDPR’s goals are to enhance individuals’ control and rights over their personal information and to simplify the regulations for international business.

\n
glossary:
\n

A glossary (from Ancient Greek: γλῶσσα, glossa; language, speech, wording), also known as a vocabulary or clavis, is an alphabetical list of terms in a particular domain of knowledge (scope) together with the definitions for those terms. Unlike a dictionary, a glossary has only one definition for each term.

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
governance diamond:
\n

A term that refers to the addition of a governing body to the standard trust triangle of issuers, holders, and verifiers of credentials. The resulting combination of four parties represents the basic structure of a digital trust ecosystem.

\n
governance document:
\n

A document with at least one identifier that specifies governance requirements for a trust community.

\n
governance framework:
\n

A collection of one or more governance documents published by the governing body of a trust community.

\n
governance graph:
\n

A graph of the governance relationships between entities with a trust community. A governance graph shows which nodes are the governing bodies and which are the governed parties. In some cases, a governance graph can be traversed by making queries to one or more trust registries.Note: a party can play both roles and also be a participant in multiple governance frameworks.

\n
governance requirement:
\n

A requirement such as a policy, rule, or technical specification specified in a governance document.

\n
governed use case:
\n

A use case specified in a governance document that results in specific governance requirements within that governance framework. Governed use cases may optionally be discovered via a trust registry authorized by the relevant governance framework.

\n
governed party:
\n

A party whose role(s) in a trust community is governed by the governance requirements in a governance framework.

\n
governed party:
\n

A party whose role(s) in a trust community is governed by the governance requirements in a governance framework.

\n
governed information:
\n

Any information published under the authority of a governing body for the purpose of governing a trust community. This includes its governance framework and any information available via an authorized trust registry.

\n
governing authority:
\n

See: governing body.

\n
governing body:
\n

The party (or set of parties) authoritative for governing a trust community, usually (but not always) by developing, publishing, maintaining, and enforcing a governance framework. A governing body may be a government, a formal legal entity of any kind, an informal group of any kind, or an individual. A governing body may also delegate operational responsibilities to an administering body.

\n
GRC:
\n

See: Governance.

\n
guardian:
\n

A party that has been assigned rights and duties in a guardianship arrangement for the purpose of caring for, protecting, guarding, and defending the entity that is the dependent in that guardianship arrangement. In the context of decentralized digital trust infrastructure, a guardian is issued guardianship credentials into their own digital wallet in order to perform such actions on behalf of the dependent as are required by this role.

\n
guardianship arrangement:
\n

A guardianship arrangement (in a jurisdiction) is the specification of a set of rights and duties between legal entities of the jurisdiction that enforces these rights and duties, for the purpose of caring for, protecting, guarding, and defending one or more of these entities. At a minimum, the entities participating in a guardianship arrangement are the guardian and the dependent.

\n
guardianship credential:
\n

A digital credential issued by a governing body to a guardian to empower the guardian to undertake the rights and duties of a guardianship arrangement on behalf of a dependent.

\n
hardware security module:
\n

A physical computing device that provides tamper-evident and intrusion-resistant safeguarding and management of digital keys and other secrets, as well as crypto-processing.

\n
hash:
\n

The result of applying a hash function to a message.

\n
hash function:
\n

An algorithm that computes a numerical value (called the hash value) on a data file or electronic message that is used to represent that file or message, and depends on the entire contents of the file or message. A hash function can be considered to be a fingerprint of the file or message. Approved hash functions satisfy the following properties: one-way (it is computationally infeasible to find any input that maps to any pre-specified output); and collision resistant (it is computationally infeasible to find any two distinct inputs that map to the same output).

\n
holder (of a claim or credential):
\n

A role an agent performs by serving as the controller of the cryptographic keys and digital credentials in a digital wallet. The holder makes issuance requests for credentials and responds to presentation requests for credentials. A holder is usually, but not always, a subject of the credentials they are holding.

\n
holder binding:
\n

The process of creating and verifying a relationship between the holder of a digital wallet and the wallet itself. Holder binding is related to but NOT the same as subject binding.

\n
host:
\n

A host is any hardware device that has the capability of permitting access to a network via a user interface, specialized software, network address, protocol stack, or any other means. Some examples include, but are not limited to, computers, personal electronic devices, thin clients, and multi-functional devices.

\n
hourglass model:
\n

An architectural model for layered systems—and specifically for the protocol layers in a protocol stack—in which a diversity of supporting protocols and services at the lower layers are able to support a great diversity of protocols and applications at the higher layers through the use of a single protocol in the spanning layer in the middle—the “neck” of the hourglass.

\n
HSM:
\n

See: hardware security module.

\n
human auditability:
\n

See: human auditable.

\n
human auditable:
\n

A process or procedure whose compliance with the policies in a trust framework or governance framework can only be verified by a human performing an audit. Human auditability is a primary goal of the ToIP Governance Stack.

\n
human experience:
\n

The processes, patterns and rituals of acquiring knowledge or skill from doing, seeing, or feeling things as a natural person. In the context of decentralized digital trust infrastructure, the direct experience of a natural person using trust applications to make trust decisions within one or more digital trust ecosystems.

\n
human-readable:
\n

Information that can be processed by a human but that is not intended to be machine-readable.

\n
human trust:
\n

A level of assurance in a trust relationship that can be achieved only via human evaluation of applicable trust factors.

\n
IAL:
\n

See: identity assurance level.

\n
identification:
\n

The action of a party obtaining the set of identity data necessary to serve as that party’s identity for a specific entity.

\n
identifier:
\n

A single attribute—typically a character string—that uniquely identifies an entity within a specific context (which may be a global context). Examples include the name of a party the URL of an organization, or a serial number for a man-made thing.

\n
identity:
\n

A collection of attributes or other identity data that describe an entity and enable it to be distinguished from all other entities within a specific scope of identification. Identity attributes may include one or more identifiers for an entity, however it is possible to establish an identity without using identifiers.

\n
identity assurance level:
\n

A category that conveys the degree of confidence that a person’s claimed identity is their real identity, for example as defined in NIST SP 800-63-3 in terms of three levels: IAL 1 (Some confidence), IAL 2 (High confidence), IAL 3 (Very high confidence).

\n
identity binding:
\n

The process of associating a set of identity data, such as a credential, with its subject, such as a natural person. The strength of an identity binding is one factor in determining an authenticator assurance level.

\n
identity data:
\n

The set of data held by a party in order to provide an identity for a specific entity.

\n
identity document:
\n

A physical or digital document containing identity data. A credential is a specialized form of identity document. Birth certificates, bank statements, and utility bills can all be considered identity documents.

\n
identity proofing:
\n

The process of a party gathering sufficient identity data to establish an identity for a particular subject at a particular identity assurance level.

\n
identity provider:
\n

An identity provider (abbreviated IdP or IDP) is a system entity that creates, maintains, and manages identity information for principals and also provides authentication services to relying applications within a federation or distributed network.

\n
IDP:
\n

See: identity provider.

\n
impersonation:
\n

In the context of cybersecurity, impersonation is when an attacker pretends to be another person in order to commit fraud or some other digital crime.

\n
integrity (of a data structure):
\n

In IT security, data integrity means maintaining and assuring the accuracy and completeness of data over its entire lifecycle. This means that data cannot be modified in an unauthorized or undetected manner.

\n
intermediary system:
\n

A system that operates at ToIP Layer 2, the trust spanning layer of the ToIP stack, in order to route ToIP messages between endpoint systems. A supporting system is one of three types of systems defined in the ToIP Technology Architecture Specification.

\n
Internet Protocol:
\n

The Internet Protocol (IP) is the network layer communications protocol in the Internet protocol suite (also known as the TCP/IP suite) for relaying datagrams across network boundaries. Its routing function enables internetworking, and essentially establishes the Internet. IP has the task of delivering packets from the source host to the destination host solely based on the IP addresses in the packet headers. For this purpose, IP defines packet structures that encapsulate the data to be delivered. It also defines addressing methods that are used to label the datagram with source and destination information.

\n
Internet protocol suite:
\n

The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the set of communication protocols used in the Internet and similar computer networks according to functional criteria. The foundational protocols in the suite are the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP).

\n
IP:
\n

See: Internet Protocol.

\n
IP address:
\n

An Internet Protocol address (IP address) is a numerical label such as 192.0.2.1 that is connected to a computer network that uses the Internet Protocol for communication. An IP address serves two main functions: network interface identification, and location addressing.

\n
issuance:
\n

The action of an issuer producing and transmitting a digital credential to a holder. A holder may request issuance by submitting an issuance request.

\n
issuance request:
\n

A protocol request invoked by the holder of a digital wallet to obtain a digital credential from an issuer.

\n
issuer (of a claim or credential):
\n

A role an agent performs to package and digitally sign a set of claims, typically in the form of a digital credential, and transmit them to a holder.

\n
jurisdiction:
\n

The composition of: a) a legal system (legislation, enforcement thereof, and conflict resolution), b) a party that governs that legal system, c) a scope within which that legal system is operational, and d) one or more objectives for the purpose of which the legal system is operated.

\n
KATE:
\n

See: keys-at-the-edge.

\n
KERI:
\n

See: Key Event Receipt Infrastructure.

\n
key:
\n

See: cryptographic key.

\n
key establishment:
\n

A process that results in the sharing of a key between two or more entities, either by transporting a key from one entity to another (key transport) or generating a key from information shared by the entities (key agreement).

\n
key event:
\n

An event in the history of the usage of a cryptographic key pair. There are multiple types of key events. The inception event is when the key pair is first generated. A rotation event is when the key pair is changed to a new key pair. In some key management systems (such as KERI), key events are tracked in a key event log.

\n
key event log:
\n

An ordered sequence of records of key events.

\n
Key Event Receipt Infrastructure:
\n

A decentralized permissionless key management architecture.

\n
key management system:
\n

A system for the management of cryptographic keys and their metadata (e.g., generation, distribution, storage, backup, archive, recovery, use, revocation, and destruction). An automated key management system may be used to oversee, automate, and secure the key management process. A key management is often protected by implementing it within the trusted execution environment (TEE) of a device. An example is the Secure Enclave on Apple iOS devices.

\n
keys-at-the-edge:
\n

A key management architecture in which keys are stored on a user’s local edge devices, such as a smartphone, tablet, or laptop, and then used in conjunction with a secure protocol to unlock a key management system (KMS) and/or a digital vault in the cloud. This approach can enable the storage and sharing of large data structures that are not feasible on edge devices. This architecture can also be used in conjunction with confidential computing to enable cloud-based digital agents to safely carry out “user not present” operations.

\n
KMS:
\n

See: key management system.

\n
knowledge:
\n

The (intangible) sum of what is known by a specific party, as well as the familiarity, awareness or understanding of someone or something by that party.

\n
Laws of Identity:
\n

A set of seven “laws” written by Kim Cameron, former Chief Identity Architect of Microsoft (1941-2021), to describe the dynamics that cause digital identity systems to succeed or fail in various contexts. His goal was to define the requirements for a unifying identity metasystem that can offer the Internet the identity layer it needs.

\n
Layer 1:
\n

See: ToIP Layer 1.

\n
Layer 2:
\n

See: ToIP Layer 2.

\n
Layer 3:
\n

See: ToIP Layer 3.

\n
Layer 4:
\n

See: ToIP Layer 4.

\n
legal entity:
\n

An entity that is not a natural person but is recognized as having legal rights and responsibilities. Examples include corporations, partnerships, sole proprietorships, non-profit organizations, associations, and governments. (In some cases even natural systems such as rivers are treated as legal entities.)

\n
Legal Entity Identifier:
\n

The Legal Entity Identifier (LEI) is a unique global identifier for legal entities participating in financial transactions. Also known as an LEI code or LEI number, its purpose is to help identify legal entities on a globally accessible database. Legal entities are organisations such as companies or government entities that participate in financial transactions.

\n
legal identity:
\n

A set of identity data considered authoritative to identify a party for purposes of legal accountability under one or more jurisdictions.

\n
legal person:
\n

In law, a legal person is any person or ‘thing’ that can do the things a human person is usually able to do in law – such as enter into contracts, sue and be sued, own property, and so on.[3][4][5] The reason for the term “legal person” is that some legal persons are not people: companies and corporations are “persons” legally speaking (they can legally do most of the things an ordinary person can do), but they are not people in a literal sense (human beings).

\n
legal system:
\n

A system in which policies and rules are defined, and mechanisms for their enforcement and conflict resolution are (implicitly or explicitly) specified. Legal systems are not just defined by governments; they can also be defined by a governance framework.

\n
LEI:
\n

See: Legal Entity Identifier.

\n
level of assurance:
\n

See: assurance level.

\n
liveness detection:
\n

Any technique used to detect a presentation attack by determining whether the source of a biometric sample is a live human being or a fake representation. This is typically accomplished using algorithms that analyze biometric sensor data to detect whether the source is live or reproduced.

\n
locus of control:
\n

The set of computing systems under a party’s direct control, where messages and data do not cross trust boundaries.

\n
machine-readable:
\n

Information written in a computer language or expression language so that it can be read and processed by a computing device.

\n
man-made thing:
\n

Athing generated by human activity of some kind. Man-made things include both active things, such as cars or drones, and passive things, such as chairs or trousers.

\n
mandatory:
\n

A requirement that must be implemented in order for an implementer to be in compliance. In ToIP governance frameworks, a mandatory requirement is expressed using a MUST or REQUIRED keyword as defined in IETF RFC 2119.

\n
metadata:
\n

Information describing the characteristics of data including, for example, structural metadata describing data structures (e.g., data format, syntax, and semantics) and descriptive metadata describing data contents (e.g., information security labels).

\n
message:
\n

A discrete unit of communication intended by the source for consumption by some recipient or group of recipients.

\n
mobile deep link:
\n

In the context of mobile apps, deep linking consists of using a uniform resource identifier (URI) that links to a specific location within a mobile app rather than simply launching the app. Deferred deep linking allows users to deep link to content even if the app is not already installed. Depending on the mobile device platform, the URI required to trigger the app may be different.

\n
MPC:
\n

See: multi-party computation.

\n
multicast:
\n

In computer networking, multicast is group communication where data transmission is addressed (using a multicast address) to a group of destination computers simultaneously. Multicast can be one-to-many or many-to-many distribution. Multicast should not be confused with physical layer point-to-multipoint communication.

\n
multicast address:
\n

A multicast address is a logical identifier for a group of hosts in a computer network that are available to process datagrams or frames intended to be multicast for a designated network service.

\n
multi-party computation:
\n

Secure multi-party computation (also known as secure computation, multi-party computation (MPC) or privacy-preserving computation) is a subfield of cryptography with the goal of creating methods for parties to jointly compute a function over their inputs while keeping those inputs private. Unlike traditional cryptographic tasks, where cryptography assures security and integrity of communication or storage and the adversary is outside the system of participants (an eavesdropper on the sender and receiver), the cryptography in this model protects participants’ privacy from each other.

\n
multi-party control:
\n

A variant of multi-party computation where multiple parties must act in concert to meet a control requirement without revealing each other’s data. All parties are privy to the output of the control, but no party learns anything about the others.

\n
multi-signature:
\n

A cryptographic signature scheme where the process of signing information (e.g., a transaction) is distributed among multiple private keys.

\n
natural person:
\n

A person (in legal meaning, i.e., one who has its own legal personality) that is an individual human being, distinguished from the broader category of a legal person, which may be a private (i.e., business entity or non-governmental organization) or public (i.e., government) organization.

\n
natural thing:
\n

A thing that exists in the natural world independently of humans. Although natural things may form part of a man-made thing, natural things are mutually exclusive with man-made things.

\n
network address:
\n

A network address is an identifier for a node or host on a telecommunications network. Network addresses are designed to be unique identifiers across the network, although some networks allow for local, private addresses, or locally administered addresses that may not be unique. Special network addresses are allocated as broadcast or multicast addresses. A network address designed to address a single device is called a unicast address.

\n
node:
\n

In telecommunications networks, a node (Latin: nodus, ‘knot’) is either a redistribution point or a communication endpoint. The definition of a node depends on the network and protocol layer referred to. A physical network node is an electronic device that is attached to a network, and is capable of creating, receiving, or transmitting information over a communication channel.

\n
non-custodial wallet:
\n

A digital wallet that is directly in the control of the holder, usually because the holder is the device controller of the device hosting the digital wallet (smartcard, smartphone, tablet, laptop, desktop, car, etc.) A digital wallet that is in the custody of a third party is called a custodial wallet.

\n
objective:
\n

Something toward which a party (its owner) directs effort (an aim, goal, or end of action).

\n
OOBI:
\n

See: out-of-band introduction.

\n
OpenWallet Foundation:
\n

A non-profit project of the Linux Foundation chartered to build a world-class open source wallet engine.

\n
operational circumstances:
\n

In the context of privacy protection, this term denotes the context in which privacy trade-off decisions are made. It includes the regulatory environment and other non-technical factors that bear on what reasonable privacy expectations might be.

\n
optional:
\n

A requirement that is not mandatory or recommended to implement in order for an implementer to be in compliance, but which is left to the implementer’s choice. In ToIP governance frameworks, an optional requirement is expressed using a MAY or OPTIONAL keyword as defined in IETF RFC 2119.

\n
organization:
\n

A party that consists of a group of parties who agree to be organized into a specific form in order to better achieve a common set of objectives. Examples include corporations, partnerships, sole proprietorships, non-profit organizations, associations, and governments.

\n
organizational authority:
\n

A type of authority where the party asserting its right is an organization.

\n
out-of-band introduction
\n

A process by which two or more entities exchange VIDs in order to form a cryptographically verifiable connection (e.g., a ToIP connection), such as by scanning a QR code (in person or remotely) or clicking a deep link.

\n
out-of-band introduction
\n

A process by which two or more entities exchange VIDs in order to form a cryptographically verifiable connection (e.g., a ToIP connection), such as by scanning a QR code (in person or remotely) or clicking a deep link.

\n
owner (of an entity):
\n

The role that a party performs when it is exercising its legal, rightful or natural title to control a specific entity.

\n
P2P:
\n

See: peer-to-peer.

\n
party:
\n

An entity that sets its objectives, maintains its knowledge, and uses that knowledge to pursue its objectives in an autonomous (sovereign) manner. Humans and organizations are the typical examples.

\n
password:
\n

A string of characters (letters, numbers and other symbols) that are used to authenticate an identity, verify access authorization or derive cryptographic keys.

\n
peer:
\n

In the context of digital networks, an actor on the network that has the same status, privileges, and communications options as the other actors on the network.

\n
peer-to-peer:
\n

Peer-to-peer (P2P) computing or networking is a distributed application architecture that partitions tasks or workloads between peers. Peers are equally privileged, equipotent participants in the network. This forms a peer-to-peer network of nodes.

\n
permission
\n

Authorization to perform some action on a system.

\n
persistent connection:
\n

A connection that is able to persist across multiple communication sessions. In a ToIP context, a persistent connection is established when two ToIP endpoints exchange verifiable identifiers that they can use to re-establish the connection with each other whenever it is needed.

\n
personal data:
\n

Any information relating to an identified or identifiable natural person (called a data subject under GDPR).

\n
personal data store:
\n

See: personal data vault.

\n
personal data vault:
\n

A digital vault whose controller is a natural person.

\n
personal wallet:
\n

A digital wallet whose holder is a natural person.

\n
personally identifiable information:
\n

Information (any form of data) that can be used to directly or indirectly identify or re-identify an individual person either singly or in combination within a single record or in correlation with other records. This information can be one or more attributes/fields/properties in a record (e.g., date-of-birth) or one or more records (e.g., medical records).

\n
physical credential:
\n

A credential in a physical form such as paper, plastic, or metal.

\n
PII:
\n

See: personally identifiable information.

\n
PKI:
\n

See: public key infrastructure.

\n
plaintext:
\n

Unencrypted information that may be input to an encryption operation. Once encrypted, it becomes ciphertext.

\n
policy
\n

Statements, rules or assertions that specify the correct or expected behavior of an entity.

\n
PoP:
\n

See: proof of personhood.

\n
presentation:
\n

A verifiable message that a holder may send to a verifier containing proofs of one or more claims derived from one or more digital credentials from one or more issuers as a response to a specific presentation request from a  verifier.

\n
presentation attack:
\n

A type of cybersecurity attack in which the attacker attempts to defeat a biometric liveness detection system by providing false inputs.

\n
presentation request:
\n

A protocol request sent by the verifier to the holder of a digital wallet to request a presentation.

\n
primary document:
\n

The governance document at the root of a governance framework. The primary document specifies the other controlled documents in the governance framework.

\n
principal:
\n

The party for whom, or on behalf of whom, an actor is executing an action (this actor is then called an agent of that party).

\n
Principles of SSI:
\n

A set of principles for self-sovereign identity systems originally defined by the Sovrin Foundation and republished by the ToIP Foundation.

\n
privacy policy:
\n

A statement or legal document (in privacy law) that discloses some or all of the ways a party gathers, uses, discloses, and manages a customer or client’s data.

\n
private key:
\n

In public key cryptography, the cryptographic key which must be kept secret by the controller in order to maintain security.

\n
proof:
\n

A digital object that enables cryptographic verification of either: a) the claims from one or more digital credentials, or b) facts about claims that do not reveal the data itself (e.g., proof of the subject being over/under a specific age without revealing a birthdate).

\n
proof of control:
\n

See: proof of possession.

\n
proof of personhood:
\n

Proof of personhood (PoP) is a means of resisting malicious attacks on peer-to-peer networks, particularly, attacks that utilize multiple fake identities, otherwise known as a Sybil attack. Decentralized online platforms are particularly vulnerable to such attacks by their very nature, as notionally democratic and responsive to large voting blocks. In PoP, each unique human participant obtains one equal unit of voting power, and any associated rewards.

\n
proof of possession:
\n

A verification process whereby a level of assurance is obtained that the owner of a key pair actually controls the private key associated with the public key.

\n
proof of presence:
\n

See: liveness detection.

\n
property:
\n

In the context of digital communication, an attribute of a digital object or data structure, such as a DID document or a schema.

\n
protected data:
\n

Data that is not publicly available but requires some type of access control to gain access.

\n
protocol layer:
\n

In modern protocol design, protocols are layered to form a protocol stack. Layering is a design principle that divides the protocol design task into smaller steps, each of which accomplishes a specific part, interacting with the other parts of the protocol only in a small number of well-defined ways. Layering allows the parts of a protocol to be designed and tested without a combinatorial explosion of cases, keeping each design relatively simple.

\n
protocol stack:
\n

The protocol stack or network stack is an implementation of a computer networking protocol suite or protocol family. Some of these terms are used interchangeably but strictly speaking, the suite is the definition of the communication protocols, and the stack is the software implementation of them.

\n
pseudonym:
\n

A pseudonym is a fictitious name that a person assumes for a particular purpose, which differs from their original or true name (orthonym). This also differs from a new name that entirely or legally replaces an individual’s own. Many pseudonym holders use pseudonyms because they wish to remain anonymous, but anonymity is difficult to achieve and often fraught with legal issues.

\n
public key:
\n

Drummond Reed: In public key cryptography, the cryptographic key that can be freely shared with anyone by the controller without compromising security. A party’s public key must be verified as authoritative in order to verify their digital signature.

\n
public key certificate:
\n

A set of data that uniquely identifies a public key (which has a corresponding private key) and an owner that is authorized to use the key pair. The certificate contains the owner’s public key and possibly other information and is digitally signed by a certification authority (i.e., a trusted party), thereby binding the public key to the owner.

\n
public key cryptography:
\n

Public key cryptography, or asymmetric cryptography, is the field of cryptographic systems that use pairs of related keys. Each key pair consists of a public key and a corresponding private key. Key pairs are generated with cryptographic algorithms based on mathematical problems termed one-way functions. Security of public key cryptography depends on keeping the private key secret; the public key can be openly distributed without compromising security.

\n
public key infrastructure:
\n

A set of policies, processes, server platforms, software and workstations used for the purpose of administering certificates and public-private key pairs, including the ability to issue, maintain, and revoke public key certificates. The PKI includes the hierarchy of certificate authorities that allow for the deployment of digital certificates that support encryption, digital signature and authentication to meet business and security requirements.

\n
QR code:
\n

A QR code (short for “quick-response code”) is a type of two-dimensional matrix barcode—a machine-readable optical image that contains information specific to the identified item. In practice, QR codes contain data for a locator, an identifier, and web tracking.

\n
RBAC:
\n

See: role-based access control.

\n
real world identity
\n

A term used to describe the opposite of digital identity, i.e., an identity (typically for a person) in the physical instead of the digital world.

\n
recommended:
\n

A requirement that is not mandatory to implement in order for an implementer to be in compliance, but which should be implemented unless the implementer has a good reason. In ToIP governance frameworks, a recommendation is expressed using a SHOULD or RECOMMENDED keyword as defined in IETF RFC 2119.

\n
record:
\n

A uniquely identifiable entry or listing in a database or registry.

\n
registrant:
\n

The party submitting a registration record to a registry.

\n
registrar:
\n

The party who performs registration on behalf of a registrant.

\n
registration:
\n

The process by which a registrant submits a record to a registry.

\n
registry:
\n

A specialized database of records that serves as an authoritative source of information about entities.

\n
relationship context:
\n

A context established within the boundary of a trust relationship.

\n
relying party:
\n

A party who consumes claims or trust graphs from other parties (such as issuers, holders, and trust registries) in order to make a trust decision.

\n
reputation:
\n

The reputation or prestige of a social entity (a person, a social group, an organization, or a place) is an opinion about that entity – typically developed as a result of social evaluation on a set of criteria, such as behavior or performance.

\n
reputation graph:
\n

A graph of the reputation relationships between different entities in a trust community. In a digital trust ecosystem, the governing body may be one trust root of a reputation graph. In some cases, a reputation graph can be traversed by making queries to one or more trust registries.

\n
reputation system:
\n

Reputation systems are programs or algorithms that allow users to rate each other in online communities in order to build trust through reputation. Some common uses of these systems can be found on e-commerce websites such as eBay, Amazon.com, and Etsy as well as online advice communities such as Stack Exchange.

\n
requirement:
\n

A specified condition or behavior to which a system needs to comply. Technical requirements are defined in technical specifications and implemented in computer systems to be executed by software actors. Governance requirements are defined in governance documents that specify policies and procedures to be executed by human actors. In ToIP architecture, requirements are expressed using the keywords defined in Internet RFC 2119.

\n
requirement:
\n

A specified condition or behavior to which a system needs to comply. Technical requirements are defined in technical specifications and implemented in computer systems to be executed by software actors. Governance requirements are defined in governance documents that specify policies and procedures to be executed by human actors. In ToIP architecture, requirements are expressed using the keywords defined in Internet RFC 2119.

\n
revocation:
\n

In the context of digital credentials, revocation is an event signifying that the issuer no longer attests to the validity of a credential they have issued. In the context of cryptographic keys, revocation is an event signifying that the controller no longer attests to the validity of a public/private key pair for which the controller is authoritative.

\n
risk:
\n

The effects that uncertainty (i.e. a lack of information, understanding or knowledge of events, their consequences or likelihoods) can have on the intended realization of an objectiveof a party.

\n
risk assessment:
\n

The process of identifying risks to organizational operations (including mission, functions, image, reputation), organizational assets, individuals, other organizations, and the overall ecosystem, resulting from the operation of an information system. Risk assessment is part of risk management, incorporates threat and vulnerability analyses, and considers risk mitigations provided by security controls planned or in place.

\n
risk decision:
\n

See: trust decision.

\n
risk management:
\n

The process of managing risks to organizational operations (including mission, functions, image, or reputation), organizational assets, or individuals resulting from the operation of an information system, and includes: (i) the conduct of a risk assessment; (ii) the implementation of a risk mitigation strategy; and (iii) employment of techniques and procedures for the continuous monitoring of the security state of the information system.

\n
risk mitigation:
\n

Prioritizing, evaluating, and implementing the appropriate risk-reducing controls/countermeasures recommended from the risk management process.

\n
role:
\n

A defined set of characteristics that an entity has in some context, such as responsibilities it may have, actions (behaviors) it may execute, or pieces of knowledge that it is expected to have in that context, which are referenced by a specific role name.

\n
role-based access control:
\n

Access control based on user roles (i.e., a collection of access authorizations a user receives based on an explicit or implicit assumption of a given role). Role permissions may be inherited through a role hierarchy and typically reflect the permissions needed to perform defined functions within an organization. A given role may apply to a single individual or to several individuals.

\n
role credential:
\n

A credential claiming that the subject has a specific role.

\n
router:
\n

A router is a networking device that forwards data packets between computer networks. Routers perform the traffic directing functions between networks and on the global Internet. Data sent through a network, such as a web page or email, is in the form of data packets. A packet is typically forwarded from one router to another router through the networks that constitute an internetwork (e.g. the Internet) until it reaches its destination node. This process is called routing.

\n
routing:
\n

Routing is the process of selecting a path for traffic in a network or between or across multiple networks. Broadly, routing is performed in many types of networks, including circuit-switched networks, such as the public switched telephone network (PSTN), and computer networks, such as the Internet. A router is a computing device that specializes in performing routing.

\n
rule:
\n

A prescribed guide for conduct, process or action to achieve a defined result or objective. Rules may be human-readable or machine-readable or both.

\n
RWI:
\n

See: real world identity.

\n
schema:
\n

A framework, pattern, or set of rules for enforcing a specific structure on a digital object or a set of digital data. There are many types of schemas, e.g., data schema, credential verification schema, database schema.

\n
scope:
\n

In the context of terminology, scope refers to the set of possible concepts within which: a) a specific term is intended to uniquely identify a concept, or b) a specific glossary is intended to identify a set of concepts. In the context of identification, scope refers to the set of possible entities within which a specific entity must be uniquely identified. In the context of specifications, scope refers to the set of problems (the problem space) within which the specification is intended to specify solutions.

\n
SCID:
\n

See: self-certifying identifier.

\n
second party:
\n

The party with whom a first party engages to form a trust relationship, establish a connection, or execute a transaction.

\n
Secure Enclave:
\n

A coprocessor on Apple iOS devices that serves as a trusted execution environment.

\n
secure multi-party computation:
\n

See: multi-party computation.

\n
Secure Sockets Layer:
\n

The original transport layer security protocol developed by Netscape and partners. Now deprecated in favor of Transport Layer Security (TLS).

\n
security domain:
\n

An environment or context that includes a set of system resources and a set of system entities that have the right to access the resources as defined by a common security policy, security model, or security architecture.

\n
security policy:
\n

A set of policies and rules that governs all aspects of security-relevant system and system element behavior.

\n
self-asserted:
\n

A term used to describe a claim or a credential whose subject is also the issuer.

\n
self-certified:
\n

When a party provides its own certification that it is compliant with a set of requirements, such as a governance framework.

\n
self-certifying identifier
\n

A subclass of verifiable identifier that is cryptographically verifiable without the need to rely on any third party for verification because the identifier is cryptographically bound to the cryptographic keys from which it was generated.\n~ Also known as: autonomous identifier.

\n
self-certifying identifier
\n

A subclass of verifiable identifier that is cryptographically verifiable without the need to rely on any third party for verification because the identifier is cryptographically bound to the cryptographic keys from which it was generated.\n~ Also known as: autonomous identifier.

\n
self-sovereign identity:
\n

A decentralized identity architecture that implements the Principles of SSI.

\n
sensitive data:
\n

Personal data that a reasonable person would view from a privacy protection standpoint as requiring special care above and beyond other personal data.

\n
session:
\n

See: communication session.

\n
sociotechnical system:
\n

An approach to complex organizational work design that recognizes the interaction between people and technology in workplaces. The term also refers to coherent systems of human relations, technical objects, and cybernetic processes that inhere to large, complex infrastructures. Social society, and its constituent substructures, qualify as complex sociotechnical systems.

\n
software agent:
\n

In computer science, a software agent is a computer program that acts for a user or other program in a relationship of agency, which derives from the Latin agere (to do): an agreement to act on one’s behalf. A user agent is a specific type of software agent that is used directly by an end-user as the principal.

\n
Sovrin Foundation:
\n

A 501 ©(4) nonprofit organization established to administer the governance framework governing the Sovrin Network, a public service utility enabling self-sovereign identity on the internet. The Sovrin Foundation is an independent organization that is responsible for ensuring the Sovrin identity system is public and globally accessible.

\n
spanning layer:
\n

A specific layer within a protocol stack that consists of a single protocol explicitly designed to provide interoperability between the protocols layers above it and below it.

\n
specification:
\n

See: technical specification.

\n
SSI:
\n

See: self-sovereign identity.

\n
SSL:
\n

See: Secure Sockets Layer.

\n
stream:
\n

In the context of digital communications, and in particular streaming media, a flow of data delivered in a continuous manner from a server to a client rather than in discrete messages.

\n
streaming media:
\n

Streaming media is multimedia for playback using an offline or online media player. Technically, the stream is delivered and consumed in a continuous manner from a client, with little or no intermediate storage in network elements. Streaming refers to the delivery method of content, rather than the content itself.

\n
subject:
\n

The entity described by one or more claims, particularly in the context of digital credentials.

\n
subscription:
\n

In the context of decentralized digital trust infrastructure, a subscription is an agreement between a first digital agent—the publisher—to automatically send a second digital agent—the subscriber—a message when a specific type of event happens in the wallet or vault managed by the first digital agent.

\n
supporting system:
\n

A system that operates at ToIP Layer 1, the trust support layer of the ToIP stack. A supporting system is one of three types of systems defined in the ToIP Technology Architecture Specification.

\n
Sybil attack:
\n

A Sybil attack is a type of attack on a computer network service in which an attacker subverts the service’s reputation system by creating a large number of pseudonymous identities and uses them to gain a disproportionately large influence. It is named after the subject of the book Sybil, a case study of a woman diagnosed with dissociative identity disorder.

\n
system of record:
\n

A system of record (SOR) or source system of record (SSoR) is a data management term for an information storage system (commonly implemented on a computer system running a database management system) that is the authoritative data source for a given data element or piece of information.

\n
tamper resistant:
\n

A process which makes alterations to the data difficult (hard to perform), costly (expensive to perform), or both.

\n
TCP:
\n

See: Transmission Control Protocol.

\n
TCP/IP:
\n

See: Internet Protocol Suite.

\n
TCP/IP stack:
\n

The protocol stack implementing the TCP/IP suite.

\n
technical requirement:
\n

A requirement for a hardware or software component or system. In the context of decentralized digital trust infrastructure, technical requirements are a subset of governance requirements. Technical requirements are often specified in a technical specification.

\n
technical specification:
\n

A document that specifies, in a complete, precise, verifiable manner, the requirements, design, behavior, or other characteristics of a system or component and often the procedures for determining whether these provisions have been satisfied.

\n
technical trust:
\n

A level of assurance in a trust relationship that can be achieved only via technical means such as hardware, software, network protocols, and cryptography. Cryptographic trust is a specialized type of technical trust.

\n
TEE:
\n

See: trusted execution environment.

\n
term:
\n

A unit of text (i.e., a word or phrase) that is used in a particular context or scope to refer to a concept (or a relation between concepts, or a property of a concept).

\n
terminology:
\n

Terminology is a group of specialized words and respective meanings in a particular field, and also the study of such terms and their use; the latter meaning is also known as terminology science. A term is a word, compound word, or multi-word expressions that in specific contexts is given specific meanings—these may deviate from the meanings the same words have in other contexts and in everyday language.[2] Terminology is a discipline that studies, among other things, the development of such terms and their interrelationships within a specialized domain. Terminology differs from lexicography, as it involves the study of concepts, conceptual systems and their labels (terms), whereas lexicography studies words and their meanings.

\n
terms community:
\n

A group of parties who share the need for a common terminology.

\n
terms wiki:
\n

A wiki website used by a terms community to input, maintain, and publish its terminology. The ToIP Foundation Concepts and Terminology Working Group has established a simple template for GitHub-based terms wikis.

\n
thing:
\n

An entity that is neither a natural person nor an organization and thus cannot be a party. A thing may be a natural thing or a man-made thing.

\n
third party:
\n

A party that is not directly involved in the trust relationship between a first party and a second party, but provides supporting services to either or both of them.

\n
three party model:
\n

The issuer—holder—verifier model used by all types of physical credentials and digital credentials to enable transitive trust decisions.

\n
timestamp:
\n

A token or packet of information that is used to provide assurance of timeliness; the timestamp contains timestamped data, including a time, and a signature generated by a trusted timestamp authority (TTA).

\n
TLS:
\n

See: Transport Layer Security.

\n
ToIP:
\n

See: Trust Over IP

\n
ToIP application:
\n

A trust application that runs at ToIP Layer 4, the trust application layer.

\n
ToIP channel:
\n

See: VID relationship.

\n
ToIP communication:
\n

Communication that uses the ToIP stack to deliver ToIP messages between ToIP endpoints, optionally using ToIP intermediaries, to provide authenticity, confidentiality, and correlation privacy.

\n
ToIP connection:
\n

A connection formed using the ToIP Trust Spanning Protocol between two ToIP endpoints identified with verifiable identifiers. A ToIP connection is instantiated as one or more VID relationships.

\n
ToIP controller:
\n

The controller of a ToIP identifier.

\n
ToIP Foundation:
\n

A non-profit project of the Linux Foundation chartered to define an overall architecture for decentralized digital trust infrastructure known as the ToIP stack.

\n
ToIP endpoint:
\n

An endpoint that communicates via the ToIP Trust Spanning Protocol as described in the ToIP Technology Architecture Specification.

\n
ToIP Governance Architecture Specification:
\n

The specification defining the requirements for the ToIP Governance Stack published by the ToIP Foundation.

\n
ToIP governance framework:
\n

A governance framework that conforms to the requirements of the ToIP Governance Architecture Specification.

\n
ToIP Governance Metamodel:
\n

A structural model for ToIP governance frameworks that specifies the recommended governance documents that should be included depending on the objectives of the trust community.

\n
ToIP Governance Stack:
\n

The governance half of the four layer ToIP stack as defined by the ToIP Governance Architecture Specification.

\n
ToIP identifier:
\n

A verifiable identifier for an entity that is addressable using the ToIP stack.

\n
ToIP intermediary:
\n

See: intermediary system.

\n
ToIP layer:
\n

One of four protocol layers in the ToIP stack. The four layers are ToIP Layer 1, ToIP Layer 2, ToIP Layer 3, and ToIP Layer 4.

\n
ToIP Layer 1:
\n

The trust support layer of the ToIP stack, responsible for supporting the trust spanning protocol at ToIP Layer 2.

\n
ToIP Layer 2:
\n

The trust spanning layer of the ToIP stack, responsible for enabling the trust task protocols at ToIP Layer 3.

\n
ToIP Layer 3:
\n

The trust task layer of the ToIP stack, responsible for enabling trust applications at ToIP Layer 4.

\n
ToIP Layer 4:
\n

The trust application layer of the ToIP stack, where end users have the direct human experience of using applications that call trust task protocols to engage in trust relationships and make trust decisions using ToIP decentralized digital trust infrastructure.

\n
ToIP message:
\n

A message communicated between ToIP endpoints using the ToIP stack.

\n
ToIP specification:
\n

A specification published by the ToIP Foundation. Specifications may be in one of three states: Draft Deliverable, Working Group Approved Deliverable, or ToIP Approved Deliverables

\n
ToIP stack:
\n

The layered architecture for decentralized digital trust infrastructure defined by the ToIP Foundation. The ToIP stack is a dual stack consisting of two halves: the ToIP Technology Stack and the ToIP Governance Stack. The four layers in the ToIP stack are ToIP Layer 1, ToIP Layer 2, ToIP Layer 3, and ToIP Layer 4.

\n
ToIP system:
\n

A computing system that participates in the ToIP Technology Stack. There are three types of ToIP systems: endpoint systems, intermediary systems, and supporting systems.

\n
ToIP trust network:
\n

A trust network implemented using the ToIP stack.

\n
ToIP Technology Architecture Specification:
\n

The technical specification defining the requirements for the ToIP Technology Stack published by the ToIP Foundation.

\n
ToIP Technology Stack:
\n

The technology half of the four layer ToIP stack as defined by the ToIP Technology Architecture Specification.

\n
ToIP trust community:
\n

A trust community governed by a ToIP governance framework.

\n
ToIP Trust Registry Protocol:
\n

The open standard trust task protocol defined by the ToIP Foundation to perform the trust task of querying a trust registry. The ToIP Trust Registry Protocol operates at Layer 3 of the ToIP stack.

\n
ToIP Trust Spanning Protocol:
\n

The ToIP Layer 2 protocol for verifiable messaging that implements the trust spanning layer of the ToIP stack.  The ToIP Trust Spanning Protocol enables actors in different digital trust domains to interact in a similar way to how the Internet Protocol (IP) enables devices on different local area networks to exchange data.

\n
transaction:
\n

A discrete event between a user and a system that supports a business or programmatic purpose. A digital system may have multiple categories or types of transactions, which may require separate analysis within the overall digital identity risk assessment.

\n
transitive trust decision:
\n

A trust decision made by a first party about a second party or another entity based on information about the second party or the other entity that is obtained from one or more third parties.

\n
Transmission Control Protocol:
\n

The Transmission Control Protocol (TCP) is one of the main protocols of the Internet protocol suite. It originated in the initial network implementation in which it complemented the Internet Protocol (IP). Therefore, the entire suite is commonly referred to as TCP/IP. TCP provides reliable, ordered, and error-checked delivery of a stream of octets (bytes) between applications running on hosts communicating via an IP network. Major internet applications such as the World Wide Web, email, remote administration, and file transfer rely on TCP, which is part of the Transport Layer of the TCP/IP suite. SSL/TLS often runs on top of TCP.

\n
Transport Layer Security:
\n

Transport Layer Security (TLS) is a cryptographic protocol designed to provide communications security over a computer network. The protocol is widely used in applications such as email, instant messaging, and Voice over IP, but its use in securing HTTPS remains the most publicly visible. The TLS protocol aims primarily to provide security, including privacy (confidentiality), integrity, and authenticity through the use of cryptography, such as the use of certificates, between two or more communicating computer applications.

\n
tribal knowledge:
\n

Knowledge that is known within an “in-group” of people but unknown outside of it. A tribe, in this sense, is a group of people that share such a common knowledge.

\n
trust:
\n

A belief that an entity will behave in a predictable manner in specified circumstances. The entity may be a person, process, object or any combination of such components. The entity can be of any size from a single hardware component or software module, to a piece of equipment identified by make and model, to a site or location, to an organization, to a nation-state. Trust, while inherently a subjective determination, can be based on objective evidence and subjective elements. The objective grounds for trust can include for example, the results of information technology product testing and evaluation. Subjective belief, level of comfort, and experience may supplement (or even replace) objective evidence, or substitute for such evidence when it is unavailable. Trust is usually relative to a specific circumstance or situation (e.g., the amount of money involved in a transaction, the sensitivity or criticality of information, or whether safety is an issue with human lives at stake). Trust is generally not transitive (e.g., you trust a friend but not necessarily a friend of a friend). Finally, trust is generally earned, based on experience or measurement.

\n
trust anchor:
\n

See: trust root.

\n
trust application:
\n

An application that runs at ToIP Layer 4 in order to perform trust tasks or engage in other verifiable messaging using the ToIP stack.

\n
trust application layer:
\n

In the context of the ToIP stack, the trust application layer is ToIP Layer 4. Applications running at this layer call trust task protocols at ToIP Layer 3.

\n
trust assurance:
\n

A process that provides a level of assurance sufficient to make a particular trust decision.

\n
trust basis:
\n

The properties of a verifiable identifier or a ToIP system that enable a party to appraise it to determine a trust limit.

\n
trust boundary:
\n

The border of a trust domain.

\n
trust chain:
\n

A set of cryptographically verifiable links between digital credentials or other data containers that enable transitive trust decisions.

\n
trust community:
\n

A set of parties who collaborate to achieve a mutual set of trust objectives.

\n
trust community:
\n

A set of parties who collaborate to achieve a mutual set of trust objectives.

\n
trust context:
\n

The context in which a specific party makes a specific trust decision. Many different factors may be involved in establishing a trust context, such as: the relevant interaction or transaction; the presence or absence of existing trust relationships; the applicability of one or more governance frameworks; and the location, time, network, and/or devices involved. A trust context may be implicit or explicit; if explicit, it may be identified using an identifier. A ToIP governance framework an example of an explicit trust context identified by a ToIP identifier.

\n
trust decision:
\n

A decision that a party needs to make about whether to engage in a specific interaction or transaction with another entity that involves real or perceived risks.

\n
trust domain:
\n

A security domain defined by a computer hardware or software architecture, a security policy, or a trust community, typically via a trust framework or governance framework.

\n
trust ecosystem:
\n

See digital trust ecosystem.

\n
trust establishment:
\n

The process two or more parties go through to establish a trust relationship. In the context of decentralized digital trust infrastructure, trust establishment takes place at two levels. At the technical trust level, it includes some form of key establishment. At the human trust level, it may be accomplished via an out-of-band introduction, the exchange of digital credentials, queries to one or more trust registries, or evaluation of some combination of human-readable and machine-readable governance frameworks.

\n
trust framework:
\n

A term (most frequently used in the digital identity industry) to describe a governance framework for a digital identity system, especially a federation.

\n
trust graph:
\n

A data structure describing the trust relationship between two or more entities. A simple trust graph may be expressed as a trust list. More complex trust graphs can be recorded or registered in and queried from a trust registry. Trust graphs can also be expressed via trust chains and chained credentials. Trust graphs can enable verifiers to make transitive trust decisions.

\n
trust limit:
\n

A limit to the degree a party is willing to trust an entity in a specific trust relationship within a specific trust context.

\n
trust list:
\n

A one-dimensional trust graph in which an authoritative source publishes a list of entities that are trusted in a specific trust context. A trust list can be considered a simplified form of a trust registry.

\n
trust network:
\n

A network of parties who are connected via trust relationships conforming to requirements defined in a legal regulation, trust framework or governance framework. A trust network is more formal than a digital trust ecosystem; the latter may connect parties more loosely via transitive trust relationships and/or across multiple trust networks.

\n
trust objective:
\n

An objective shared by the parties in a trust community to establish and maintain trust relationships.

\n
Trust over IP:
\n

A term coined by John Jordan to describe the decentralized digital trust infrastructure made possible by the ToIP stack. A play on the term Voice over IP (abbreviated VoIP).

\n
trust registry:
\n

A registry that serves as an authoritative source for trust graphs or other governed information describing one or more trust communities. A trust registry is typically authorized by a governance framework.

\n
trust registry protocol:
\n

See: ToIP Trust Registry Protocol.

\n
trust relationship:
\n

A relationship between a party and an entity in which the party has decided to trust the entity in one or more trust contexts up to a trust limit.

\n
trust root:
\n

The authoritative source that serves as the origin of a trust chain.

\n
trust service provider:
\n

In the context of specific digital trust ecosystems, such as the European Union’s eIDAS regulations, a trust service provider (TSP) is a legal entity that provides specific trust support services as required by legal regulations, trust frameworks, or governance frameworks. In the larger context of ToIP infrastructure, a TSP is a provider of services based on the ToIP stack. Most generally, a TSP is to the trust layer for the Internet what an Internet service provider (ISP) is to the Internet layer.

\n
trust support:
\n

A system, protocol, or other infrastructure whose function is to facilitate the establishment and maintenance of trust relationships at higher protocol layers. In the ToIP stack, the trust support layer is Layer 1.

\n
trust support layer:
\n

In the context of the ToIP stack, the trust support layer is ToIP Layer 1. It supports the operations of the ToIP Trust Spanning Protocol at ToIP Layer 2.

\n
trust spanning layer:
\n

A spanning layer designed to span between different digital trust domains. In the ToIP stack, ToIP Layer 2 is the trust spanning layer.

\n
trust spanning protocol:
\n

See: ToIP Trust Spanning Protocol.

\n
trust task:
\n

A specific task that involves establishing, verifying, or maintaining trust relationships or exchanging verifiable messages or verifiable data that can be performed on behalf of a trust application by a trust task protocol at Layer 3 of the ToIP stack.

\n
trust task layer:
\n

In the context of the ToIP stack, the trust task layer is ToIP Layer 3. It supports trust applications operating at ToIP Layer 4.

\n
trust task protocol:
\n

A ToIP Layer 3 protocol that implements a specific trust task on behalf of a ToIP Layer 4 trust application.

\n
trust triangle:
\n

See: three-party model.

\n
trusted execution environment:
\n

A trusted execution environment (TEE) is a secure area of a main processor. It helps code and data loaded inside it to be protected with respect to confidentiality and integrity. Data integrity prevents unauthorized entities from outside the TEE from altering data, while code integrity prevents code in the TEE from being replaced or modified by unauthorized entities, which may also be the computer owner itself as in certain DRM schemes.

\n
trusted role:
\n

A role that performs restricted activities for an organization after meeting competence, security and background verification requirements for that role.

\n
trusted third party:
\n

In cryptography, a trusted third party (TTP) is an entity which facilitates interactions between two parties who both trust the third party; the third party reviews all critical transaction communications between the parties, based on the ease of creating fraudulent digital content. In TTP models, the relying parties use this trust to secure their own interactions. TTPs are common in any number of commercial transactions and in cryptographic digital transactions as well as cryptographic protocols, for example, a certificate authority (CA) would issue a digital certificate to one of the two parties in the next example. The CA then becomes the TTP to that certificate’s issuance. Likewise transactions that need a third party recordation would also need a third-party repository service of some kind.

\n
trusted timestamp authority:
\n

An authority that is trusted to provide accurate time information in the form of a timestamp.

\n
trustworthy:
\n

A property of an entity that has the attribute of trustworthiness.

\n
trustworthiness:
\n

An attribute of a person or organization that provides confidence to others of the qualifications, capabilities, and reliability of that entity to perform specific tasks and fulfill assigned responsibilities. Trustworthiness is also a characteristic of information technology products and systems. The attribute of trustworthiness, whether applied to people, processes, or technologies, can be measured, at least in relative terms if not quantitatively. The determination of trustworthiness plays a key role in establishing trust relationships among persons and organizations. The trust relationships are key factors in risk decisions made by senior leaders/executives.

\n
TSP:
\n

See: trust service provider, trust spanning protocol.

\n
TTA:
\n

See: trusted timestamp authority.

\n
TTP:
\n

See: trusted third party.

\n
UDP:
\n

See: User Datagram Protocol.

\n
unicast:
\n

In computer networking, unicast is a one-to-one transmission from one point in the network to another point; that is, one sender and one receiver, each identified by a network address (a unicast address). Unicast is in contrast to multicast and broadcast which are one-to-many transmissions. Internet Protocol unicast delivery methods such as Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) are typically used.

\n
unicast address:
\n

A network address used for a unicast.

\n
user agent:
\n

A software agent that is used directly by the end-user as the principal. Browsers, email clients, and digital wallets are all examples of user agents.

\n
User Datagram Protocol:
\n

In computer networking, the User Datagram Protocol (UDP) is one of the core communication protocols of the Internet protocol suite used to send messages (transported as datagrams in packets) to other hosts on an Internet Protocol (IP) network. Within an IP network, UDP does not require prior communication to set up communication channels or data paths.

\n
utility governance framework:
\n

A governance framework for a digital trust utility. A utility governance framework may be a component of or referenced by an ecosystem governance framework or a credential governance framework.

\n
validation:
\n

An action an agent (of a principal) performs to determine whether a digital object or set of data meets the requirements of a specific party.

\n
vault:
\n

See: digital vault.

\n
VC:
\n

See: verifiable credential.

\n
verifiability (of a digital object:
\n

The property of a digital object, assertion, claim, or communication, being verifiable.

\n
verifiability (of a digital object:
\n

The property of a digital object, assertion, claim, or communication, being verifiable.

\n
verifiability (of a digital object:
\n

The property of a digital object, assertion, claim, or communication, being verifiable.

\n
verifiable:
\n

In the context of digital communications infrastructure, the ability to determine the authenticity of a communication (e.g., sender, contents, claims, metadata, provenance), or the underlying sociotechnical infrastructure (e.g., governance, roles, policies, authorizations, certifications).

\n
verifiable credential:
\n

A standard data model and representation format for cryptographically-verifiable digital credentials as defined by the W3C Verifiable Credentials Data Model specification.

\n
verifiable data:
\n

Any digital data or object that is digitally signed in such a manner that it can be cryptographically verified.

\n
verifiable data registry:
\n

A registry that facilitates the creation, verification, updating, and/or deactivation of decentralized identifiers and DID documents. A verifiable data registry may also be used for other cryptographically-verifiable data structures such as verifiable credentials.

\n
verifiable identifier:
\n

An identifier over which the controller can provide cryptographic proof of control.

\n
verifiable identifier:
\n

An identifier over which the controller can provide cryptographic proof of control.

\n
verifiable message:
\n

A message communicated as verifiable data.

\n
verification:
\n

An action an agent (of a principal) performs to determine the authenticity of a claim or other digital object using a cryptographic key.

\n
verifier (of a claim or credential):
\n

A role an agent performs to perform verification of one or more proofs of the claims in a digital credential.

\n
VID:
\n

See ​​verifiable identifier.

\n
VID relationship:
\n

The communications relationship formed between two VIDs using the ToIP Trust Spanning Protocol. A particular feature of this protocol is its ability to establish as many VID relationships as needed to establish different relationship contexts between the communicating entities.

\n
VID-to-VID:
\n

The specialized type of peer-to-peer communications enabled by the ToIP Trust Spanning Protocol. Each pair of VIDs creates a unique VID relationship.

\n
virtual vault:
\n

A digital vault enclosed inside another digital vault by virtue of having its own verifiable identifier (VID) and its own set of encryption keys that are separate from those used to unlock the enclosing vault.

\n
Voice over IP:
\n

Voice over Internet Protocol (VoIP), also called IP telephony, is a method and group of technologies for voice calls for the delivery of voice communication sessions over Internet Protocol (IP) networks, such as the Internet.

\n
VoIP:
\n

See: Voice over IP.

\n
W3C Verifiable Credentials Data Model Specification:
\n

A W3C Recommendation defining a standard data model and representation format for cryptographically-verifiable digital credentials. Version 1.1 was published on 03 March 2022.

\n
wallet:
\n

See: digital wallet.

\n
wallet engine:
\n

The set of software components that form the core of a digital wallet, but which by themselves are not sufficient to deliver a fully functional wallet for use by a digital agent (of a principal). A wallet engine is to a digital wallet what a browser engine is to a web browser.

\n
witness:
\n

A computer system that receives, verifies, and stores proofs of key events for a verifiable identifier (especially an autonomous identifier). Each witness controls its own verifiable identifier used to sign key event messages stored by the witness. A witness may use any suitable computer system or database architecture, including a file, centralized database, distributed database, distributed ledger, or blockchain.

\n
zero-knowledge proof:
\n

A specific kind of cryptographic proof that proves facts about data to a verifier without revealing the underlying data itself. A common example is proving that a person is over or under a specific age without revealing the person’s exact birthdate.

\n
zero-knowledge service:
\n

In cloud computing, the term “zero-knowledge” refers to an online service that stores, transfers or manipulates data in a way that maintains a high level of confidentiality, where the data is only accessible to the data's owner (the client), and not to the service provider. This is achieved by encrypting the raw data at the client’s side or end-to-end (in case there is more than one client), without disclosing the password to the service provider. This means that neither the service provider, nor any third party that might intercept the data, can decrypt and access the data without prior permission, allowing the client a higher degree of privacy than would otherwise be possible. In addition, zero-knowledge services often strive to hold as little metadata as possible, holding only that data that is functionally needed by the service.

\n
zero-knowledge service provider:
\n

The provider of a zero-knowledge service that hosts encrypted data on behalf of the principal but does not have access to the private keys in order to be able to decrypt it.

\n
zero-trust architecture:
\n

A network security architecture based on the core design principle “never trust, always verify”, so that all actors are denied access to resources pending verification.

\n
ZKP:
\n

See: zero-knowledge proof.

\n
anonymous
\n

An adjective describing when the identity of a natural person or other actor is unknown.

\n
assurance level
\n

A level of confidence that may be relied on by others. Different types of assurance levels are defined for different types of trust assurance mechanisms. Examples include authenticator assurance level, federation assurance level, and identity assurance level.

\n
authorization
\n

The process of verifying that a requested action or service is approved for a specific entity.

\n
out-of-band introduction
\n

A process by which two or more entities exchange VIDs in order to form a cryptographically verifiable connection (e.g., a ToIP connection), such as by scanning a QR code (in person or remotely) or clicking a deep link.

\n
out-of-band introduction
\n

A process by which two or more entities exchange VIDs in order to form a cryptographically verifiable connection (e.g., a ToIP connection), such as by scanning a QR code (in person or remotely) or clicking a deep link.

\n
permission
\n

Authorization to perform some action on a system.

\n
policy
\n

Statements, rules or assertions that specify the correct or expected behavior of an entity.

\n
real world identity
\n

A term used to describe the opposite of digital identity, i.e., an identity (typically for a person) in the physical instead of the digital world.

\n
self-certifying identifier
\n

A subclass of verifiable identifier that is cryptographically verifiable without the need to rely on any third party for verification because the identifier is cryptographically bound to the cryptographic keys from which it was generated.\n~ Also known as: autonomous identifier.

\n
self-certifying identifier
\n

A subclass of verifiable identifier that is cryptographically verifiable without the need to rely on any third party for verification because the identifier is cryptographically bound to the cryptographic keys from which it was generated.\n~ Also known as: autonomous identifier.

\n
NIST-CSRC
\n

NIST Computer Security Resource Center Glossary

\n
","
AAL:
\n

See: authenticator assurance level.

\n
ABAC:
\n

See: attribute-based access control.

\n
access control:
\n

The process of granting or denying specific requests for obtaining and using information and related information processing services.

\n
ACDC
\n

See: Authentic Chained Data Container.

\n
action
\n

Something that is actually done (a ‘unit of work’ that is executed) by a single actor (on behalf of a given party), as a single operation, in a specific context.Source: eSSIF-Lab.

\n
actor
\n

An entity that can act (do things/execute actions), e.g. people, machines, but not organizations. A digital agent can serve as an actor acting on behalf of its principal.Source: eSSIF-Lab.

\n
address
\n

See: network address.

\n
administering authority:
\n

See: administering body.

\n
administering body:
\n

A legal entity delegated by a governing body to administer the operation of a governance framework and governed infrastructure for a digital trust ecosystem, such as one or more trust registries.

\n
agency:
\n

In the context of decentralized digital trust infrastructure, the empowering of a party to act independently of its own accord, and in particular to empower the party to employ an agent to act on the party’s behalf.

\n
agent:
\n

An actor that is executing an action on behalf of a party (called the principal of that actor). In the context of decentralized digital trust infrastructure, the term “agent” is most frequently used to mean a digital agent.

\n
AID:
\n

See autonomic identifier.

\n
anonymous
\n

An adjective describing when the identity of a natural person or other actor is unknown.

\n
anycast:
\n

Anycast is a network addressing and routing methodology in which a single IP-address is shared by devices (generally servers) in multiple locations. Routers direct packets addressed to this destination to the location nearest the sender, using their normal decision-making algorithms, typically the lowest number of BGP network hops. Anycast routing is widely used by content delivery networks such as web and name servers, to bring their content closer to end users.

\n
anycast address:
\n

A network address (especially an IP address) used for anycast routing of network transmissions.

\n
appraisability (of a communications endpoint):
\n

The ability for a communication endpoint identified with a verifiable identifier to be appraised for the set of its properties that enable a relying party or a verifier to make a trust decision about communicating with that endpoint.

\n
assurance level
\n

A level of confidence that may be relied on by others. Different types of assurance levels are defined for different types of trust assurance mechanisms. Examples include authenticator assurance level, federation assurance level, and identity assurance level.

\n
appropriate friction:
\n

A user-experience design principle for information systems (such as digital wallets) specifying that the level of attention required of the holder for a particular transaction should provide a reasonable opportunity for an informed choice by the holder.

\n
attestation:
\n

The issue of a statement, based on a decision, that fulfillment of specified requirements has been demonstrated. In the context of decentralized digital trust infrastructure, an attestation usually has a digital signature so that it is cryptographically verifiable.

\n
attribute:
\n

An identifiable set of data that describes an entity, which is the subject of the attribute.

\n
attribute-based access control:
\n

An access control approach in which access is mediated based on attributes associated with subjects (requesters) and the objects to be accessed. Each object and subject has a set of associated attributes, such as location, time of creation, access rights, etc. Access to an object is authorized or denied depending upon whether the required (e.g., policy-defined) correlation can be made between the attributes of that object and of the requesting subject.

\n
audit (of system controls):
\n

Independent review and examination of records and activities to assess the adequacy of system controls, to ensure compliance with established policies and operational procedures.

\n
audit log:
\n

An audit log is a security-relevant chronological record, set of records, and/or destination and source of records that provide documentary evidence of the sequence of activities that have affected at any time a specific operation, procedure, event, or device.

\n
auditor (of an entity):
\n

The party responsible for performing an audit. Typically an auditor must be accredited.

\n
authentication(of a user; process; or device):
\n

Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in an information system.

\n
authentication(of a user; process; or device):
\n

Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in an information system.

\n
authenticator
\n

Something the claimant possesses and controls (typically a cryptographic module or password) that is used to authenticate the claimant’s identity.

\n
authenticator assurance level
\n

A measure of the strength of an authentication mechanism and, therefore, the confidence in it.

\n
authenticator assurance level
\n

A measure of the strength of an authentication mechanism and, therefore, the confidence in it.

\n
Authentic Chained Data Container:
\n

A digital data structure designed for both cryptographic verification and chaining of data containers. ACDC may be used for digital credentials.

\n
authenticity:
\n

The property of being genuine and being able to be verified and trusted; confidence in the validity of a transmission, a message, or message originator.

\n
authorization
\n

The process of verifying that a requested action or service is approved for a specific entity.

\n
authorized organizational representative
\n

A person who has the authority to make claims, sign documents or otherwise commit resources on behalf of an organization.

\n
authorization graph:
\n

A graph of the authorization relationships between different entities in a trust-community. In a digital trust ecosystem, the governing body is typically the trust root of an authorization graph. In some cases, an authorization graph can be traversed by making queries to one or more trust registries.

\n
authoritative source:
\n

A source of information that a relying party considers to be authoritative for that information. In ToIP architecture, the trust registry authorized by the governance framework (#governance-framework) for a [trust community is typically considered an authoritative source by the members of that trust community. A system of record is an authoritative source for the data records it holds. A trust root is an authoritative source for the beginning of a trust chain.

\n
authority:
\n

A party of which certain decisions, ideas, rules etc. are followed by other parties.

\n
autonomic identifier:
\n

The specific type of self-certifying identifier specified by the KERI specifications.

\n
biometric:
\n

A measurable physical characteristic or personal behavioral trait used to recognize the AID, or verify the claimed identity, of an applicant. Facial images, fingerprints, and iris scan samples are all examples of biometrics.

\n
blockchain:
\n

A distributed digital ledger of cryptographically-signed transactions that are grouped into blocks. Each block is cryptographically linked to the previous one (making it tamper evident) after validation and undergoing a consensus decision. As new blocks are added, older blocks become more difficult to modify (creating tamper resistance). New blocks are replicated across copies of the ledger within the network, and any conflicts are resolved automatically using established rules.

\n
broadcast:
\n

In computer networking, telecommunication and information theory, broadcasting is a method of transferring a message to all recipients simultaneously. Broadcast delivers a message to all nodes in the network using a one-to-all association; a single datagram (or packet) from one sender is routed to all of the possibly multiple endpoints associated with the broadcast address. The network automatically replicates datagrams as needed to reach all the recipients within the scope of the broadcast, which is generally an entire network subnet.

\n
broadcast address:
\n

A broadcast address is a network address used to transmit to all devices connected to a multiple-access communications network. A message sent to a broadcast address may be received by all network-attached hosts. In contrast, a multicast address is used to address a specific group of devices, and a unicast address is used to address a single device. For network layer communications, a broadcast address may be a specific IP address.

\n
C2PA:
\n

See: Coalition for Content Provenance and Authenticity.

\n
CA:
\n

See: certificate authority.

\n
CAI:
\n

See: Content Authenticity Initiative.

\n
certification authority:
\n

See: certificate authority.

\n
certificate authority:
\n

The entity in a public key infrastructure (PKI) that is responsible for issuing public key certificates and exacting compliance to a PKI policy.

\n
certification (of a party):
\n

A comprehensive assessment of the management, operational, and technical security controls in an information system, made in support of security accreditation, to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the security requirements for the system.

\n
certification body:
\n

A legal entity that performs certification.

\n
chain of trust:
\n

See: trust chain.

\n
chained credentials:
\n

Two or more credentials linked together to create a trust chain between the credentials that is cryptographically verifiable.

\n
chaining:
\n

See: trust chain.

\n
channel:
\n

See: communication channel.

\n
ciphertext:
\n

Encrypted (enciphered) data. The confidential form of the plaintext that is the output of the encryption function.

\n
claim:
\n

An assertion about a subject, typically expressed as an attribute or property of the subject. It is called a “claim” because the assertion is always made by some party, called the issuer of the claim, and the validity of the claim must be judged by the verifier.

\n
Coalition for Content Provenance and Authenticity:
\n

C2PA is a Joint Development Foundation project of the Linux Foundation that addresses the prevalence of misleading information online through the development of technical standards for certifying the source and history (or provenance) of media content.

\n
communication:
\n

The transmission of information.

\n
communication endpoint:
\n

A type of communication network node. It is an interface exposed by a communicating party or by a communication channel. An example of the latter type of a communication endpoint is a publish-subscribe topic or a group in group communication systems.

\n
communication channel:
\n

A communication channel refers either to a physical transmission medium such as a wire, or to a logical connection over a multiplexed medium such as a radio channel in telecommunications and computer networking. A channel is used for information transfer of, for example, a digital bit stream, from one or several senders to one or several receivers.

\n
communication metadata:
\n

Metadata that describes the sender, receiver, routing, handling, or contents of a communication. Communication metadata is often observable even if the contents of the communication are encrypted.

\n
communication session:
\n

A finite period for which a communication channel is instantiated and maintained, during which certain properties of that channel, such as authentication of the participants, are in effect. A session has a beginning, called the session initiation, and an ending, called the session termination.

\n
complex password:
\n

A password that meets certain security requirements, such as minimum length, inclusion of different character types, non-repetition of characters, and so on.

\n
compliance:
\n

In the context of decentralized digital trust infrastructure, the extent to which a system, actor, or party conforms to the requirements of a governance framework or trust framework that pertains to that particular entity.

\n
concept:
\n

An abstract idea that enables the classification of entities, i.e., a mental construct that enables an instance of a class of entities to be distinguished from entities that are not an instance of that class. A concept can be identified with a term.

\n
confidential computing:
\n

Hardware-enabled features that isolate and process encrypted data in memory so that the data is at less risk of exposure and compromise from concurrent workloads or the underlying system and platform.

\n
confidentiality:
\n

In a communications context, a type of privacy protection in which messages use encryption or other privacy-preserving technologies so that only authorized parties have access.

\n
connection:
\n

A communication channel established between two communication endpoints. A connection may be ephemeral or persistent.

\n
Content Authenticity Initiative:
\n

The Content Authenticity Initiative (CAI) is an association founded in November 2019 by Adobe, the New York Times and Twitter. The CAI promotes an industry standard for provenance metadata defined by the C2PA. The CAI cites curbing disinformation as one motivation for its activities.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
controller (of a key:
\n

In the context of digital communications, the entity in control of sending and receiving digital communications. In the context of decentralized digital trust infrastructure, the entity in control of the cryptographic keys necessary to perform cryptographically verifiable actions using a digital agent and digital wallet. In a ToIP context, the entity in control of a ToIP endpoint.

\n
consent management:
\n

A system, process or set of policies under which a person agrees to share personal data for specific usages. A consent management system will typically create a record of such consent.

\n
controlled document:
\n

A governance document whose authority is derived from a primary document.

\n
correlation privacy:
\n

In a communications context, a type of privacy protection in which messages use encryption, hashes, or other privacy-preserving technologies to avoid the use of identifiers or other content that unauthorized parties may use to correlate the sender and/or receiver(s).

\n
counterparty:
\n

From the perspective of one party, the other party in a transaction, such as a financial transaction.

\n
credential:
\n

A container of claims describing one or more subjects. A credential is generated by the issuer of the credential and given to the holder of the credential. A credential typically includes a signature or some other means of proving its authenticity. A credential may be either a physical credential or a digital credential.

\n
credential family:
\n

A set of related digital credentials defined by a governing body (typically in a governance framework) to empower transitive trust decisions among the participants in a digital trust ecosystem.

\n
credential governance framework:
\n

A governance framework for a credential family. A credential governance framework may be included within or referenced by an ecosystem governance framework.

\n
credential offer:
\n

A protocol request invoked by an issuer to offer to issue a digital credential to the  holder of a digital wallet. If the request is invoked by the holder, it is called an issuance request.

\n
credential request:
\n

See: issuance request.

\n
credential schema:
\n

A data schema describing the structure of a digital credential. The W3C Verifiable Credentials Data Model Specification defines a set of requirements for credential schemas.

\n
criterion:
\n

In the context of terminology, a written description of a concept that anyone can evaluate to determine whether or not an entity is an instance or example of that concept. Evaluation leads to a yes/no result.

\n
cryptographic binding:
\n

Associating two or more related elements of information using cryptographic techniques.

\n
cryptographic key:
\n

A key in cryptography is a piece of information, usually a string of numbers or letters that are stored in a file, which, when processed through a cryptographic algorithm, can encode or decode cryptographic data. Symmetric cryptography refers to the practice of the same key being used for both encryption and decryption. Asymmetric cryptography has separate keys for encrypting and decrypting. These keys are known as the public keys and private keys, respectively.

\n
cryptographic trust:
\n

A specialized type of technical trust that is achieved using cryptographic algorithms.

\n
cryptographic verifiability:
\n

The property of being cryptographically verifiable.

\n
cryptographically verifiable:
\n

A property of a data structure that has been digitally signed using a private key such that the digital signature can be verified using the public key. Verifiable data, verifiable messages, verifiable credentials, and verifiable data registries are all cryptographically verifiable. Cryptographic verifiability is a primary goal of the ToIP Technology Stack.

\n
cryptographically bound:
\n

A state in which two or more elements of information have a cryptographic binding.

\n
custodial wallet:
\n

A digital wallet that is directly in the custody of a principal, i.e., under the principal’s direct personal or organizational control. A digital wallet that is in the custody of a third party is called a non-custodial wallet.

\n
custodian:
\n

A third party that has been assigned rights and duties in a custodianship arrangement for the purpose of hosting and safeguarding a principal’s private keys, digital wallet and digital assets on the principal’s behalf. Depending on the custodianship arrangement, the custodian may act as an exchange and provide additional services, such as staking, lending, account recovery, or security features.

\n
custodianship arrangement:
\n

The informal terms or formal legal agreement under which a custodian agrees to provide service to a principal.

\n
dark pattern:
\n

A design pattern, mainly in user interfaces, that has the effect of deceiving individuals into making choices that are advantageous to the designer.

\n
data:
\n

In the pursuit of knowledge, data is a collection of discrete values that convey information, describing quantity, quality, fact, statistics, other basic units of meaning, or simply sequences of symbols that may be further interpreted. A datum is an individual value in a collection of data.

\n
datagram:
\n

See: data packet.

\n
data packet:
\n

In telecommunications and computer networking, a network packet is a formatted unit of data carried by a packet-switched network such as the Internet. A packet consists of control information and user data; the latter is also known as the payload. Control information provides data for delivering the payload (e.g., source and destination network addresses, error detection codes, or sequencing information). Typically, control information is found in packet headers and trailers.

\n
data schema:
\n

A description of the structure of a digital document or object, typically expressed in a machine-readable language in terms of constraints on the structure and content of documents or objects of that type. A credential schema is a particular type of data schema.

\n
data subject:
\n

The natural person that is described by personal data. Data subject is the term used by the EU General Data Protection Regulation.

\n
data vault:
\n

See: digital vault.

\n
decentralized identifier:
\n

A globally unique persistent identifier that does not require a centralized registration authority and is often generated and/or registered cryptographically. The generic format of a DID is defined in section 3.1 DID Syntax of the W3C Decentralized Identifiers (DIDs) 1.0 specification. A specific DID scheme is defined in a DID method specification.

\n
decentralized identifier:
\n

A globally unique persistent identifier that does not require a centralized registration authority and is often generated and/or registered cryptographically. The generic format of a DID is defined in section 3.1 DID Syntax of the W3C Decentralized Identifiers (DIDs) 1.0 specification. A specific DID scheme is defined in a DID method specification.

\n
decentralized identifier:
\n

A globally unique persistent identifier that does not require a centralized registration authority and is often generated and/or registered cryptographically. The generic format of a DID is defined in section 3.1 DID Syntax of the W3C Decentralized Identifiers (DIDs) 1.0 specification. A specific DID scheme is defined in a DID method specification.

\n
decentralized identifier:
\n

A globally unique persistent identifier that does not require a centralized registration authority and is often generated and/or registered cryptographically. The generic format of a DID is defined in section 3.1 DID Syntax of the W3C Decentralized Identifiers (DIDs) 1.0 specification. A specific DID scheme is defined in a DID method specification.

\n
decentralized identity:
\n

A digital identity architecture in which a digital identity is established via the control of a set of cryptographic keys in a digital wallet so that the controller is not dependent on any external identity provider or other third party.

\n
Decentralized Identity Foundation:
\n

A non-profit project of the Linux Foundation chartered to develop the foundational components of an open, standards-based, decentralized identity ecosystem for people, organizations, apps, and devices.

\n
Decentralized Web Node:
\n

A decentralized personal and application data storage and message relay node, as defined in the DIF Decentralized Web Node specification. Users may have multiple nodes that replicate their data between them.

\n
deceptive pattern:
\n

See: dark pattern.

\n
decryption:
\n

The process of changing ciphertext into plaintext using a cryptographic algorithm and key. The opposite of encryption.

\n
deep link:
\n

In the context of the World Wide Web, deep linking is the use of a hyperlink that links to a specific, generally searchable or indexed, piece of web content on a website (e.g. “https://example.com/path/page”), rather than the website’s home page (e.g., “https://example.com”). The URL contains all the information needed to point to a particular item. Deep linking is different from mobile deep linking, which refers to directly linking to in-app content using a non-HTTP URI.

\n
definition:
\n

A textual statement defining the meaning of a term by specifying criterion that enable the concept identified by the term to be distinguished from all other concepts within the intended scope.

\n
delegation:
\n

TODO

\n
delegation credential:
\n

TODO

\n
dependent:
\n

An entity for the caring for and/or protecting/guarding/defending of which a guardianship arrangement has been established with a guardian.

\n
device controller:
\n

The controller of a device capable of digital communications, e.g., a smartphone, tablet, laptop, IoT device, etc.

\n
dictionary:
\n

A dictionary is a listing of lexemes (words or terms) from the lexicon of one or more specific languages, often arranged alphabetically, which may include information on definitions, usage, etymologies, pronunciations, translation, etc. It is a lexicographical reference that shows inter-relationships among the data. Unlike a glossary, a dictionary may provide multiple definitions of a term depending on its scope or context.

\n
DID controller:
\n

An entity that has the capability to make changes to a DID document. A DID might have more than one DID controller. The DID controller(s) can be denoted by the optional controller property at the top level of the DID document. Note that a DID controller might be the DID subject.

\n
DID document:
\n

A set of data describing the DID subject, including mechanisms, such as cryptographic public keys, that the DID subject or a DID delegate can use to authenticate itself and prove its association with the DID. A DID document might have one or more different representations as defined in section 6 of the W3C Decentralized Identifiers (DIDs) 1.0 specification.

\n
DID method:
\n

A definition of how a specific DID method scheme is implemented. A DID method is defined by a DID method specification, which specifies the precise operations by which DIDs and DID documents are created, resolved, updated, and deactivated.

\n
DID subject:
\n

The entity identified by a DID and described by a DID document. Anything can be a DID subject: person, group, organization, physical thing, digital thing, logical thing, etc.

\n
DID URL:
\n

A DID plus any additional syntactic component that conforms to the definition in section 3.2 of the W3C Decentralized Identifiers (DIDs) 1.0 specification. This includes an optional DID path (with its leading / character), optional DID query (with its leading ? character), and optional DID fragment (with its leading # character).

\n
digital agent:
\n

In the context of ​​decentralized digital trust infrastructure, an agent (specifically a type of software agent) that operates in conjunction with a digital wallet.

\n
digital asset:
\n

A digital asset is anything that exists only in digital form and comes with a distinct usage right. Data that do not possess that right are not considered assets.

\n
digital certificate:
\n

See: public key certificate.

\n
digital credential:
\n

A credential in digital form that is signed with a digital signature and held in a digital wallet. A digital credential is issued to a holder by an issuer; a proof of the credential is presented by the holder to a verifier.

\n
digital ecosystem:
\n

A digital ecosystem is a distributed, adaptive, open socio-technical system with properties of self-organization, scalability and sustainability inspired from natural ecosystems. Digital ecosystem models are informed by knowledge of natural ecosystems, especially for aspects related to competition and collaboration among diverse entities.

\n
digital identity:
\n

An identity expressed in a digital form for the purpose representing the identified entity within a computer system or digital network.

\n
digital rights management:
\n

Digital rights management (DRM) is the management of legal access to digital content. Various tools or technological protection measures (TPM) like access control technologies, can restrict the use of proprietary hardware and copyrighted works. DRM technologies govern the use, modification and distribution of copyrighted works (e.g. software, multimedia content) and of systems that enforce these policies within devices.

\n
digital trust ecosystem:
\n

A digital ecosystem in which the participants are one or more interoperating trust communities. Governance of the various roles of governed parties within a digital trust ecosystem (e.g., issuers, holders, verifiers, certification bodies, auditors) is typically managed by a governing body using a governance framework as recommended in the ToIP Governance Stack. Many digital trust ecosystems will also maintain one or more trust lists and/or trust registries.

\n
digital trust utility:
\n

An information system, network, distributed database, or blockchain designed to provide one or more supporting services to higher level components of decentralized digital trust infrastructure. In the ToIP stack, digital trust utilities are at Layer 1. A verifiable data registry is one type of digital trust utility.

\n
digital signature:
\n

A digital signature is a mathematical scheme for verifying the authenticity of digital messages or documents. A valid digital signature, where the prerequisites are satisfied, gives a recipient very high confidence that the message was created by a known sender (authenticity), and that the message was not altered in transit (integrity).

\n
digital vault:
\n

A secure container for data whose controller is the principal. A digital vault is most commonly used in conjunction with a digital wallet and a digital agent. A digital vault may be implemented on a local device or in the cloud; multiple digital vaults may be used by the same principal across different devices and/or the cloud; if so they may use some type of synchronization. If the capability is supported, data may flow into or out of the digital vault automatically based on subscriptions approved by the controller.

\n
digital wallet:
\n

A user agent, optionally including a hardware component, capable of securely storing and processing cryptographic keys, digital credentials, digital assets and other sensitive private data that enables the controller to perform cryptographically verifiable operations. A non-custodial wallet is directly in the custody of a principal. A custodial wallet is in the custody of a third party. Personal wallets are held by individual persons; enterprise wallets are held by organizations or other legal entities.

\n
distributed ledger:
\n

A distributed ledger (also called a shared ledger or distributed ledger technology or DLT) is the consensus of replicated, shared, and synchronized digital data that is geographically spread (distributed) across many sites, countries, or institutions. In contrast to a centralized database, a distributed ledger does not require a central administrator, and consequently does not have a single (central) point-of-failure. In general, a distributed ledger requires a peer-to-peer (P2P) computer network and consensus algorithms so that the ledger is reliably replicated across distributed computer nodes (servers, clients, etc.). The most common form of distributed ledger technology is the blockchain, which can either be on a public or private network.

\n
domain:
\n

See: security domain.

\n
DRM:
\n

See: digital rights management.

\n
DWN:
\n

See: Decentralized Web Node.

\n
ecosystem:
\n

See: digital ecosystem.

\n
ecosystem governance framework:
\n

A governance framework for a digital trust ecosystem. An ecosystem governance framework may incorporate, aggregate, or reference other types of governance frameworks such as a credential governance framework or a utility governance framework.

\n
ecosystem governance framework:
\n

A governance framework for a digital trust ecosystem. An ecosystem governance framework may incorporate, aggregate, or reference other types of governance frameworks such as a credential governance framework or a utility governance framework.

\n
eIDAS:
\n

eIDAS (electronic IDentification, Authentication and trust Services) is an EU regulation with the stated purpose of governing “electronic identification and trust services for electronic transactions”. It passed in 2014 and its provisions came into effect between 2016-2018.

\n
encrypted data vault:
\n

See: digital vault.

\n
encryption:
\n

Cryptographic transformation of data (called plaintext) into a form (called ciphertext) that conceals the data’s original meaning to prevent it from being known or used. If the transformation is reversible, the corresponding reversal process is called decryption, which is a transformation that restores encrypted data to its original state.

\n
end-to-end encryption:
\n

Encryption that is applied to a communication before it is transmitted from the sender’s communication endpoint and cannot be decrypted until after it is received at the receiver’s communication endpoint. When end-to-end encryption is used, the communication cannot be decrypted in transit no matter how many intermediaries are involved in the routing process.

\n
End-to-End Principle:
\n

The end-to-end principle is a design framework in computer networking. In networks designed according to this principle, guaranteeing certain application-specific features, such as reliability and security, requires that they reside in the communicating end nodes of the network. Intermediary nodes, such as gateways and routers, that exist to establish the network, may implement these to improve efficiency but cannot guarantee end-to-end correctness.

\n
endpoint:
\n

See: communication endpoint.

\n
endpoint system:
\n

The system that operates a communications endpoint. In the context of the ToIP stack, an endpoint system is one of three types of systems defined in the ToIP Technology Architecture Specification.

\n
enterprise data vault:
\n

A digital vault whose controller is an organization.

\n
enterprise wallet:
\n

A digital wallet whose holder is an organization.

\n
entity:
\n

Someone or something that is known to exist.

\n
entity:
\n

Someone or something that is known to exist.

\n
ephemeral connection:
\n

A connection that only exists for the duration of a single communication session or transaction.

\n
expression language:
\n

A language for creating a computer-interpretable (machine-readable) representation of specific knowledge.

\n
FAL:
\n

See: federation assurance level.

\n
federated identity:
\n

A digital identity architecture in which a digital identity established on one computer system, network, or trust domain is linked to other computer systems, networks, or trust domains for the purpose of identifying the same entity across those domains.

\n
federation:
\n

A group of organizations that collaborate to establish a common trust framework or governance framework for the exchange of identity data in a federated identity system.

\n
federation assurance level:
\n

A category that describes the federation protocol used to communicate an assertion containing authentication) and attribute information (if applicable) to a relying party, as defined in NIST SP 800-63-3 in terms of three levels: FAL 1 (Some confidence), FAL 2 (High confidence), FAL 3 (Very high confidence).

\n
fiduciary:
\n

A fiduciary is a person who holds a legal or ethical relationship of trust with one or more other parties (person or group of persons). Typically, a fiduciary prudently takes care of money or other assets for another person. One party, for example, a corporate trust company or the trust department of a bank, acts in a fiduciary capacity to another party, who, for example, has entrusted funds to the fiduciary for safekeeping or investment. In a fiduciary relationship, one person, in a position of vulnerability, justifiably vests confidence, good faith, reliance, and trust in another whose aid, advice, or protection is sought in some matter.

\n
first party:
\n

The party who initiates a trust relationship, connection, or transaction with a second party.

\n
foundational identity:
\n

A set of identity data, such as a credential, issued by an authoritative source for the legal identity of the subject. Birth certificates, passports, driving licenses, and other forms of government ID documents are considered foundational identity documents. Foundational identities are often used to provide identity binding for functional identities.

\n
fourth party:
\n

A party that is not directly involved in the trust relationship between a first party and a second party, but provides supporting services exclusively to the first party (in contrast with a third party, who in most cases provides supporting services to the second party). In its strongest form, a fourth party has a fiduciary relationship with the first party.

\n
functional identity:
\n

A set of identity data, such as a credential, that is issued not for the purpose of establishing a foundational identity for the subject, but for the purpose of establishing other attributes, qualifications, or capabilities of the subject. Loyalty cards, library cards, and employee IDs are all examples of functional identities. Foundational identities are often used to provide identity binding for functional identities.

\n
gateway:
\n

A gateway is a piece of networking hardware or software used in telecommunications networks that allows data to flow from one discrete network to another. Gateways are distinct from routers or switches in that they communicate using more than one protocol to connect multiple networks[1][2] and can operate at any of the seven layers of the open systems interconnection model (OSI).

\n
GDPR:
\n

See: General Data Protection Regulation.

\n
General Data Protection Regulation:
\n

The General Data Protection Regulation (Regulation (EU) 2016/679, abbreviated GDPR) is a European Union regulation on information privacy in the European Union (EU) and the European Economic Area (EEA). The GDPR is an important component of EU privacy law and human rights law, in particular Article 8(1) of the Charter of Fundamental Rights of the European Union. It also governs the transfer of personal data outside the EU and EEA. The GDPR’s goals are to enhance individuals’ control and rights over their personal information and to simplify the regulations for international business.

\n
glossary:
\n

A glossary (from Ancient Greek: γλῶσσα, glossa; language, speech, wording), also known as a vocabulary or clavis, is an alphabetical list of terms in a particular domain of knowledge (scope) together with the definitions for those terms. Unlike a dictionary, a glossary has only one definition for each term.

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
Governance:
\n

Governance, risk management, and compliance (GRC) are three related facets that aim to assure an organization reliably achieves objectives, addresses uncertainty and acts with integrity. Governance is the combination of processes established and executed by the directors (or the board of directors) that are reflected in the organization's structure and how it is managed and led toward achieving goals. Risk management is predicting and managing risks that could hinder the organization from reliably achieving its objectives under uncertainty. Compliance refers to adhering with the mandated boundaries (laws and regulations) and voluntary boundaries (company’s policies, procedures, etc.)

\n
governance diamond:
\n

A term that refers to the addition of a governing body to the standard trust triangle of issuers, holders, and verifiers of credentials. The resulting combination of four parties represents the basic structure of a digital trust ecosystem.

\n
governance document:
\n

A document with at least one identifier that specifies governance requirements for a trust community.

\n
governance framework:
\n

A collection of one or more governance documents published by the governing body of a trust community.

\n
governance graph:
\n

A graph of the governance relationships between entities with a trust community. A governance graph shows which nodes are the governing bodies and which are the governed parties. In some cases, a governance graph can be traversed by making queries to one or more trust registries.Note: a party can play both roles and also be a participant in multiple governance frameworks.

\n
governance requirement:
\n

A requirement such as a policy, rule, or technical specification specified in a governance document.

\n
governed use case:
\n

A use case specified in a governance document that results in specific governance requirements within that governance framework. Governed use cases may optionally be discovered via a trust registry authorized by the relevant governance framework.

\n
governed party:
\n

A party whose role(s) in a trust community is governed by the governance requirements in a governance framework.

\n
governed party:
\n

A party whose role(s) in a trust community is governed by the governance requirements in a governance framework.

\n
governed information:
\n

Any information published under the authority of a governing body for the purpose of governing a trust community. This includes its governance framework and any information available via an authorized trust registry.

\n
governing authority:
\n

See: governing body.

\n
governing body:
\n

The party (or set of parties) authoritative for governing a trust community, usually (but not always) by developing, publishing, maintaining, and enforcing a governance framework. A governing body may be a government, a formal legal entity of any kind, an informal group of any kind, or an individual. A governing body may also delegate operational responsibilities to an administering body.

\n
GRC:
\n

See: Governance.

\n
guardian:
\n

A party that has been assigned rights and duties in a guardianship arrangement for the purpose of caring for, protecting, guarding, and defending the entity that is the dependent in that guardianship arrangement. In the context of decentralized digital trust infrastructure, a guardian is issued guardianship credentials into their own digital wallet in order to perform such actions on behalf of the dependent as are required by this role.

\n
guardianship arrangement:
\n

A guardianship arrangement (in a jurisdiction) is the specification of a set of rights and duties between legal entities of the jurisdiction that enforces these rights and duties, for the purpose of caring for, protecting, guarding, and defending one or more of these entities. At a minimum, the entities participating in a guardianship arrangement are the guardian and the dependent.

\n
guardianship credential:
\n

A digital credential issued by a governing body to a guardian to empower the guardian to undertake the rights and duties of a guardianship arrangement on behalf of a dependent.

\n
hardware security module:
\n

A physical computing device that provides tamper-evident and intrusion-resistant safeguarding and management of digital keys and other secrets, as well as crypto-processing.

\n
hash:
\n

The result of applying a hash function to a message.

\n
hash function:
\n

An algorithm that computes a numerical value (called the hash value) on a data file or electronic message that is used to represent that file or message, and depends on the entire contents of the file or message. A hash function can be considered to be a fingerprint of the file or message. Approved hash functions satisfy the following properties: one-way (it is computationally infeasible to find any input that maps to any pre-specified output); and collision resistant (it is computationally infeasible to find any two distinct inputs that map to the same output).

\n
holder (of a claim or credential):
\n

A role an agent performs by serving as the controller of the cryptographic keys and digital credentials in a digital wallet. The holder makes issuance requests for credentials and responds to presentation requests for credentials. A holder is usually, but not always, a subject of the credentials they are holding.

\n
holder binding:
\n

The process of creating and verifying a relationship between the holder of a digital wallet and the wallet itself. Holder binding is related to but NOT the same as subject binding.

\n
host:
\n

A host is any hardware device that has the capability of permitting access to a network via a user interface, specialized software, network address, protocol stack, or any other means. Some examples include, but are not limited to, computers, personal electronic devices, thin clients, and multi-functional devices.

\n
hourglass model:
\n

An architectural model for layered systems—and specifically for the protocol layers in a protocol stack—in which a diversity of supporting protocols and services at the lower layers are able to support a great diversity of protocols and applications at the higher layers through the use of a single protocol in the spanning layer in the middle—the “neck” of the hourglass.

\n
HSM:
\n

See: hardware security module.

\n
human auditability:
\n

See: human auditable.

\n
human auditable:
\n

A process or procedure whose compliance with the policies in a trust framework or governance framework can only be verified by a human performing an audit. Human auditability is a primary goal of the ToIP Governance Stack.

\n
human experience:
\n

The processes, patterns and rituals of acquiring knowledge or skill from doing, seeing, or feeling things as a natural person. In the context of decentralized digital trust infrastructure, the direct experience of a natural person using trust applications to make trust decisions within one or more digital trust ecosystems.

\n
human-readable:
\n

Information that can be processed by a human but that is not intended to be machine-readable.

\n
human trust:
\n

A level of assurance in a trust relationship that can be achieved only via human evaluation of applicable trust factors.

\n
IAL:
\n

See: identity assurance level.

\n
identification:
\n

The action of a party obtaining the set of identity data necessary to serve as that party’s identity for a specific entity.

\n
identifier:
\n

A single attribute—typically a character string—that uniquely identifies an entity within a specific context (which may be a global context). Examples include the name of a party the URL of an organization, or a serial number for a man-made thing.

\n
identity:
\n

A collection of attributes or other identity data that describe an entity and enable it to be distinguished from all other entities within a specific scope of identification. Identity attributes may include one or more identifiers for an entity, however it is possible to establish an identity without using identifiers.

\n
identity assurance level:
\n

A category that conveys the degree of confidence that a person’s claimed identity is their real identity, for example as defined in NIST SP 800-63-3 in terms of three levels: IAL 1 (Some confidence), IAL 2 (High confidence), IAL 3 (Very high confidence).

\n
identity binding:
\n

The process of associating a set of identity data, such as a credential, with its subject, such as a natural person. The strength of an identity binding is one factor in determining an authenticator assurance level.

\n
identity data:
\n

The set of data held by a party in order to provide an identity for a specific entity.

\n
identity document:
\n

A physical or digital document containing identity data. A credential is a specialized form of identity document. Birth certificates, bank statements, and utility bills can all be considered identity documents.

\n
identity proofing:
\n

The process of a party gathering sufficient identity data to establish an identity for a particular subject at a particular identity assurance level.

\n
identity provider:
\n

An identity provider (abbreviated IdP or IDP) is a system entity that creates, maintains, and manages identity information for principals and also provides authentication services to relying applications within a federation or distributed network.

\n
IDP:
\n

See: identity provider.

\n
impersonation:
\n

In the context of cybersecurity, impersonation is when an attacker pretends to be another person in order to commit fraud or some other digital crime.

\n
integrity (of a data structure):
\n

In IT security, data integrity means maintaining and assuring the accuracy and completeness of data over its entire lifecycle. This means that data cannot be modified in an unauthorized or undetected manner.

\n
intermediary system:
\n

A system that operates at ToIP Layer 2, the trust spanning layer of the ToIP stack, in order to route ToIP messages between endpoint systems. A supporting system is one of three types of systems defined in the ToIP Technology Architecture Specification.

\n
Internet Protocol:
\n

The Internet Protocol (IP) is the network layer communications protocol in the Internet protocol suite (also known as the TCP/IP suite) for relaying datagrams across network boundaries. Its routing function enables internetworking, and essentially establishes the Internet. IP has the task of delivering packets from the source host to the destination host solely based on the IP addresses in the packet headers. For this purpose, IP defines packet structures that encapsulate the data to be delivered. It also defines addressing methods that are used to label the datagram with source and destination information.

\n
Internet protocol suite:
\n

The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the set of communication protocols used in the Internet and similar computer networks according to functional criteria. The foundational protocols in the suite are the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP).

\n
IP:
\n

See: Internet Protocol.

\n
IP address:
\n

An Internet Protocol address (IP address) is a numerical label such as 192.0.2.1 that is connected to a computer network that uses the Internet Protocol for communication. An IP address serves two main functions: network interface identification, and location addressing.

\n
issuance:
\n

The action of an issuer producing and transmitting a digital credential to a holder. A holder may request issuance by submitting an issuance request.

\n
issuance request:
\n

A protocol request invoked by the holder of a digital wallet to obtain a digital credential from an issuer.

\n
issuer (of a claim or credential):
\n

A role an agent performs to package and digitally sign a set of claims, typically in the form of a digital credential, and transmit them to a holder.

\n
jurisdiction:
\n

The composition of: a) a legal system (legislation, enforcement thereof, and conflict resolution), b) a party that governs that legal system, c) a scope within which that legal system is operational, and d) one or more objectives for the purpose of which the legal system is operated.

\n
KATE:
\n

See: keys-at-the-edge.

\n
KERI:
\n

See: Key Event Receipt Infrastructure.

\n
key:
\n

See: cryptographic key.

\n
key establishment:
\n

A process that results in the sharing of a key between two or more entities, either by transporting a key from one entity to another (key transport) or generating a key from information shared by the entities (key agreement).

\n
key event:
\n

An event in the history of the usage of a cryptographic key pair. There are multiple types of key events. The inception event is when the key pair is first generated. A rotation event is when the key pair is changed to a new key pair. In some key management systems (such as KERI), key events are tracked in a key event log.

\n
key event log:
\n

An ordered sequence of records of key events.

\n
Key Event Receipt Infrastructure:
\n

A decentralized permissionless key management architecture.

\n
key management system:
\n

A system for the management of cryptographic keys and their metadata (e.g., generation, distribution, storage, backup, archive, recovery, use, revocation, and destruction). An automated key management system may be used to oversee, automate, and secure the key management process. A key management is often protected by implementing it within the trusted execution environment (TEE) of a device. An example is the Secure Enclave on Apple iOS devices.

\n
keys-at-the-edge:
\n

A key management architecture in which keys are stored on a user’s local edge devices, such as a smartphone, tablet, or laptop, and then used in conjunction with a secure protocol to unlock a key management system (KMS) and/or a digital vault in the cloud. This approach can enable the storage and sharing of large data structures that are not feasible on edge devices. This architecture can also be used in conjunction with confidential computing to enable cloud-based digital agents to safely carry out “user not present” operations.

\n
KMS:
\n

See: key management system.

\n
knowledge:
\n

The (intangible) sum of what is known by a specific party, as well as the familiarity, awareness or understanding of someone or something by that party.

\n
Laws of Identity:
\n

A set of seven “laws” written by Kim Cameron, former Chief Identity Architect of Microsoft (1941-2021), to describe the dynamics that cause digital identity systems to succeed or fail in various contexts. His goal was to define the requirements for a unifying identity metasystem that can offer the Internet the identity layer it needs.

\n
Layer 1:
\n

See: ToIP Layer 1.

\n
Layer 2:
\n

See: ToIP Layer 2.

\n
Layer 3:
\n

See: ToIP Layer 3.

\n
Layer 4:
\n

See: ToIP Layer 4.

\n
legal entity:
\n

An entity that is not a natural person but is recognized as having legal rights and responsibilities. Examples include corporations, partnerships, sole proprietorships, non-profit organizations, associations, and governments. (In some cases even natural systems such as rivers are treated as legal entities.)

\n
Legal Entity Identifier:
\n

The Legal Entity Identifier (LEI) is a unique global identifier for legal entities participating in financial transactions. Also known as an LEI code or LEI number, its purpose is to help identify legal entities on a globally accessible database. Legal entities are organisations such as companies or government entities that participate in financial transactions.

\n
legal identity:
\n

A set of identity data considered authoritative to identify a party for purposes of legal accountability under one or more jurisdictions.

\n
legal person:
\n

In law, a legal person is any person or ‘thing’ that can do the things a human person is usually able to do in law – such as enter into contracts, sue and be sued, own property, and so on.[3][4][5] The reason for the term “legal person” is that some legal persons are not people: companies and corporations are “persons” legally speaking (they can legally do most of the things an ordinary person can do), but they are not people in a literal sense (human beings).

\n
legal system:
\n

A system in which policies and rules are defined, and mechanisms for their enforcement and conflict resolution are (implicitly or explicitly) specified. Legal systems are not just defined by governments; they can also be defined by a governance framework.

\n
LEI:
\n

See: Legal Entity Identifier.

\n
level of assurance:
\n

See: assurance level.

\n
liveness detection:
\n

Any technique used to detect a presentation attack by determining whether the source of a biometric sample is a live human being or a fake representation. This is typically accomplished using algorithms that analyze biometric sensor data to detect whether the source is live or reproduced.

\n
locus of control:
\n

The set of computing systems under a party’s direct control, where messages and data do not cross trust boundaries.

\n
machine-readable:
\n

Information written in a computer language or expression language so that it can be read and processed by a computing device.

\n
man-made thing:
\n

Athing generated by human activity of some kind. Man-made things include both active things, such as cars or drones, and passive things, such as chairs or trousers.

\n
mandatory:
\n

A requirement that must be implemented in order for an implementer to be in compliance. In ToIP governance frameworks, a mandatory requirement is expressed using a MUST or REQUIRED keyword as defined in IETF RFC 2119.

\n
metadata:
\n

Information describing the characteristics of data including, for example, structural metadata describing data structures (e.g., data format, syntax, and semantics) and descriptive metadata describing data contents (e.g., information security labels).

\n
message:
\n

A discrete unit of communication intended by the source for consumption by some recipient or group of recipients.

\n
mobile deep link:
\n

In the context of mobile apps, deep linking consists of using a uniform resource identifier (URI) that links to a specific location within a mobile app rather than simply launching the app. Deferred deep linking allows users to deep link to content even if the app is not already installed. Depending on the mobile device platform, the URI required to trigger the app may be different.

\n
MPC:
\n

See: multi-party computation.

\n
multicast:
\n

In computer networking, multicast is group communication where data transmission is addressed (using a multicast address) to a group of destination computers simultaneously. Multicast can be one-to-many or many-to-many distribution. Multicast should not be confused with physical layer point-to-multipoint communication.

\n
multicast address:
\n

A multicast address is a logical identifier for a group of hosts in a computer network that are available to process datagrams or frames intended to be multicast for a designated network service.

\n
multi-party computation:
\n

Secure multi-party computation (also known as secure computation, multi-party computation (MPC) or privacy-preserving computation) is a subfield of cryptography with the goal of creating methods for parties to jointly compute a function over their inputs while keeping those inputs private. Unlike traditional cryptographic tasks, where cryptography assures security and integrity of communication or storage and the adversary is outside the system of participants (an eavesdropper on the sender and receiver), the cryptography in this model protects participants’ privacy from each other.

\n
multi-party control:
\n

A variant of multi-party computation where multiple parties must act in concert to meet a control requirement without revealing each other’s data. All parties are privy to the output of the control, but no party learns anything about the others.

\n
multi-signature:
\n

A cryptographic signature scheme where the process of signing information (e.g., a transaction) is distributed among multiple private keys.

\n
natural person:
\n

A person (in legal meaning, i.e., one who has its own legal personality) that is an individual human being, distinguished from the broader category of a legal person, which may be a private (i.e., business entity or non-governmental organization) or public (i.e., government) organization.

\n
natural thing:
\n

A thing that exists in the natural world independently of humans. Although natural things may form part of a man-made thing, natural things are mutually exclusive with man-made things.

\n
network address:
\n

A network address is an identifier for a node or host on a telecommunications network. Network addresses are designed to be unique identifiers across the network, although some networks allow for local, private addresses, or locally administered addresses that may not be unique. Special network addresses are allocated as broadcast or multicast addresses. A network address designed to address a single device is called a unicast address.

\n
node:
\n

In telecommunications networks, a node (Latin: nodus, ‘knot’) is either a redistribution point or a communication endpoint. The definition of a node depends on the network and protocol layer referred to. A physical network node is an electronic device that is attached to a network, and is capable of creating, receiving, or transmitting information over a communication channel.

\n
non-custodial wallet:
\n

A digital wallet that is directly in the control of the holder, usually because the holder is the device controller of the device hosting the digital wallet (smartcard, smartphone, tablet, laptop, desktop, car, etc.) A digital wallet that is in the custody of a third party is called a custodial wallet.

\n
objective:
\n

Something toward which a party (its owner) directs effort (an aim, goal, or end of action).

\n
OOBI:
\n

See: out-of-band introduction.

\n
OpenWallet Foundation:
\n

A non-profit project of the Linux Foundation chartered to build a world-class open source wallet engine.

\n
operational circumstances:
\n

In the context of privacy protection, this term denotes the context in which privacy trade-off decisions are made. It includes the regulatory environment and other non-technical factors that bear on what reasonable privacy expectations might be.

\n
optional:
\n

A requirement that is not mandatory or recommended to implement in order for an implementer to be in compliance, but which is left to the implementer’s choice. In ToIP governance frameworks, an optional requirement is expressed using a MAY or OPTIONAL keyword as defined in IETF RFC 2119.

\n
organization:
\n

A party that consists of a group of parties who agree to be organized into a specific form in order to better achieve a common set of objectives. Examples include corporations, partnerships, sole proprietorships, non-profit organizations, associations, and governments.

\n
organizational authority:
\n

A type of authority where the party asserting its right is an organization.

\n
out-of-band introduction
\n

A process by which two or more entities exchange VIDs in order to form a cryptographically verifiable connection (e.g., a ToIP connection), such as by scanning a QR code (in person or remotely) or clicking a deep link.

\n
out-of-band introduction
\n

A process by which two or more entities exchange VIDs in order to form a cryptographically verifiable connection (e.g., a ToIP connection), such as by scanning a QR code (in person or remotely) or clicking a deep link.

\n
owner (of an entity):
\n

The role that a party performs when it is exercising its legal, rightful or natural title to control a specific entity.

\n
P2P:
\n

See: peer-to-peer.

\n
party:
\n

An entity that sets its objectives, maintains its knowledge, and uses that knowledge to pursue its objectives in an autonomous (sovereign) manner. Humans and organizations are the typical examples.

\n
password:
\n

A string of characters (letters, numbers and other symbols) that are used to authenticate an identity, verify access authorization or derive cryptographic keys.

\n
peer:
\n

In the context of digital networks, an actor on the network that has the same status, privileges, and communications options as the other actors on the network.

\n
peer-to-peer:
\n

Peer-to-peer (P2P) computing or networking is a distributed application architecture that partitions tasks or workloads between peers. Peers are equally privileged, equipotent participants in the network. This forms a peer-to-peer network of nodes.

\n
permission
\n

Authorization to perform some action on a system.

\n
persistent connection:
\n

A connection that is able to persist across multiple communication sessions. In a ToIP context, a persistent connection is established when two ToIP endpoints exchange verifiable identifiers that they can use to re-establish the connection with each other whenever it is needed.

\n
personal data:
\n

Any information relating to an identified or identifiable natural person (called a data subject under GDPR).

\n
personal data store:
\n

See: personal data vault.

\n
personal data vault:
\n

A digital vault whose controller is a natural person.

\n
personal wallet:
\n

A digital wallet whose holder is a natural person.

\n
personally identifiable information:
\n

Information (any form of data) that can be used to directly or indirectly identify or re-identify an individual person either singly or in combination within a single record or in correlation with other records. This information can be one or more attributes/fields/properties in a record (e.g., date-of-birth) or one or more records (e.g., medical records).

\n
physical credential:
\n

A credential in a physical form such as paper, plastic, or metal.

\n
PII:
\n

See: personally identifiable information.

\n
PKI:
\n

See: public key infrastructure.

\n
plaintext:
\n

Unencrypted information that may be input to an encryption operation. Once encrypted, it becomes ciphertext.

\n
policy
\n

Statements, rules or assertions that specify the correct or expected behavior of an entity.

\n
PoP:
\n

See: proof of personhood.

\n
presentation:
\n

A verifiable message that a holder may send to a verifier containing proofs of one or more claims derived from one or more digital credentials from one or more issuers as a response to a specific presentation request from a  verifier.

\n
presentation attack:
\n

A type of cybersecurity attack in which the attacker attempts to defeat a biometric liveness detection system by providing false inputs.

\n
presentation request:
\n

A protocol request sent by the verifier to the holder of a digital wallet to request a presentation.

\n
primary document:
\n

The governance document at the root of a governance framework. The primary document specifies the other controlled documents in the governance framework.

\n
principal:
\n

The party for whom, or on behalf of whom, an actor is executing an action (this actor is then called an agent of that party).

\n
Principles of SSI:
\n

A set of principles for self-sovereign identity systems originally defined by the Sovrin Foundation and republished by the ToIP Foundation.

\n
privacy policy:
\n

A statement or legal document (in privacy law) that discloses some or all of the ways a party gathers, uses, discloses, and manages a customer or client’s data.

\n
private key:
\n

In public key cryptography, the cryptographic key which must be kept secret by the controller in order to maintain security.

\n
proof:
\n

A digital object that enables cryptographic verification of either: a) the claims from one or more digital credentials, or b) facts about claims that do not reveal the data itself (e.g., proof of the subject being over/under a specific age without revealing a birthdate).

\n
proof of control:
\n

See: proof of possession.

\n
proof of personhood:
\n

Proof of personhood (PoP) is a means of resisting malicious attacks on peer-to-peer networks, particularly, attacks that utilize multiple fake identities, otherwise known as a Sybil attack. Decentralized online platforms are particularly vulnerable to such attacks by their very nature, as notionally democratic and responsive to large voting blocks. In PoP, each unique human participant obtains one equal unit of voting power, and any associated rewards.

\n
proof of possession:
\n

A verification process whereby a level of assurance is obtained that the owner of a key pair actually controls the private key associated with the public key.

\n
proof of presence:
\n

See: liveness detection.

\n
property:
\n

In the context of digital communication, an attribute of a digital object or data structure, such as a DID document or a schema.

\n
protected data:
\n

Data that is not publicly available but requires some type of access control to gain access.

\n
protocol layer:
\n

In modern protocol design, protocols are layered to form a protocol stack. Layering is a design principle that divides the protocol design task into smaller steps, each of which accomplishes a specific part, interacting with the other parts of the protocol only in a small number of well-defined ways. Layering allows the parts of a protocol to be designed and tested without a combinatorial explosion of cases, keeping each design relatively simple.

\n
protocol stack:
\n

The protocol stack or network stack is an implementation of a computer networking protocol suite or protocol family. Some of these terms are used interchangeably but strictly speaking, the suite is the definition of the communication protocols, and the stack is the software implementation of them.

\n
pseudonym:
\n

A pseudonym is a fictitious name that a person assumes for a particular purpose, which differs from their original or true name (orthonym). This also differs from a new name that entirely or legally replaces an individual’s own. Many pseudonym holders use pseudonyms because they wish to remain anonymous, but anonymity is difficult to achieve and often fraught with legal issues.

\n
public key:
\n

Drummond Reed: In public key cryptography, the cryptographic key that can be freely shared with anyone by the controller without compromising security. A party’s public key must be verified as authoritative in order to verify their digital signature.

\n
public key certificate:
\n

A set of data that uniquely identifies a public key (which has a corresponding private key) and an owner that is authorized to use the key pair. The certificate contains the owner’s public key and possibly other information and is digitally signed by a certification authority (i.e., a trusted party), thereby binding the public key to the owner.

\n
public key cryptography:
\n

Public key cryptography, or asymmetric cryptography, is the field of cryptographic systems that use pairs of related keys. Each key pair consists of a public key and a corresponding private key. Key pairs are generated with cryptographic algorithms based on mathematical problems termed one-way functions. Security of public key cryptography depends on keeping the private key secret; the public key can be openly distributed without compromising security.

\n
public key infrastructure:
\n

A set of policies, processes, server platforms, software and workstations used for the purpose of administering certificates and public-private key pairs, including the ability to issue, maintain, and revoke public key certificates. The PKI includes the hierarchy of certificate authorities that allow for the deployment of digital certificates that support encryption, digital signature and authentication to meet business and security requirements.

\n
QR code:
\n

A QR code (short for “quick-response code”) is a type of two-dimensional matrix barcode—a machine-readable optical image that contains information specific to the identified item. In practice, QR codes contain data for a locator, an identifier, and web tracking.

\n
RBAC:
\n

See: role-based access control.

\n
real world identity
\n

A term used to describe the opposite of digital identity, i.e., an identity (typically for a person) in the physical instead of the digital world.

\n
recommended:
\n

A requirement that is not mandatory to implement in order for an implementer to be in compliance, but which should be implemented unless the implementer has a good reason. In ToIP governance frameworks, a recommendation is expressed using a SHOULD or RECOMMENDED keyword as defined in IETF RFC 2119.

\n
record:
\n

A uniquely identifiable entry or listing in a database or registry.

\n
registrant:
\n

The party submitting a registration record to a registry.

\n
registrar:
\n

The party who performs registration on behalf of a registrant.

\n
registration:
\n

The process by which a registrant submits a record to a registry.

\n
registry:
\n

A specialized database of records that serves as an authoritative source of information about entities.

\n
relationship context:
\n

A context established within the boundary of a trust relationship.

\n
relying party:
\n

A party who consumes claims or trust graphs from other parties (such as issuers, holders, and trust registries) in order to make a trust decision.

\n
reputation:
\n

The reputation or prestige of a social entity (a person, a social group, an organization, or a place) is an opinion about that entity – typically developed as a result of social evaluation on a set of criteria, such as behavior or performance.

\n
reputation graph:
\n

A graph of the reputation relationships between different entities in a trust community. In a digital trust ecosystem, the governing body may be one trust root of a reputation graph. In some cases, a reputation graph can be traversed by making queries to one or more trust registries.

\n
reputation system:
\n

Reputation systems are programs or algorithms that allow users to rate each other in online communities in order to build trust through reputation. Some common uses of these systems can be found on e-commerce websites such as eBay, Amazon.com, and Etsy as well as online advice communities such as Stack Exchange.

\n
requirement:
\n

A specified condition or behavior to which a system needs to comply. Technical requirements are defined in technical specifications and implemented in computer systems to be executed by software actors. Governance requirements are defined in governance documents that specify policies and procedures to be executed by human actors. In ToIP architecture, requirements are expressed using the keywords defined in Internet RFC 2119.

\n
requirement:
\n

A specified condition or behavior to which a system needs to comply. Technical requirements are defined in technical specifications and implemented in computer systems to be executed by software actors. Governance requirements are defined in governance documents that specify policies and procedures to be executed by human actors. In ToIP architecture, requirements are expressed using the keywords defined in Internet RFC 2119.

\n
revocation:
\n

In the context of digital credentials, revocation is an event signifying that the issuer no longer attests to the validity of a credential they have issued. In the context of cryptographic keys, revocation is an event signifying that the controller no longer attests to the validity of a public/private key pair for which the controller is authoritative.

\n
risk:
\n

The effects that uncertainty (i.e. a lack of information, understanding or knowledge of events, their consequences or likelihoods) can have on the intended realization of an objectiveof a party.

\n
risk assessment:
\n

The process of identifying risks to organizational operations (including mission, functions, image, reputation), organizational assets, individuals, other organizations, and the overall ecosystem, resulting from the operation of an information system. Risk assessment is part of risk management, incorporates threat and vulnerability analyses, and considers risk mitigations provided by security controls planned or in place.

\n
risk decision:
\n

See: trust decision.

\n
risk management:
\n

The process of managing risks to organizational operations (including mission, functions, image, or reputation), organizational assets, or individuals resulting from the operation of an information system, and includes: (i) the conduct of a risk assessment; (ii) the implementation of a risk mitigation strategy; and (iii) employment of techniques and procedures for the continuous monitoring of the security state of the information system.

\n
risk mitigation:
\n

Prioritizing, evaluating, and implementing the appropriate risk-reducing controls/countermeasures recommended from the risk management process.

\n
role:
\n

A defined set of characteristics that an entity has in some context, such as responsibilities it may have, actions (behaviors) it may execute, or pieces of knowledge that it is expected to have in that context, which are referenced by a specific role name.

\n
role-based access control:
\n

Access control based on user roles (i.e., a collection of access authorizations a user receives based on an explicit or implicit assumption of a given role). Role permissions may be inherited through a role hierarchy and typically reflect the permissions needed to perform defined functions within an organization. A given role may apply to a single individual or to several individuals.

\n
role credential:
\n

A credential claiming that the subject has a specific role.

\n
router:
\n

A router is a networking device that forwards data packets between computer networks. Routers perform the traffic directing functions between networks and on the global Internet. Data sent through a network, such as a web page or email, is in the form of data packets. A packet is typically forwarded from one router to another router through the networks that constitute an internetwork (e.g. the Internet) until it reaches its destination node. This process is called routing.

\n
routing:
\n

Routing is the process of selecting a path for traffic in a network or between or across multiple networks. Broadly, routing is performed in many types of networks, including circuit-switched networks, such as the public switched telephone network (PSTN), and computer networks, such as the Internet. A router is a computing device that specializes in performing routing.

\n
rule:
\n

A prescribed guide for conduct, process or action to achieve a defined result or objective. Rules may be human-readable or machine-readable or both.

\n
RWI:
\n

See: real world identity.

\n
schema:
\n

A framework, pattern, or set of rules for enforcing a specific structure on a digital object or a set of digital data. There are many types of schemas, e.g., data schema, credential verification schema, database schema.

\n
scope:
\n

In the context of terminology, scope refers to the set of possible concepts within which: a) a specific term is intended to uniquely identify a concept, or b) a specific glossary is intended to identify a set of concepts. In the context of identification, scope refers to the set of possible entities within which a specific entity must be uniquely identified. In the context of specifications, scope refers to the set of problems (the problem space) within which the specification is intended to specify solutions.

\n
SCID:
\n

See: self-certifying identifier.

\n
second party:
\n

The party with whom a first party engages to form a trust relationship, establish a connection, or execute a transaction.

\n
Secure Enclave:
\n

A coprocessor on Apple iOS devices that serves as a trusted execution environment.

\n
secure multi-party computation:
\n

See: multi-party computation.

\n
Secure Sockets Layer:
\n

The original transport layer security protocol developed by Netscape and partners. Now deprecated in favor of Transport Layer Security (TLS).

\n
security domain:
\n

An environment or context that includes a set of system resources and a set of system entities that have the right to access the resources as defined by a common security policy, security model, or security architecture.

\n
security policy:
\n

A set of policies and rules that governs all aspects of security-relevant system and system element behavior.

\n
self-asserted:
\n

A term used to describe a claim or a credential whose subject is also the issuer.

\n
self-certified:
\n

When a party provides its own certification that it is compliant with a set of requirements, such as a governance framework.

\n
self-certifying identifier
\n

A subclass of verifiable identifier that is cryptographically verifiable without the need to rely on any third party for verification because the identifier is cryptographically bound to the cryptographic keys from which it was generated.\n~ Also known as: autonomous identifier.

\n
self-certifying identifier
\n

A subclass of verifiable identifier that is cryptographically verifiable without the need to rely on any third party for verification because the identifier is cryptographically bound to the cryptographic keys from which it was generated.\n~ Also known as: autonomous identifier.

\n
self-sovereign identity:
\n

A decentralized identity architecture that implements the Principles of SSI.

\n
sensitive data:
\n

Personal data that a reasonable person would view from a privacy protection standpoint as requiring special care above and beyond other personal data.

\n
session:
\n

See: communication session.

\n
sociotechnical system:
\n

An approach to complex organizational work design that recognizes the interaction between people and technology in workplaces. The term also refers to coherent systems of human relations, technical objects, and cybernetic processes that inhere to large, complex infrastructures. Social society, and its constituent substructures, qualify as complex sociotechnical systems.

\n
software agent:
\n

In computer science, a software agent is a computer program that acts for a user or other program in a relationship of agency, which derives from the Latin agere (to do): an agreement to act on one’s behalf. A user agent is a specific type of software agent that is used directly by an end-user as the principal.

\n
Sovrin Foundation:
\n

A 501 ©(4) nonprofit organization established to administer the governance framework governing the Sovrin Network, a public service utility enabling self-sovereign identity on the internet. The Sovrin Foundation is an independent organization that is responsible for ensuring the Sovrin identity system is public and globally accessible.

\n
spanning layer:
\n

A specific layer within a protocol stack that consists of a single protocol explicitly designed to provide interoperability between the protocols layers above it and below it.

\n
specification:
\n

See: technical specification.

\n
SSI:
\n

See: self-sovereign identity.

\n
SSL:
\n

See: Secure Sockets Layer.

\n
stream:
\n

In the context of digital communications, and in particular streaming media, a flow of data delivered in a continuous manner from a server to a client rather than in discrete messages.

\n
streaming media:
\n

Streaming media is multimedia for playback using an offline or online media player. Technically, the stream is delivered and consumed in a continuous manner from a client, with little or no intermediate storage in network elements. Streaming refers to the delivery method of content, rather than the content itself.

\n
subject:
\n

The entity described by one or more claims, particularly in the context of digital credentials.

\n
subscription:
\n

In the context of decentralized digital trust infrastructure, a subscription is an agreement between a first digital agent—the publisher—to automatically send a second digital agent—the subscriber—a message when a specific type of event happens in the wallet or vault managed by the first digital agent.

\n
supporting system:
\n

A system that operates at ToIP Layer 1, the trust support layer of the ToIP stack. A supporting system is one of three types of systems defined in the ToIP Technology Architecture Specification.

\n
Sybil attack:
\n

A Sybil attack is a type of attack on a computer network service in which an attacker subverts the service’s reputation system by creating a large number of pseudonymous identities and uses them to gain a disproportionately large influence. It is named after the subject of the book Sybil, a case study of a woman diagnosed with dissociative identity disorder.

\n
system of record:
\n

A system of record (SOR) or source system of record (SSoR) is a data management term for an information storage system (commonly implemented on a computer system running a database management system) that is the authoritative data source for a given data element or piece of information.

\n
tamper resistant:
\n

A process which makes alterations to the data difficult (hard to perform), costly (expensive to perform), or both.

\n
TCP:
\n

See: Transmission Control Protocol.

\n
TCP/IP:
\n

See: Internet Protocol Suite.

\n
TCP/IP stack:
\n

The protocol stack implementing the TCP/IP suite.

\n
technical requirement:
\n

A requirement for a hardware or software component or system. In the context of decentralized digital trust infrastructure, technical requirements are a subset of governance requirements. Technical requirements are often specified in a technical specification.

\n
technical specification:
\n

A document that specifies, in a complete, precise, verifiable manner, the requirements, design, behavior, or other characteristics of a system or component and often the procedures for determining whether these provisions have been satisfied.

\n
technical trust:
\n

A level of assurance in a trust relationship that can be achieved only via technical means such as hardware, software, network protocols, and cryptography. Cryptographic trust is a specialized type of technical trust.

\n
TEE:
\n

See: trusted execution environment.

\n
term:
\n

A unit of text (i.e., a word or phrase) that is used in a particular context or scope to refer to a concept (or a relation between concepts, or a property of a concept).

\n
terminology:
\n

Terminology is a group of specialized words and respective meanings in a particular field, and also the study of such terms and their use; the latter meaning is also known as terminology science. A term is a word, compound word, or multi-word expressions that in specific contexts is given specific meanings—these may deviate from the meanings the same words have in other contexts and in everyday language.[2] Terminology is a discipline that studies, among other things, the development of such terms and their interrelationships within a specialized domain. Terminology differs from lexicography, as it involves the study of concepts, conceptual systems and their labels (terms), whereas lexicography studies words and their meanings.

\n
terms community:
\n

A group of parties who share the need for a common terminology.

\n
terms wiki:
\n

A wiki website used by a terms community to input, maintain, and publish its terminology. The ToIP Foundation Concepts and Terminology Working Group has established a simple template for GitHub-based terms wikis.

\n
thing:
\n

An entity that is neither a natural person nor an organization and thus cannot be a party. A thing may be a natural thing or a man-made thing.

\n
third party:
\n

A party that is not directly involved in the trust relationship between a first party and a second party, but provides supporting services to either or both of them.

\n
three party model:
\n

The issuer—holder—verifier model used by all types of physical credentials and digital credentials to enable transitive trust decisions.

\n
timestamp:
\n

A token or packet of information that is used to provide assurance of timeliness; the timestamp contains timestamped data, including a time, and a signature generated by a trusted timestamp authority (TTA).

\n
TLS:
\n

See: Transport Layer Security.

\n
ToIP:
\n

See: Trust Over IP

\n
ToIP application:
\n

A trust application that runs at ToIP Layer 4, the trust application layer.

\n
ToIP channel:
\n

See: VID relationship.

\n
ToIP communication:
\n

Communication that uses the ToIP stack to deliver ToIP messages between ToIP endpoints, optionally using ToIP intermediaries, to provide authenticity, confidentiality, and correlation privacy.

\n
ToIP connection:
\n

A connection formed using the ToIP Trust Spanning Protocol between two ToIP endpoints identified with verifiable identifiers. A ToIP connection is instantiated as one or more VID relationships.

\n
ToIP controller:
\n

The controller of a ToIP identifier.

\n
ToIP Foundation:
\n

A non-profit project of the Linux Foundation chartered to define an overall architecture for decentralized digital trust infrastructure known as the ToIP stack.

\n
ToIP endpoint:
\n

An endpoint that communicates via the ToIP Trust Spanning Protocol as described in the ToIP Technology Architecture Specification.

\n
ToIP Governance Architecture Specification:
\n

The specification defining the requirements for the ToIP Governance Stack published by the ToIP Foundation.

\n
ToIP governance framework:
\n

A governance framework that conforms to the requirements of the ToIP Governance Architecture Specification.

\n
ToIP Governance Metamodel:
\n

A structural model for ToIP governance frameworks that specifies the recommended governance documents that should be included depending on the objectives of the trust community.

\n
ToIP Governance Stack:
\n

The governance half of the four layer ToIP stack as defined by the ToIP Governance Architecture Specification.

\n
ToIP identifier:
\n

A verifiable identifier for an entity that is addressable using the ToIP stack.

\n
ToIP intermediary:
\n

See: intermediary system.

\n
ToIP layer:
\n

One of four protocol layers in the ToIP stack. The four layers are ToIP Layer 1, ToIP Layer 2, ToIP Layer 3, and ToIP Layer 4.

\n
ToIP Layer 1:
\n

The trust support layer of the ToIP stack, responsible for supporting the trust spanning protocol at ToIP Layer 2.

\n
ToIP Layer 2:
\n

The trust spanning layer of the ToIP stack, responsible for enabling the trust task protocols at ToIP Layer 3.

\n
ToIP Layer 3:
\n

The trust task layer of the ToIP stack, responsible for enabling trust applications at ToIP Layer 4.

\n
ToIP Layer 4:
\n

The trust application layer of the ToIP stack, where end users have the direct human experience of using applications that call trust task protocols to engage in trust relationships and make trust decisions using ToIP decentralized digital trust infrastructure.

\n
ToIP message:
\n

A message communicated between ToIP endpoints using the ToIP stack.

\n
ToIP specification:
\n

A specification published by the ToIP Foundation. Specifications may be in one of three states: Draft Deliverable, Working Group Approved Deliverable, or ToIP Approved Deliverables

\n
ToIP stack:
\n

The layered architecture for decentralized digital trust infrastructure defined by the ToIP Foundation. The ToIP stack is a dual stack consisting of two halves: the ToIP Technology Stack and the ToIP Governance Stack. The four layers in the ToIP stack are ToIP Layer 1, ToIP Layer 2, ToIP Layer 3, and ToIP Layer 4.

\n
ToIP system:
\n

A computing system that participates in the ToIP Technology Stack. There are three types of ToIP systems: endpoint systems, intermediary systems, and supporting systems.

\n
ToIP trust network:
\n

A trust network implemented using the ToIP stack.

\n
ToIP Technology Architecture Specification:
\n

The technical specification defining the requirements for the ToIP Technology Stack published by the ToIP Foundation.

\n
ToIP Technology Stack:
\n

The technology half of the four layer ToIP stack as defined by the ToIP Technology Architecture Specification.

\n
ToIP trust community:
\n

A trust community governed by a ToIP governance framework.

\n
ToIP Trust Registry Protocol:
\n

The open standard trust task protocol defined by the ToIP Foundation to perform the trust task of querying a trust registry. The ToIP Trust Registry Protocol operates at Layer 3 of the ToIP stack.

\n
ToIP Trust Spanning Protocol:
\n

The ToIP Layer 2 protocol for verifiable messaging that implements the trust spanning layer of the ToIP stack.  The ToIP Trust Spanning Protocol enables actors in different digital trust domains to interact in a similar way to how the Internet Protocol (IP) enables devices on different local area networks to exchange data.

\n
transaction:
\n

A discrete event between a user and a system that supports a business or programmatic purpose. A digital system may have multiple categories or types of transactions, which may require separate analysis within the overall digital identity risk assessment.

\n
transitive trust decision:
\n

A trust decision made by a first party about a second party or another entity based on information about the second party or the other entity that is obtained from one or more third parties.

\n
Transmission Control Protocol:
\n

The Transmission Control Protocol (TCP) is one of the main protocols of the Internet protocol suite. It originated in the initial network implementation in which it complemented the Internet Protocol (IP). Therefore, the entire suite is commonly referred to as TCP/IP. TCP provides reliable, ordered, and error-checked delivery of a stream of octets (bytes) between applications running on hosts communicating via an IP network. Major internet applications such as the World Wide Web, email, remote administration, and file transfer rely on TCP, which is part of the Transport Layer of the TCP/IP suite. SSL/TLS often runs on top of TCP.

\n
Transport Layer Security:
\n

Transport Layer Security (TLS) is a cryptographic protocol designed to provide communications security over a computer network. The protocol is widely used in applications such as email, instant messaging, and Voice over IP, but its use in securing HTTPS remains the most publicly visible. The TLS protocol aims primarily to provide security, including privacy (confidentiality), integrity, and authenticity through the use of cryptography, such as the use of certificates, between two or more communicating computer applications.

\n
tribal knowledge:
\n

Knowledge that is known within an “in-group” of people but unknown outside of it. A tribe, in this sense, is a group of people that share such a common knowledge.

\n
trust:
\n

A belief that an entity will behave in a predictable manner in specified circumstances. The entity may be a person, process, object or any combination of such components. The entity can be of any size from a single hardware component or software module, to a piece of equipment identified by make and model, to a site or location, to an organization, to a nation-state. Trust, while inherently a subjective determination, can be based on objective evidence and subjective elements. The objective grounds for trust can include for example, the results of information technology product testing and evaluation. Subjective belief, level of comfort, and experience may supplement (or even replace) objective evidence, or substitute for such evidence when it is unavailable. Trust is usually relative to a specific circumstance or situation (e.g., the amount of money involved in a transaction, the sensitivity or criticality of information, or whether safety is an issue with human lives at stake). Trust is generally not transitive (e.g., you trust a friend but not necessarily a friend of a friend). Finally, trust is generally earned, based on experience or measurement.

\n
trust anchor:
\n

See: trust root.

\n
trust application:
\n

An application that runs at ToIP Layer 4 in order to perform trust tasks or engage in other verifiable messaging using the ToIP stack.

\n
trust application layer:
\n

In the context of the ToIP stack, the trust application layer is ToIP Layer 4. Applications running at this layer call trust task protocols at ToIP Layer 3.

\n
trust assurance:
\n

A process that provides a level of assurance sufficient to make a particular trust decision.

\n
trust basis:
\n

The properties of a verifiable identifier or a ToIP system that enable a party to appraise it to determine a trust limit.

\n
trust boundary:
\n

The border of a trust domain.

\n
trust chain:
\n

A set of cryptographically verifiable links between digital credentials or other data containers that enable transitive trust decisions.

\n
trust community:
\n

A set of parties who collaborate to achieve a mutual set of trust objectives.

\n
trust community:
\n

A set of parties who collaborate to achieve a mutual set of trust objectives.

\n
trust context:
\n

The context in which a specific party makes a specific trust decision. Many different factors may be involved in establishing a trust context, such as: the relevant interaction or transaction; the presence or absence of existing trust relationships; the applicability of one or more governance frameworks; and the location, time, network, and/or devices involved. A trust context may be implicit or explicit; if explicit, it may be identified using an identifier. A ToIP governance framework an example of an explicit trust context identified by a ToIP identifier.

\n
trust decision:
\n

A decision that a party needs to make about whether to engage in a specific interaction or transaction with another entity that involves real or perceived risks.

\n
trust domain:
\n

A security domain defined by a computer hardware or software architecture, a security policy, or a trust community, typically via a trust framework or governance framework.

\n
trust ecosystem:
\n

See digital trust ecosystem.

\n
trust establishment:
\n

The process two or more parties go through to establish a trust relationship. In the context of decentralized digital trust infrastructure, trust establishment takes place at two levels. At the technical trust level, it includes some form of key establishment. At the human trust level, it may be accomplished via an out-of-band introduction, the exchange of digital credentials, queries to one or more trust registries, or evaluation of some combination of human-readable and machine-readable governance frameworks.

\n
trust framework:
\n

A term (most frequently used in the digital identity industry) to describe a governance framework for a digital identity system, especially a federation.

\n
trust graph:
\n

A data structure describing the trust relationship between two or more entities. A simple trust graph may be expressed as a trust list. More complex trust graphs can be recorded or registered in and queried from a trust registry. Trust graphs can also be expressed via trust chains and chained credentials. Trust graphs can enable verifiers to make transitive trust decisions.

\n
trust limit:
\n

A limit to the degree a party is willing to trust an entity in a specific trust relationship within a specific trust context.

\n
trust list:
\n

A one-dimensional trust graph in which an authoritative source publishes a list of entities that are trusted in a specific trust context. A trust list can be considered a simplified form of a trust registry.

\n
trust network:
\n

A network of parties who are connected via trust relationships conforming to requirements defined in a legal regulation, trust framework or governance framework. A trust network is more formal than a digital trust ecosystem; the latter may connect parties more loosely via transitive trust relationships and/or across multiple trust networks.

\n
trust objective:
\n

An objective shared by the parties in a trust community to establish and maintain trust relationships.

\n
Trust over IP:
\n

A term coined by John Jordan to describe the decentralized digital trust infrastructure made possible by the ToIP stack. A play on the term Voice over IP (abbreviated VoIP).

\n
trust registry:
\n

A registry that serves as an authoritative source for trust graphs or other governed information describing one or more trust communities. A trust registry is typically authorized by a governance framework.

\n
trust registry protocol:
\n

See: ToIP Trust Registry Protocol.

\n
trust relationship:
\n

A relationship between a party and an entity in which the party has decided to trust the entity in one or more trust contexts up to a trust limit.

\n
trust root:
\n

The authoritative source that serves as the origin of a trust chain.

\n
trust service provider:
\n

In the context of specific digital trust ecosystems, such as the European Union’s eIDAS regulations, a trust service provider (TSP) is a legal entity that provides specific trust support services as required by legal regulations, trust frameworks, or governance frameworks. In the larger context of ToIP infrastructure, a TSP is a provider of services based on the ToIP stack. Most generally, a TSP is to the trust layer for the Internet what an Internet service provider (ISP) is to the Internet layer.

\n
trust support:
\n

A system, protocol, or other infrastructure whose function is to facilitate the establishment and maintenance of trust relationships at higher protocol layers. In the ToIP stack, the trust support layer is Layer 1.

\n
trust support layer:
\n

In the context of the ToIP stack, the trust support layer is ToIP Layer 1. It supports the operations of the ToIP Trust Spanning Protocol at ToIP Layer 2.

\n
trust spanning layer:
\n

A spanning layer designed to span between different digital trust domains. In the ToIP stack, ToIP Layer 2 is the trust spanning layer.

\n
trust spanning protocol:
\n

See: ToIP Trust Spanning Protocol.

\n
trust task:
\n

A specific task that involves establishing, verifying, or maintaining trust relationships or exchanging verifiable messages or verifiable data that can be performed on behalf of a trust application by a trust task protocol at Layer 3 of the ToIP stack.

\n
trust task layer:
\n

In the context of the ToIP stack, the trust task layer is ToIP Layer 3. It supports trust applications operating at ToIP Layer 4.

\n
trust task protocol:
\n

A ToIP Layer 3 protocol that implements a specific trust task on behalf of a ToIP Layer 4 trust application.

\n
trust triangle:
\n

See: three-party model.

\n
trusted execution environment:
\n

A trusted execution environment (TEE) is a secure area of a main processor. It helps code and data loaded inside it to be protected with respect to confidentiality and integrity. Data integrity prevents unauthorized entities from outside the TEE from altering data, while code integrity prevents code in the TEE from being replaced or modified by unauthorized entities, which may also be the computer owner itself as in certain DRM schemes.

\n
trusted role:
\n

A role that performs restricted activities for an organization after meeting competence, security and background verification requirements for that role.

\n
trusted third party:
\n

In cryptography, a trusted third party (TTP) is an entity which facilitates interactions between two parties who both trust the third party; the third party reviews all critical transaction communications between the parties, based on the ease of creating fraudulent digital content. In TTP models, the relying parties use this trust to secure their own interactions. TTPs are common in any number of commercial transactions and in cryptographic digital transactions as well as cryptographic protocols, for example, a certificate authority (CA) would issue a digital certificate to one of the two parties in the next example. The CA then becomes the TTP to that certificate’s issuance. Likewise transactions that need a third party recordation would also need a third-party repository service of some kind.

\n
trusted timestamp authority:
\n

An authority that is trusted to provide accurate time information in the form of a timestamp.

\n
trustworthy:
\n

A property of an entity that has the attribute of trustworthiness.

\n
trustworthiness:
\n

An attribute of a person or organization that provides confidence to others of the qualifications, capabilities, and reliability of that entity to perform specific tasks and fulfill assigned responsibilities. Trustworthiness is also a characteristic of information technology products and systems. The attribute of trustworthiness, whether applied to people, processes, or technologies, can be measured, at least in relative terms if not quantitatively. The determination of trustworthiness plays a key role in establishing trust relationships among persons and organizations. The trust relationships are key factors in risk decisions made by senior leaders/executives.

\n
TSP:
\n

See: trust service provider, trust spanning protocol.

\n
TTA:
\n

See: trusted timestamp authority.

\n
TTP:
\n

See: trusted third party.

\n
UDP:
\n

See: User Datagram Protocol.

\n
unicast:
\n

In computer networking, unicast is a one-to-one transmission from one point in the network to another point; that is, one sender and one receiver, each identified by a network address (a unicast address). Unicast is in contrast to multicast and broadcast which are one-to-many transmissions. Internet Protocol unicast delivery methods such as Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) are typically used.

\n
unicast address:
\n

A network address used for a unicast.

\n
user agent:
\n

A software agent that is used directly by the end-user as the principal. Browsers, email clients, and digital wallets are all examples of user agents.

\n
User Datagram Protocol:
\n

In computer networking, the User Datagram Protocol (UDP) is one of the core communication protocols of the Internet protocol suite used to send messages (transported as datagrams in packets) to other hosts on an Internet Protocol (IP) network. Within an IP network, UDP does not require prior communication to set up communication channels or data paths.

\n
utility governance framework:
\n

A governance framework for a digital trust utility. A utility governance framework may be a component of or referenced by an ecosystem governance framework or a credential governance framework.

\n
validation:
\n

An action an agent (of a principal) performs to determine whether a digital object or set of data meets the requirements of a specific party.

\n
vault:
\n

See: digital vault.

\n
VC:
\n

See: verifiable credential.

\n
verifiability (of a digital object:
\n

The property of a digital object, assertion, claim, or communication, being verifiable.

\n
verifiability (of a digital object:
\n

The property of a digital object, assertion, claim, or communication, being verifiable.

\n
verifiability (of a digital object:
\n

The property of a digital object, assertion, claim, or communication, being verifiable.

\n
verifiable:
\n

In the context of digital communications infrastructure, the ability to determine the authenticity of a communication (e.g., sender, contents, claims, metadata, provenance), or the underlying sociotechnical infrastructure (e.g., governance, roles, policies, authorizations, certifications).

\n
verifiable credential:
\n

A standard data model and representation format for cryptographically-verifiable digital credentials as defined by the W3C Verifiable Credentials Data Model specification.

\n
verifiable data:
\n

Any digital data or object that is digitally signed in such a manner that it can be cryptographically verified.

\n
verifiable data registry:
\n

A registry that facilitates the creation, verification, updating, and/or deactivation of decentralized identifiers and DID documents. A verifiable data registry may also be used for other cryptographically-verifiable data structures such as verifiable credentials.

\n
verifiable identifier:
\n

An identifier over which the controller can provide cryptographic proof of control.

\n
verifiable identifier:
\n

An identifier over which the controller can provide cryptographic proof of control.

\n
verifiable message:
\n

A message communicated as verifiable data.

\n
verification:
\n

An action an agent (of a principal) performs to determine the authenticity of a claim or other digital object using a cryptographic key.

\n
verifier (of a claim or credential):
\n

A role an agent performs to perform verification of one or more proofs of the claims in a digital credential.

\n
VID:
\n

See ​​verifiable identifier.

\n
VID relationship:
\n

The communications relationship formed between two VIDs using the ToIP Trust Spanning Protocol. A particular feature of this protocol is its ability to establish as many VID relationships as needed to establish different relationship contexts between the communicating entities.

\n
VID-to-VID:
\n

The specialized type of peer-to-peer communications enabled by the ToIP Trust Spanning Protocol. Each pair of VIDs creates a unique VID relationship.

\n
virtual vault:
\n

A digital vault enclosed inside another digital vault by virtue of having its own verifiable identifier (VID) and its own set of encryption keys that are separate from those used to unlock the enclosing vault.

\n
Voice over IP:
\n

Voice over Internet Protocol (VoIP), also called IP telephony, is a method and group of technologies for voice calls for the delivery of voice communication sessions over Internet Protocol (IP) networks, such as the Internet.

\n
VoIP:
\n

See: Voice over IP.

\n
W3C Verifiable Credentials Data Model Specification:
\n

A W3C Recommendation defining a standard data model and representation format for cryptographically-verifiable digital credentials. Version 1.1 was published on 03 March 2022.

\n
wallet:
\n

See: digital wallet.

\n
wallet engine:
\n

The set of software components that form the core of a digital wallet, but which by themselves are not sufficient to deliver a fully functional wallet for use by a digital agent (of a principal). A wallet engine is to a digital wallet what a browser engine is to a web browser.

\n
witness:
\n

A computer system that receives, verifies, and stores proofs of key events for a verifiable identifier (especially an autonomous identifier). Each witness controls its own verifiable identifier used to sign key event messages stored by the witness. A witness may use any suitable computer system or database architecture, including a file, centralized database, distributed database, distributed ledger, or blockchain.

\n
zero-knowledge proof:
\n

A specific kind of cryptographic proof that proves facts about data to a verifier without revealing the underlying data itself. A common example is proving that a person is over or under a specific age without revealing the person’s exact birthdate.

\n
zero-knowledge service:
\n

In cloud computing, the term “zero-knowledge” refers to an online service that stores, transfers or manipulates data in a way that maintains a high level of confidentiality, where the data is only accessible to the data's owner (the client), and not to the service provider. This is achieved by encrypting the raw data at the client’s side or end-to-end (in case there is more than one client), without disclosing the password to the service provider. This means that neither the service provider, nor any third party that might intercept the data, can decrypt and access the data without prior permission, allowing the client a higher degree of privacy than would otherwise be possible. In addition, zero-knowledge services often strive to hold as little metadata as possible, holding only that data that is functionally needed by the service.

\n
zero-knowledge service provider:
\n

The provider of a zero-knowledge service that hosts encrypted data on behalf of the principal but does not have access to the private keys in order to be able to decrypt it.

\n
zero-trust architecture:
\n

A network security architecture based on the core design principle “never trust, always verify”, so that all actors are denied access to resources pending verification.

\n
ZKP:
\n

See: zero-knowledge proof.

\n
anonymous
\n

An adjective describing when the identity of a natural person or other actor is unknown.

\n
assurance level
\n

A level of confidence that may be relied on by others. Different types of assurance levels are defined for different types of trust assurance mechanisms. Examples include authenticator assurance level, federation assurance level, and identity assurance level.

\n
authorization
\n

The process of verifying that a requested action or service is approved for a specific entity.

\n
out-of-band introduction
\n

A process by which two or more entities exchange VIDs in order to form a cryptographically verifiable connection (e.g., a ToIP connection), such as by scanning a QR code (in person or remotely) or clicking a deep link.

\n
out-of-band introduction
\n

A process by which two or more entities exchange VIDs in order to form a cryptographically verifiable connection (e.g., a ToIP connection), such as by scanning a QR code (in person or remotely) or clicking a deep link.

\n
permission
\n

Authorization to perform some action on a system.

\n
policy
\n

Statements, rules or assertions that specify the correct or expected behavior of an entity.

\n
real world identity
\n

A term used to describe the opposite of digital identity, i.e., an identity (typically for a person) in the physical instead of the digital world.

\n
self-certifying identifier
\n

A subclass of verifiable identifier that is cryptographically verifiable without the need to rely on any third party for verification because the identifier is cryptographically bound to the cryptographic keys from which it was generated.\n~ Also known as: autonomous identifier.

\n
self-certifying identifier
\n

A subclass of verifiable identifier that is cryptographically verifiable without the need to rely on any third party for verification because the identifier is cryptographically bound to the cryptographic keys from which it was generated.\n~ Also known as: autonomous identifier.

\n
NIST-CSRC
\n

NIST Computer Security Resource Center Glossary

\n
"]