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.
1.1 KiB
1.1 KiB
Implementation Phases
Phase 1 - Research and reduction
- study PiCo documentation and article material
- identify the smallest reusable semantic hubs for GLAM custodians
- decide what stays conceptual and what remains engineering-only
Phase 2 - Parsimonious LinkML scaffolding
- create the package structure
- create package metadata and root schema
- define the first small set of classes and slots
Phase 3 - Bridge to engineering ontology
- create explicit mapping modules
- document downward realization from hypernyms to engineering classes/slots/enums
- verify external ontology mappings against
data/ontology/
Phase 4 - Rule revisions
- edit or extend the relevant LinkML rules
- document which rules are shared across both ontology layers
- document which rules are engineering-only and which become dual-layer
Phase 5 - Dashboard rollout
- enable
/parsimony - verify manifests, routing, and UML rendering
- surface the package even before full ontology completion
Phase 6 - Iterative population
- add the final limited class set
- add the slot budget in a controlled way
- resist ontology growth unless justified in the mapping docs