Mastering Ontology Engineering with Protege and Pizza.owl, Volume 3, is where your ontology starts enforcing real logical requirements instead of just describing structure.
This volume was originally a single chapter bundled inside Volume 2, and it grew large enough, nearly three times the length of any other chapter, that it now stands on its own across three focused chapters. You'll learn the existential restriction (some), the requirement that at least one qualifying relationship must exist, and the universal restriction (only), the constraint that bounds what's allowed. Then you'll see exactly why both must be combined correctly to define something like VegetarianPizza the way a reasoner actually understands it, a detail that trips up nearly everyone the first time. The volume closes by placing restrictions inside the Executable Knowledge Architecture (EKA) framework as a governance layer, and by cataloguing the most common restriction-modeling mistakes, drawn directly from real technical review.
In this volume you'll learn to:
- Use existential restriction (
some) and understand what it actually asserts to a reasoner - Use universal restriction (
only), including the vacuous truth trap that catches most beginners - Correctly combine both into a composite class definition
- Compare the same logical requirement as a Cypher constraint in Neo4j, and understand why OWL's Open World Assumption differs from a property graph's Closed World queries
- Treat restrictions as a governance layer within the EKA framework
- Recognize and avoid the most common restriction-modeling mistakes
This edition includes forewords by Timothy W. Cook (Founder, Semantic Data Charter) and Michael DeBellis, along with detailed technical review credited throughout the book, including a corrected VegetarianPizza definition contributed directly by Michael DeBellis.
Best read after Volumes 1 and 2, though readers already comfortable with basic OWL classes and object properties can start here.
