The AFMRO sample.

The Aircraft Fleet Mission Readiness Ontology — a small gist 14-aligned exemplar covering aircraft fleet capability, mission tasking, configuration, and maintenance state. Used as the workshop's demonstration ontology.

gist 14 aligned ~28 classes CC-BY-SA-4.0

The five files

Download or view each file. Drop the flawed version onto the linter's home page to see all six rules fire.

TTL
afmro-clean.ttl
Clean reference ontology — what the demo ends up at after applying the methodology. Sixteen domain classes extending gist 14 by IRI; full SKOS annotations; OWL property restrictions throughout.
TTL
afmro-flawed.ttl
The deliberately flawed demo version. Three primary anti-patterns — deep hierarchy explosion, plan/occurrence collapse, parallel property invention — plus orphan classes and minor hygiene flaws. Drop this on the linter for 44 findings across all six rules.
TTL
afmro-shacl-clean.ttl
SHACL shapes for the clean ontology. Enforces the structural constraints implied by the competency questions, including disjointness on Mission/MissionPlan to keep planning and occurrence properties on the right classes.
TTL
afmro-instances-sample.ttl
Synthetic instance data. Ten aircraft across three categories, two squadrons, two RAAF bases, components, capabilities, readiness states, mission plans (one cancelled, one capability-gap), missions, and maintenance events. Designed so every CQ has both a yes-case and a no-case.
TXT
afmro-cqs.txt
Twelve worked competency questions for AFMRO. Each has a use case, the ontology elements it exercises, and a SPARQL skeleton against the clean ontology.