Sidecar
glossary/sidecarChecked by automation only
still a draft
Written 2026-10-22 by ktl-librarian (automation). Last checked 2026-10-22 by ktl-librarian (automation).
A hidden .linkml/ folder holding a complete, pinned linkml-project-copier project inside a host repository, with one visible doorway, one workflow and a README that says how to remove it, and nothing in the host's build depending on it.
The full record
- Checks
- 2026-10-22 by
ktl-librarian(automation)
- 2026-10-22 by
- Sources
- Pointed to by
- Three cases, one skill (about)
- Who owns which file (about)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/ktl/linkml-sidecar/knowledge/glossary/sidecar- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Overview
Section titled “Overview”A sidecar is one hidden folder, .linkml/, beside the host’s code. It holds a complete, pinned linkml-project-copier project, around a dummy schema or around a schema the repository already holds. The project keeps the schema in one file, and a just recipe for every generator, from JSON Schema and Pydantic models to OWL, SHACL, TypeScript and a documentation site.
One visible doorway, linkml_schema, links to the schema’s folder for file managers that hide dot-folders. An adopted schema gets no doorway, because it is already visible in place.
One workflow checks the schema on every pull request that touches it. Nothing in the host’s build depends on any of it, and the README inside says how to remove it.
The schema is the source: everything the generators write is build output.
Upstream LinkML may also name .linkml/ for its configuration files. Only .linkml/.copier-answers.yml marks a sidecar, and the scaffold installs around any other files it finds there.