OSCAL Component Definition Schema
datasets/oscal-component-schemaNobody has checked this yet
Written 2026-10-29 by ktl-librarian (automation).
The full record
- Checks
- none recorded
- Sources
- Is part of
- References
- Depends on
- Derived from
- Pointed to by
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/lmodel/oscal/knowledge/datasets/oscal-component-schema- Licence
- https://www.apache.org/licenses/LICENSE-2.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
OSCAL Component Definition Schema
Section titled “OSCAL Component Definition Schema”src/oscal/schema/oscal_component.yaml is the module titled “OSCAL Component Definition Model”, with the id https://w3id.org/lmodel/oscal/oscal_component.1 Its version is 1.2.3, its license Apache-2.0, and its source is NIST’s JSON schema of the model, http://csrc.nist.gov/ns/oscal/1.2.3/oscal-component-definition-schema.json. It imports linkml:types, the catalog module and the assessment plan module. Its see_also names NIST’s page on the component definition, https://pages.nist.gov/OSCAL/learn/concepts/layer/implementation/component-definition/.
The README describes the model as components and the controls each implements.2 ComponentDefinition is “A collection of component descriptions, which may optionally be grouped by capability”. It requires uuid and metadata, and also holds import-component-definitions, components, capabilities and back-matter. ComponentDefinitionDocument wraps one component definition as the root of a component definition document.
The module’s one subset, component_definition, holds the root document and its containers: ImportComponentDefinition, DefinedComponent, Capability, IncorporatesComponent, ControlImplementationSet, ImplementedRequirement and ImplementedControlStatement. The two third-party fixture sets, CNCF AI Ecosystem OSCAL Benchmarks and NIST 800-53 Rev 5 to AWS Service Mapping (Luigi Carpio), are component definitions checked against this module.