Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 56 GitHub source documents. All source documents are searchable here.
Last updated: October 7, 2025
This content is meant to be consumed by AI agents via MCP. Click here to get the MCP configuration.
Note: In rare cases it may contain LLM hallucinations.
For authoritative documentation, please consult the official GLEIF vLEI trainings and the ToIP Glossary.
In technical specifications, 'normative' designates content that establishes mandatory requirements, procedures, or behaviors that implementations MUST follow for compliance, as opposed to informative or explanatory content.
In the context of technical specifications and standards documentation, normative refers to sections, statements, or requirements that are prescriptive and mandatory. Normative content:
This contrasts with non-normative (informative) content, which provides examples, explanations, or guidance without imposing requirements.
Within KERI and ACDC specifications, the normative/non-normative distinction is critical for implementers:
Normative Sections in KERI specifications include:
Normative Language uses RFC 2119 keywords:
When reading KERI/ACDC specifications:
For vLEI and other KERI-based ecosystems:
Normative requirements have versioning implications:
For example, the KERI specification states normatively: "Each establishment event MUST include a commitment to the next set of keys via cryptographic digest." This is a binding requirement—implementations lacking this feature are non-compliant.
ACDC Normative Requirements include:
v, d, i, s, a, e, r)Non-Normative Content in these specifications includes:
The distinction matters because:
RFC 2119 Keywords: The standard vocabulary for expressing normative requirements in technical specifications, defining the precise meaning of MUST, SHOULD, MAY, etc.
Conformance: The state of meeting all normative requirements in a specification—implementations are either conformant or non-conformant based on normative criteria.
Specification: A formal document containing both normative (mandatory) and non-normative (informative) content that defines a protocol, format, or system.
Governance Framework: Documents like the vLEI Ecosystem Governance Framework that establish normative policies and requirements for ecosystem participants.