Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors“Ontology Without Trying” is best read as a practical proposal, not a recognized philosophical doctrine: make the assumptions about what exists that a particular question needs, use them provisionally, and revise them when they stop helping. Ontology, in philosophy, is the study of what it means to exist. In technology, the word also describes an explicit model of concepts and their relationships in a defined domain. Neither use requires you to settle every question about reality before you can think or build.
What does ontology mean?
In philosophy, ontology asks what it means for something to exist and what kinds of things there are. The Cambridge English Dictionary defines it as “the part of philosophy that studies what it means to exist” (Cambridge English Dictionary, accessed September 27, 2026). Questions might include whether numbers, minds, properties, or social institutions exist, and in what sense.
As an Amazon Associate I earn from qualifying purchases.
In information science and software, an ontology is a formal description of the concepts in a particular domain, their properties, and constraints on those properties. The Stanford Protégé guide defines it in terms of classes, properties (also called slots or roles), and restrictions (facets). A model of a library, for example, might define books and authors as classes, a title as a property of a book, and a rule about what values that property can take. That model organizes a domain; by itself, it does not settle the philosophical question of what ultimately exists.
What might “without trying” mean?
The phrase is not established here as the title of a recognized theory or as an attributed slogan. As an interpretation, it suggests resisting the urge to construct a complete account of reality before addressing a specific question. You can state a limited set of assumptions, use them for the task at hand, and remain willing to change them.
#1 Best Overall
This is not a claim that assumptions can be avoided. Even ordinary reasoning depends on distinctions: what counts as an object, an event, a cause, or evidence. The useful move is to make important assumptions visible rather than quietly treating them as final truths. A working model can answer a practical question without pretending to be a universal map of existence.
Philosophical ontology and technical ontology are different tasks
| Question | Philosophical ontology | Technical ontology |
|---|---|---|
| What is being described? | What exists, or what it means to exist. | Concepts in a specified domain, their properties, and constraints. |
| What does a result claim? | A position about reality or categories of being. | A structured representation intended for a task or field. |
| What can revision mean? | Reconsidering the underlying account of what is real. | Changing classes, properties, or restrictions as the domain or purpose becomes clearer. |
The distinction matters because a technical model can be useful without answering metaphysical questions. A database may treat a customer, account, or transaction as a defined kind of record. Those categories support consistent processing, but they need not imply that the model captures the deepest structure of reality.
Rank #2
Do you need an ontology before modeling a domain?
You need enough shared structure to make the model useful, but not necessarily a complete or permanent ontology in advance. The Stanford Protégé guide says there is “no single correct ontology-design methodology” and describes development as iterative. That supports a practical sequence: clarify the purpose, define the concepts needed for it, test the model against examples, and revise it when it fails to represent something important.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Define the task. Specify what the model must help people or software do. A catalog, a clinical record system, and a research knowledge base may need different categories even when they describe overlapping subject matter.
- Name the key concepts. Decide which things, events, or roles need explicit representation for that task. Keep the initial scope narrow enough to examine.
- Specify properties and constraints. Record what information belongs to each concept and what values or relationships are allowed. This makes assumptions inspectable rather than implicit.
- Try real cases. Check whether representative examples fit, whether important distinctions disappear, and whether the model permits nonsensical combinations.
- Revise when the task or evidence calls for it. Add, remove, or redefine concepts when users encounter gaps or the domain changes. Treat revision as part of modeling, not automatically as proof that the first attempt was careless.
How to use assumptions provisionally
A provisional stance is not the same as saying every model is equally good. A model can still be judged by whether it fits the evidence, serves its stated purpose, communicates its categories clearly, and handles relevant cases consistently. What stays open is whether the model should be treated as a final account of reality.
- Mark the scope: say which domain and task the assumptions cover.
- Separate description from commitment: distinguish “the system represents X as a category” from “X is ultimately a fundamental kind of thing.”
- Look for consequences: ask what the assumptions make possible, exclude, or hard to express.
- Keep revision available: change the model if its categories no longer match the problem or obscure a relevant distinction.
R. A. E. Olenius’s reader guide to The Architecture of Consciousness, Part III (December 21, 2025) offers a compatible framing: “Think of what follows as a working translation, not a replacement theory.” The guide also says, “You are not being asked to adopt a worldview. You are being invited to notice a structure.” These are the guide’s formulations, not a canonical definition of “Ontology Without Trying.”
How this relates to Putnam’s Ethics without Ontology
Hilary Putnam’s Ethics without Ontology, published in 2004, is a related comparison, not the source or an alternate name for this topic. In the passage reproduced by The Telos summary, Putnam argues that ethical objectivity need not depend on “a special kind of metaphysical reality.” The point is narrower than rejecting ontology altogether: it challenges the idea that objective ethical claims require positing a distinct metaphysical realm. It illustrates how one can defend objectivity while questioning a particular ontological commitment.
Rank #4
That comparison helps clarify the provisional approach. Declining to posit one special kind of entity does not eliminate the need to explain what makes a claim warranted or meaningful. Likewise, working without a finished metaphysical system does not mean abandoning careful distinctions; it means asking which commitments the argument or model actually needs.
What this approach does—and does not—promise
- It does: make assumptions easier to inspect, support useful models before every foundational question is settled, and leave room to revise categories.
- It does not: provide a complete theory of existence, guarantee that a model is neutral, or show that all ontological questions are unimportant.
“Without trying” is therefore most defensible as a modest method: begin with the smallest explicit account that lets you address the question, see what follows from it, and do not confuse a workable structure with the last word on reality.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
