From Semantic Modeling to Executable Knowledge
By completing Chapter (14) - I know it’s a long chapter - you have reached an important milestone in your ontology engineering journey.
So far, this book has introduced the fundamental building blocks of OWL, including:
some)only)These concepts form the logical language used to describe knowledge in an ontology.
At this point, you already understand how OWL expresses semantic knowledge.
The focus now changes.
Instead of learning individual OWL constructs one by one, the remaining chapters will show how these constructs work together to build complete semantic systems.
In other words, you are moving from
learning a language
toward:
learning an engineering discipline.
Congratulations on reaching this milestone!
Before continuing, consider taking a short break, grab a cup of coffee or tea.
Reflect on how far you have progressed – from creating your first ontology in Protégé to understanding semantic restrictions and automated reasoning.
The chapters that follow will build upon everything you have learned so far.
Learning OWL syntax is similar to learning the vocabulary and grammar of a spoken language.
Knowing individual words does not automatically enable someone to write a novel.
Likewise, understanding individual OWL constructs DOES NOT immediately translate into designing scalable enterprise ontologies.
Ontology engineering is a systematic process.
Each modeling decision influences future reasoning, validation, governance, and knowledge reuse.
Professional ontology engineers therefore think beyond individual classes or properties.
They consider questions such as:
These questions shift ontology engineering from software operation to architectural design.
The remaining chapters of this book introduce a structured engineering workflow that answers these questions.
Throughout the remainder of this book, we introduce the Semantic Knowledge Development Lifecycle (SKDL).
The SKDL describes the progressive stages through which semantic knowledge evolves – from an initial conceptual model into executable knowledge capable of supporting intelligent systems.
Unlike a software development lifecycle (SDLC), which primarily transforms requirements into executable code, the SKDL transforms domain knowledge into executable semantics.
This lifecycle provides a practical roadmap for ontology engineers, enterprise architects, and knowledge graph practitioners.
flowchart LR
A[1. Conceptual<br/>Modeling]
-->B[2. Semantic<br/>Description]
-->C[3. Knowledge<br/>Reuse]
-->D[4. Semantic<br/>Governance]
-->E[5. Validation]
-->F[6. Reasoning]
-->G[7. Executable<br/>Knowledge]
style G fill:#D5F5E3
Each stage builds upon the previous one.
Together, these stages transform static data models into intelligent semantic systems.
| Stage | Purpose | Typical Activities |
|---|---|---|
| 1. Conceptual Modeling | Identify and organize domain concepts into semantic hierarchies. | Create classes, subclasses, and taxonomy structures. |
| 2. Semantic Description | Describe concepts using logical characteristics and restrictions. | Add properties, restrictions, and semantic definitions. |
| 3. Knowledge Reuse | Reuse existing semantic patterns to improve modeling efficiency and consistency. | Duplicate, refine, and specialize ontology structures. |
| 4. Semantic Governance | Maintain semantic quality and prevent contradictory knowledge. | |
| 5. Validation | Verify ontology consistency before deployment. | Detect logical conflicts using reasoners and validation tools. |
| 6. Reasoning | Discover implicit knowledge automatically. | Execute OWL inference and semantic classification. |
| 7. Executable Knowledge | Connect semantic knowledge with enterprise systems and intelligent automation. | Integrate with EKA, knowledge graphs, APIs, workflows, and AI applications. |
Although presented sequentially, ontology development is rarely linear.
Engineers often revisit earlier stages as domain knowledge evolves.
The lifecycle is therefore iterative rather than strictly sequential.
Readers familiar with the EKA framework will notice that the Semantic Knowledge Development Lifecycle (SKDL) naturally aligns with the architecture introduced in Chapter (00).
$\large{EKA = (K, R, \Theta, \Phi, \Gamma)}$
| Lifecycle Stage | Primary EKA Components | Contribution |
|---|---|---|
| 1. Conceptual Modeling | $K$ | Establishes entities and semantic relationships. |
| 2. Semantic Description | $K+R$ | Enriches the graph with logical semantics and OWL axioms. |
| 3. Knowledge Reuse | $K$ | Promotes reusable ontology design patterns and semantic consistency. |
| 4. Semantic Governance | $\Gamma$ | Applies semantic rules, quality controls, SHACL constraints, and governance policies. |
| 5. Validation | $\Gamma + R$ | Uses reasoners and validation mechanisms to verify logical consistency. |
| 6. Reasoning | $R$ | Infers new knowledge through OWL reasoning and rule execution. |
| 7. Executable Knowledge | $\Theta + \Phi$ | Connects semantic reasoning with events, workflows, APIs, and enterprise execution. |
Ths lifecycle there explains how semantic knowledge evolves, while EKA explains how that knowledge is operationalized inside executable enterprise systems.
One unique aspect of this ebook is that is interprets Michael DeBellis’ Pizza tutorial through the perspective of ontology engineering rather than simply following the software exercises.
Exercise 14 through 20 collectively illustrate the complete Semantic Knowledge Development Lifecycle.
| Tutorial Exercise | Semantic Knowledge Development Lifecycle | Primary Learning Objective |
|---|---|---|
| Exercise 14 | Conceptual Modeling | Create the first semantic taxonomy. |
| Exercise 15 | Semantic Description | Add logical characteristics to classes. |
| Exercise 16-17 | Knowledge Reuse | Reuse and specialize semantic design patterns. |
| Exercise 18 | Semantic Governance | Protect semantic integrity through disjointness. |
| Exercise 19 | Validation | Detect logical inconsistencies using reasoning. |
| Exercise 20 | Reasoning | Enable automatic semantic classification. |
Viewed individually, these exercises appear to be simple Protégé operations.
Viewed collectively, they demonstrate the lifecycle followed by professional ontology engineers.
This perspective transforms a sequence of software tutorials into a coherent methodology for semantic knowledge development.
The idea that knowledge develops through progressive stages is not new. Throughout history, philosophers, scientists, and management scholars have proposed different ways of understanding how knowledge is created, refined, and applied.
One of the earliest discussions can be found in Plato’s Theaetetus, where Socrates explores the question:
What is knowledge?
Among the ideas discussed is the famous concept that knowledge can be understood as justified true belief – a belief that is true and supported by sufficient justification. Although modern epistemology has refined and challenged this definition, it established an enduring principle:
Knowledge is more than information; it requires structure, meaning, and justification.
More than two thousand years later, knowledge management researchers continued exploring how knowledge evolves within organization. A particularly influential example is the SECI Model, proposed by Ikujiro Nonaka and Hirotaka Takeuchi. The model describes organizational knowledge creation as a continuous cycle of:
The Semantic Knowledge Development Lifecycle (SKDL) introduced in this book is inspired by the same fundamental observation:
Knowledge is not created in a single step – it evolves through successive stages.
However, SKDL addresses a different problem.
Rather than describing how people create organizational knowledge, SKDL describes how semantic knowledge is engineered into machine-interpretable models capable of supporting automated reasoning and intelligent systems.
The progression can be summarized as:
flowchart TD
A[Concepts]-->B[Semantic Models]
-->C[Knowledge Reuse]
-->D[Semantic Governance]
-->E[Validation]
-->F[Reasoning]
-->G[Executable Knowledge]