Keet notes: the reading guide

The Keet Notes are study notes from Hadto’s working read of Maria Keet’s ontology-engineering textbook, applied to one question: what does a small business need to make its operating knowledge explicit, inspectable, and transferable? They are annex material, written in a study register for readers who care about the research itself. If you own a business and landed here from a search, the posts written for you are indexed from the start-here page; this series is the source work behind them.

The notes follow the book’s chapter order, and the order matters: the first four notes set the vocabulary the later application notes assume.

The study order

1. Start with the business problem, not the schema (Ch. 1). The annex’s working rule: judge an ontology by what it helps a system do.
2. Reasoning is a control surface, not an academic luxury (Ch. 2). What automated reasoning adds to a system’s guarantees: checks, contradiction detection, surfaced implications.
3. Description logics tell us what to automate and what to bound (Ch. 3). Description logics as an explicit statement of system power and system limits.
4. The ontology stack needs explicit contracts (Ch. 4). OWL and the wider Semantic Web stack read as capability boundaries for builders.
5. Keet notes, chapter 5: methodology and the quality gates (Ch. 5, consolidated). Methodology, pitfalls, and the quality gates, merged from five earlier notes.
6. A venture platform needs a stated ontology posture (Ch. 6). Foundational ontology commitments as a policy decision rather than invisible plumbing.
7. Not every contains edge is parthood (companion to Ch. 6). Keet’s part-whole taxonomy: containment, membership, participation, and composition cannot share one edge.
8. Keet notes, chapter 7: bottom-up sources need lifting and review (Ch. 7, consolidated). Extracting ontology candidates from data and documents, merged from three earlier notes.
9. Your ontology platform has to say where the live data lives (Ch. 8). Ontology-based data access, and why the semantic layer has to name its reach into live records.
10. Multilingual ontology work is governance, not extra labels (Ch. 9). Multilingual support as identifier policy and translation governance.
11. Confidence scores are not fuzzy semantics (Ch. 10). A confidence field does not mean the ontology understands uncertainty.
12. Keet notes, chapter 11: when is ontology work published? (Ch. 11, consolidated). What makes ontology work publishable and maintainable, merged from three earlier notes.

About the consolidated notes

Three entries above are consolidation points from the archive restructure, and it helps to know that when you follow older links. The Chapter 5 note absorbed five earlier posts on methodology, pitfalls, and gates. The Chapter 7 and Chapter 11 notes each absorbed three, on bottom-up sources and on publication. Eleven earlier posts were retired into those three chapter notes, which are now the canonical home for that material; if you remember an older standalone note on, say, RBox governance or semantic lifting, its substance is in the matching chapter note.

Citations from outside the series already point at the consolidated notes. The pipeline post on keeping research evidence attached cites the Chapter 7 and Chapter 11 notes as its public context, which is the pattern the annex is meant to support: the chapter note holds the study material, and the operating posts cite it instead of restating it.