DataTerminology.comNEW
Also known as: BFO
A top-level ontology distinguishing continuants and occurrents to support scientific domains.
DESCRIPTION
Basic Formal Ontology is an upper ontology that provides high-level categories and relations to align domain ontologies. It distinguishes continuants (enduring entities) from occurrents (processes, events) and supports scientific data integration. BFO is widely used across OBO Foundry ontologies, promoting interoperability and rigorous modeling. It is implemented in OWL and has formal documentation and releases.
ALTERNATIVE DEFINITIONS
Basic Formal Ontology
BFO is a top-level ontology that provides a framework for domain ontologies by distinguishing continuant entities from occurrent entities.
Highlights the continuant–occurrent dichotomy central to BFO’s structure.
OBO Foundry
The Basic Formal Ontology (BFO) is an upper-level ontology used to support information integration across scientific domains.
Emphasizes BFO’s role in integrating scientific information within OBO Foundry.
RELATED TERMS
SUMO OBO Foundry Knowledge Representation Upper Ontology Continuant Occurrent Universal OWL
COMPETING TERMS
DOLCE Suggested Upper Merged Ontology
RELATIONS
- Broader: Formal Ontology Upper Ontology
- Conforms to: OWL
KNOWLEDGE AREAS
Semantic & Knowledge Modeling Data Modeling
TARGET AUDIENCE
Data Modeler Data Architect Information Analyst Data Management Consultant
EXTERNAL SOURCES
- Wikipedia - Basic Formal Ontology
- Basic Formal Ontology - Official site and documentation
- OBO Foundry - BFO overview and governance
- BFO Ontology GitHub - Source and releases for BFO
TOP QUESTIONS
Why use Basic Formal Ontology in scientific modeling?
BFO provides shared upper-level categories that promote interoperability among domain ontologies, reducing ambiguity and improving data integration.
Category: Relevancy
How does Basic Formal Ontology distinguish entities?
It separates continuants (enduring entities) and occurrents (temporal processes), guiding consistent ontological commitments.
Category: Overview
What’s a common mistake when adopting Basic Formal Ontology?
Misclassifying processes as continuants or vice versa. Carefully analyze temporal characteristics before alignment.
Category: Mistakes
What risks exist with inconsistent upper ontology mappings?
Interoperability and query reasoning suffer; data integration across ontologies becomes fragile or incorrect.
Category: Risks
How does Basic Formal Ontology compare to DOLCE and SUMO?
All are upper ontologies, but they differ in philosophical commitments and modeling emphasis. Choose based on domain needs and ecosystem alignment.
Category: Alternatives
What is a hot topic around Basic Formal Ontology?
Formalizing provenance and roles, and improving tooling for OWL reasoning and validation across OBO ontologies.
Category: Topic
How to apply Basic Formal Ontology to a domain ontology?
Map domain classes to BFO categories, reuse relations, and validate with competency questions and reasoners.
Category: Requirements
Where to learn Basic Formal Ontology fundamentals?
Study official docs, OBO tutorials, and OWL reasoning exercises. Start with small modeling examples.
Category: Example
What’s the biggest misunderstanding about Basic Formal Ontology?
That it prescribes all domain classes. BFO provides the upper-level scaffold; domain ontologies define specific concepts.
Category: Misunderstanding