Skip to content
MIF Ontologies
A shared base, extended by domains The knowledge triad and shared-traits mixins form a typed cyan base; domain ontologies extend it, fanning out to the right as amber nodes — software-security, scientific, regenerative-agriculture, and more — with a dashed node still forming. MIF ONE BASE, MANY DOMAINS mif-base extends +new typed base · domains extend it

MIF Ontology Corpus

One model, read the same by a person and a parser — no translation, no drift.
The ontology modelAuthor your first ontologyBrowse the corpusSpecification (mif-spec.dev)MIF home

How the corpus fits together

Section titled “How the corpus fits together”

A domain ontology does not invent its own vocabulary. It extends a shared base and adds only what is its own — the machine-cyan typed base every domain builds on, the human-amber meaning each domain contributes.

graph LR
  base["mif-base<br/>_semantic · _episodic · _procedural"] --> traits["shared-traits"]
  traits --> eng["engineering-base"]
  traits --> sec["software-security"]
  traits --> sci["scientific"]
  traits --> agri["regenerative-agriculture"]
  eng --> sec

Each ontology is one pair of files: the *.ontology.yaml a person reads and the generated *.ontology.jsonld a parser resolves. Start with the ontology model for the why, then author your first ontology for the how.