No technical book is perfect – including this one.
Despite countless hours of writing, reviewing, testing, and refining, errors inevitably remain still. Some my be typographical. Others may be technical inaccurancies. A few might be conceptual oversights or outdated patterns that better approaches have since clarified.
This chapter exists for one reaon:
to invite you, the reader, to help make this book better!
Ontology engieering is a living discipline. Semantic technologies evolve. Best Practices mature. New tools introduce. And with your help, this book can evolve alongside them.
This chapter serves three purposes:
Before you begin searching (“hunting”), let me help you understand what to look for.
Errors in a book could like this typically fall into below categories:
| Error Category | Description | Sample Types |
|---|---|---|
| Technical Errors | These are factual mistakes about OWL, Protégé, RDF, reasoning, or the EKA framework itself | <li>Incorrect OWL syntax</li><li>Misleading logical statements</li><li>Reasoning behavior errors</li> |
| Conceptual Errors | These are misunderstandings or oversimplifications that might mislead readers about deeper semantic principles. | <li>Oversimplified distinctions</li><li>Missing nuance in OWL</li><li>Confusing concepts</li> |
| Typographical and Grammatical Errors | These are the “small stuff” – but small fixes improve readability and professionalism. | <li>Misspellings</li><li>Missing words</li><li>Inconsistent terminology</li> |
| Outdated or Deprecated Patterns | Ontology engineerng tools and standards evolve. What was best practice in 2025 may be outdated by 2028. | <li>Deprecated reasoner features</li><li>Outdated plugin names</li><li>Evolving OWL 2 features<li> |
| Structural and Pedagogical Issues | These are not “errors” per se, but opportunities to improve learning effectiveness. | <li>Unclear explanations<li><li>Missing prerequisites</li><li>Exercise ambiguity</li><li>Brokden cross-reference</li> |
Great, you catch one 😊! Your contribution are sincerely appreciated.
Please follow this structured process so I can address your feedback efficiently.
Before reporting, please:
You have two options:
| Method | Best for | Link |
|---|---|---|
| GitHub Issue | Reporting errors without proposing specific fixes | Open an issue $\rightarrow$ |
| Pull Request | Proposing direct corrections (typos, code examples, clarifications) | Open a Pull Request $\rightarrow$ |
For Issues (no fix proposed), I’ve configured this template in repository already:
=== Template Start===
Chapter: [e.g., Chapter 14]
Section: [e.g., 14.5.2]
Page/Line: [if applicable]
Error Type: (Technical / Conceptual / Typographical / Outdated / Pedagogical)
Current Text:
[Quote the exact text that contains the error]
Suggested Correction:
[Describe what should replace it, or why it is wrong]
Reasoning:
[Explain why this is an error — cite OWL specification, reasoner behavior, or logical principles]
Additional Context:
[Protégé version, reasoner used, screenshots if helpful]
=== Template End===
For Pull Request (fix proposed):
If you are comfortable with Git and Markdown, welcome directly edit the .md file in the ebook/ directory.
Your pull request should:
main branchI will review all pull requests as quickly as possible.
All feedback is welcome and appreciated – including critical feedback. However, please follow the principle of charitable interpretation.
Rude or dismissive reports will be closed. Thoughtful, respectful reports will be treasured.
Contributors section below.The book is a living document. When errors are fixed:
CHANGELOG.md will track significant correctionsYou can always find the latest version at ebook folder of https://github.com/yasenstar/protege_pizza.
The following invididuals have contributed error reports, corrections, or improvements to this book. (also in the dedicated contributors file)
| Name / GitHub Handle | Contribution Type | Chapter(s) | Date |
|---|---|---|---|
| Your name here | Error report / Pull request | X | YYYY-MM-DD |
This space is reserved for you.
When you report an error that leads to a correction, your name will be added here with my sincere thanks.
This chapter exists because I believe in a specific philosophy of technical education:
Books are not monuments. Books are conversations.
When you read a chapter and find an error, you are not “criticizing” the author. You are contributing the work of making knowledge clearer, more accurate, and more useful.
Every technical book ever written contains errors. The only question is whether those errors remain hidden or become opportunities for improvement.
By opening this chapter, by inviting you to report errors, by publishing the entire book on GitHub (and fine formatted to LeanPub), I am choosing the second path.
This book is not finished. It will never be finished. And that is exactly as it should be.
Because ontology engineering itself is a living discipline. The Semantic Web evolves continuously. Protégé development keep updates. Reasoners improves. New enterprise challenges emerge. And this book will evolve alongside them – with your help!
You are not just a reader. You are a co-creator.
| Action | Link |
|---|---|
| Report an error (no fix) | Open an Issue $\rightarrow$ |
| Propose a correction | Open a Pull Request $\rightarrow$ |
| View the latest version | Repository Main $\rightarrow$ |
| Browse the eBook directory | ebook/ $\rightarrow$ |
Before you close this book and move on with your day, please consider:
Did you find anything in this book that confused you?
That confusion – even if not a “technical error” – is worth reporting. Unclear explanations are a kind of error too. If something took you three readings to understand, that section could be improved.
Did you find a type, a missing word, or an inconsistent term?
Thos are trivial to fix and make the book more professional. Pleae report them.
Did you try an example in Protégé and get a different result than the book described?
That is the most valuable report of all. Real-world testing trumps theoretical writing every time.
Thank you for reading. Thank you for learning. And thank you, in advance, for helping make this book better.
Last updated: 2026-06-12
Repository: https://github.com/yasenstar/protege_pizza
Author contact: GitHub Issues (preferred) or via YouTube channel
The best books are those are acknowledge they are never truly finished – only temporarily improved!