A small OWL ontology for basic geographic notions, published under the TopBraid Composer namespace and reused by other ontologies through owl:imports.
The URI http://www.topbraidcomposer.org/owl/2006/07/tbcgeo.owl turns up in the headers of ontologies that were built with, or near, TopBraid Composer, TopQuadrant’s Eclipse-based ontology editor. It names a small geography ontology published under that tool’s namespace in 2006, and it usually appears as the object of owl:imports. Most people who meet it are reading someone else’s ontology and want to know what that line is doing.
What the file is
Ontology editors of the mid-2000s shipped with example and utility ontologies, and TopBraid Composer was no exception. The tbcgeo file is one of these: a compact OWL ontology with basic geographic notions that a modeler could import instead of writing them from scratch. Its URI follows a common pattern of the time, with the year and month of publication in the path and the .owl extension on the end.
Small utility ontologies like this are not standards. They were not developed through a standards body, they are not versioned with release notes, and the domain that hosts them may stop serving the file. That matters for anyone who inherits an ontology that imports one.
How owl:imports works
owl:imports is an ontology-level property defined in OWL. Placed in an ontology header, as in the example, it says: this ontology includes the axioms of the named ontology. A tool processing the importing ontology fetches the imported one by its IRI (or by a version IRI), merges its axioms, and does the same for anything that ontology imports in turn. The result is called the imports closure.
| Aspect | Behavior |
|---|---|
| Direction | importing ontology → imported ontology |
| Scope | all axioms, not selected terms |
| Recursion | imports of imports are followed |
| Resolution | by IRI, or via a local catalog that maps IRIs to files |
Using a term from another namespace and importing that namespace’s ontology are different acts. An RDF graph can say ex:site geo:lat "52.1" without importing anything. Importing is needed only when the axioms (class hierarchies, domains, ranges, restrictions) should apply in reasoning.
Reusing small geography ontologies
Geographic notions are a frequent target for reuse because almost every domain needs some: places, coordinates, containment. The W3C Basic Geo vocabulary (http://www.w3.org/2003/01/geo/wgs84_pos#, with geo:lat and geo:long), the GeoNames ontology and OGC GeoSPARQL are widely used examples. For simple metadata, Dublin Core offers dcterms:Box for bounding boxes and ISO 3166 codes for countries without any OWL import at all.
The practical questions before importing any small ontology are the same:
- Will the IRI resolve? If the hosting site goes away, every tool that follows the import fails or loads less than expected. A local catalog file (Protégé reads
catalog-v001.xml) that points the IRI to a saved copy removes the dependency. - What does the import add? A reasoner treats imported axioms as true. An unexpected domain or disjointness axiom can make an otherwise sound ontology inconsistent.
- Is the whole ontology needed? If only two or three terms are used, referencing them without importing, or copying the needed declarations with attribution, keeps the closure small.
Inheriting an ontology that imports tbcgeo
The usual situation is an inherited OWL file whose header names tbcgeo.owl. A sensible first step is to load the ontology in an editor and see whether the import resolves. If it does not, check which geography terms the ontology actually uses; often it is a handful of classes or properties that can be mapped to a maintained vocabulary such as GeoSPARQL or W3C Basic Geo. Where the import must stay for compatibility, keeping a dated local copy under a catalog entry preserves the behavior the original modeler saw.
Example in RDF
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<https://example.org/onto/collections>
a owl:Ontology ;
rdfs:label "Example collections ontology" ;
owl:versionIRI <https://example.org/onto/collections/1.2> ;
owl:imports <http://www.topbraidcomposer.org/owl/2006/07/tbcgeo.owl> .
Questions about TopBraid geography ontology (tbcgeo)
What is the tbcgeo ontology?
It is a small OWL file published under the TopBraid Composer namespace, with 2006/07 in its URI, that provides basic geographic terms. Ontologies built in or alongside TopBraid Composer have imported it to reuse those terms instead of defining their own.
What does owl:imports do?
owl:imports is a statement in an ontology header that names another ontology by IRI. An OWL tool that honors it loads the named ontology and treats its axioms as part of the importing ontology. Imports are followed recursively, producing the imports closure.
What happens if an imported ontology cannot be found?
Behavior depends on the tool. Protégé reports a missing import and can continue without it; reasoners then work on an incomplete set of axioms. Tools typically resolve imports through local catalog files that map ontology IRIs to files on disk.
Is owl:imports the same as using terms from another namespace?
No. Any RDF graph can use terms from another namespace without importing anything. owl:imports goes further: it pulls in the other ontology's axioms, so class hierarchies, domains and ranges from it apply to the importing ontology.
What is TopBraid Composer?
TopBraid Composer is an ontology and RDF editor developed by TopQuadrant. It was built on the Eclipse platform and supported RDFS, OWL, SPARQL and later SHACL. Its namespace was used for example and utility ontologies distributed with the tool.