Structure
Overview
UBKDS organizes knowledge using a stable reference structure intended to be:
- consistent,
- teachable,
- and portable.
The standard separates Domain, Sensitivity, and Lifecycle so that meaning, access, and change can be governed independently.
Structural Rules
Meaning is anchored in Domain
Domain describes what something is.
Access is controlled through Sensitivity
Sensitivity controls who can see or edit.
Change is managed through Lifecycle
Lifecycle controls drafting, publishing, review, and retirement.
A reference must be stable
References should not be reorganized casually.
Canonical Addressing
A UBKDS reference provides a stable location for a knowledge item.
A reference is composed of:
- Domain code (meaning)
- Sensitivity code (access)
- Lifecycle code (change stage)
This structure allows:
- consistent retrieval,
- consistent governance,
- and clearer change management.
Controlled Vocabulary
UBKDS relies on controlled definitions. Organizations may extend the system, but:
- extensions must not conflict with canon,
- and canon should remain stable across organizations.
Implementation Neutrality
UBKDS can be implemented in:
- document libraries,
- knowledge bases,
- wikis,
- ticketing systems,
- or custom platforms.
The structure is not dependent on any single vendor.