LinkML
references/linkmlNobody has checked this yet
Written 2026-10-29 by ktl-librarian (automation).
The full record
- Checks
- none recorded
- Sources
- Related to
- Pointed to by
- OSCAL Assessment Plan Schema (references)
- OSCAL Assessment Results Schema (references)
- OSCAL Catalog Schema (references)
- OSCAL Component Definition Schema (references)
- OSCAL Mapping Collection Schema (references)
- OSCAL POA&M Schema (references)
- OSCAL Profile Schema (references)
- OSCAL Schema (top-level) (references)
- OSCAL System Security Plan Schema (references)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/lmodel/oscal/knowledge/references/linkml- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
LinkML
Section titled “LinkML”The OSCAL schema is a LinkML schema: every schema file in src/oscal/schema/ binds the prefix linkml: to https://w3id.org/linkml/ and imports linkml:types. The README says that the repository was built from the linkml-project-copier template, which it credits by the DOI 10.5281/zenodo.15163584.1 .copier-answers.yml records the template’s address, https://github.com/linkml/linkml-project-copier, at v0.5.0.2
Versions
Section titled “Versions”pyproject.toml requires linkml-runtime 1.9.4 or later, and its dev group linkml 1.9.3 or later and jsonschema.3 uv.lock pins linkml 1.11.1 and linkml-runtime 1.11.1.4
The tools the recipes run
Section titled “The tools the recipes run”The justfile runs LinkML’s gen-project for most generated formats, and gen-pydantic, gen-java, gen-typescript and gen-owl on their own. It runs gen-yaml and gen-doc for the documentation, linkml-lint for just lint, and linkml-run-examples in just test.5 project.justfile runs linkml-validate over the example data and many further generators: Generated artefacts lists them, and notes the patched scripts in scripts/issues/ that work around generator bugs.
Where the generated code falls short
Section titled “Where the generated code falls short”tests/test_data.py records two limits of the generated Python code.6 Some generated classes read hyphenated alias keys during construction, so the test loader injects those keys by hand for a few classes, and its docstring says that issues were raised upstream with LinkML. A generated enum class does not accept a value outside its declared set, even for an enum that allows other values, and the tests mark that as an expected failure. SECURITY.md says that problems in LinkML, its generators and its runtime are reported to LinkML.
Footnotes
Section titled “Footnotes”-
README.md, the Credits section ↩
-
.copier-answers.yml,
_src_pathand_commit↩ -
pyproject.toml, dependencies and dependency-groups ↩
-
uv.lock, the linkml and linkml-runtime packages ↩
-
justfile, the gen-project, gen-python, gen-doc,
_gen-yaml, lint and_test-examplesrecipes ↩ -
tests/test_data.py, the docstring of
_validate_schemaand the allow-other tests ↩