LinkML models of published specifications, standards and vocabularies. lmodel is a workshop for LinkML patterns: no model here is an official release of what it renders, and most have no users yet. Each model's address, https://w3id.org/lmodel/<repository>, redirects to its documentation site.

A host can pin a usable model, adapt it for its knowledge bundle and import it. slsa is the reference for every item.

• A linkml-project-copier project at template v0.5.0, or, in a fork of an upstream project, the same toolchain beside the upstream's code. The CONTRIBUTING checklist, the SECURITY policy, the code of conduct, the AI covenant, NOTICE, and lint configuration for links, Markdown, YAML and LinkML.
• A schema header with the upstream's edition in version, its canonical address in source, and the licence. An upstream watch pinned to that edition reports when it moves.
• A copy of the upstream text only where its licence allows, matched to the edition by hash, and a citation by address and date otherwise.
• A valid example for each class a concept may name as its type, a counter-example for each constraint the schema states, tests green, and linkml-lint clean under the repository's .linkmllint.yaml.
• Semantic-release from a baseline tag. Each GitHub release carries schema-<tag>-<name>.yaml, its .sha256 and a build-provenance attestation.
• A KTL sidecar at the current KTL release with lokf 0.9.0 or later, a librarian-written knowledge bundle and a knowledge website. just lokf-adapt with named roots, just lokf-adapt-check in CI, and a README section listing the classes for the Known LOKF types setting and the keys the copy renames.
• A README that says what the schema models and at which edition, what shaped its design, and what it maps to without borrowing from.
• PyPI publishing off until a consumer needs the Python classes.
• A row below.

The waves bring each repository to the list above, one repository at a time. A new repository joins when a host needs its classes as concept types or two models need it as a shared import, and it has a stable, licensed, machine-readable source to pin. The version column is the schema header's as it stands, and the Release column names the latest release that carries a schema asset, the one a host pins.

The models a supply-chain knowledge bundle cites as authorities: the workflow contract, the attestation container, assessment results, the SBOM and the secure development practices.

Control catalogues, with oscal as their pivot.

attack follows stix, whose schema it carries. The Unified Cyber Ontology repositories become one repository, uco, with a module for each, and each module keeps its address.

ucs-core and ucs-containers, a use-case framework with no upstream, are archived until a model needs them.

vulnerability-core goes first, because cve, nist-nvd and kev-catalog import it.

nist-ai-600-1 and nist-ai-rmf import nist-ai-100-1, so the three go in that order.

• linkml-project-copier: a fork of the LinkML project template.
• sssom-files: mapping files in the SSSOM TSV format.
• w3id_smoke_test: tests the w3id.org/lmodel redirects.