ab5ad23699
- Created manifest.json for the parsimonious LinkML package. - Added metadata.yaml with detailed information about the Heritage Custodian Parsimony Ontology. - Established directory structure for classes, enums, mappings, and slots with corresponding README files. - Each module directory includes a brief description of its purpose and planned scale.
28 lines
1.7 KiB
Markdown
28 lines
1.7 KiB
Markdown
# Semantic Parsimony Ontology Plan
|
|
|
|
This plan defines how to derive a parsimonious LinkML ontology from the engineering ontology in `schemas/20251121/linkml/modules/` while keeping the engineering model as the authoritative implementation layer.
|
|
|
|
Goals:
|
|
|
|
- Keep the parsimonious ontology deliberately small: about 10 classes, 30 datatype properties, and 50 object properties.
|
|
- Reuse the PiCo pattern: small conceptual hub classes, explicit evidence/provenance, and strong reuse of external vocabularies.
|
|
- Make the parsimonious-to-engineering mapping a first-class deliverable, not an afterthought.
|
|
- Expose the parsimonious LinkML schema in the same dashboard/viewer pattern used for `bronhouder.nl/linkml`.
|
|
- Document which existing LinkML rules stay valid, which need clarification, and which need extension for the parsimonious layer.
|
|
|
|
Document index:
|
|
|
|
- `00-master-checklist.md` - implementation tracker
|
|
- `01-reference-model-review.md` - PiCo and related parsimonious ontology lessons
|
|
- `02-target-parsimonious-model.md` - target class/property budget and conceptual shape
|
|
- `03-linkml-module-layout.md` - file layout and schema packaging plan
|
|
- `04-engineering-mapping-strategy.md` - core mapping strategy to the engineering ontology
|
|
- `05-rule-updates.md` - required updates/extensions to `.opencode/rules/linkml/`
|
|
- `06-dashboard-and-uml-viewer.md` - `bronhouder.nl/parsimony` rollout plan
|
|
- `07-implementation-phases.md` - phased execution plan
|
|
|
|
Core stance:
|
|
|
|
- The parsimonious ontology is the semantic/conceptual layer.
|
|
- The engineering ontology remains the data-rich operational layer.
|
|
- Hypernym-style parsimonious concepts must map downward into concrete engineering classes, enums, and slots with verified LinkML mappings and explicit rationale.
|