OBO Foundry & the Gene Ontology

How life science coordinates dozens of interoperable, BFO-anchored ontologies.

0/2 done

Theory

A federation of ontologies that actually fit together

Biology and biomedicine run on the OBO Foundry — a community of open, interoperable ontologies built to shared principles. The flagship is the Gene Ontology (GO), which describes gene products by their molecular functions, biological processes and cellular components — and is one of the most-used resources in all of science.

  • Shared principles — OBO ontologies commit to openness, a common IRI scheme (http://purl.obolibrary.org/obo/...), clear definitions, and orthogonality: each ontology owns its domain so they compose instead of overlapping. GO owns gene function; ChEBI owns chemicals; Uberon owns anatomy; DOID owns diseases.
  • A common upper ontology — most OBO ontologies anchor to BFO (Basic Formal Ontology), which is why they interoperate: shared top-level distinctions (continuant vs occurrent, etc.) make cross-ontology axioms coherent.
  • Annotation at scale — GO's real payload is annotations: millions of statements linking gene products to GO terms, with evidence codes recording how each was established (experiment vs inference).
  • Tooling — ontologies are authored in OWL, distilled to OBO format, browsed in OLS / BioPortal, and edited with Protégé / ROBOT pipelines.

Use Case Example: A lab runs an experiment and gets a list of over-expressed genes. GO enrichment analysis asks 'which biological processes are over-represented?' by rolling the genes up GO's is-a/part-of hierarchy — turning a raw gene list into interpretable biology, all because everyone annotates against the same governed ontology.

Analogy

OBO Foundry is a federation with a shared constitution. Independent states (GO for function, ChEBI for chemicals, Uberon for anatomy) each govern their own territory, but all sign up to the same constitution (open licences, shared IRIs, a common upper ontology). Because they agreed the ground rules once, a treaty between any two — a cross-ontology axiom — just works, instead of every pair negotiating from scratch.

A BFO-anchored federation

Click a node to focus its neighbourhood · drag to pan · scroll to zoom

Orthogonal ontologies on a shared upper layer

Each OBO ontology owns one domain; BFO underneath keeps them coherent so they compose.

Field guide — health/life licensing & vocabulary

Health and life-science licensing field guide

Healthcare standards are where vocabulary rights matter most because real terms can be clinically and commercially sensitive.

StandardWhat is safe to say in demosWhat needs care in production
SNOMED CTgrammar, architecture, placeholder SCTIDs, high-level role of concepts/descriptions/relationshipsreal SCTIDs/terms/definitions/hierarchy often require affiliate/member licence and jurisdiction review
ICDrole as billing/epidemiology classificationedition, country modification, and use rights vary
LOINClab/observation code rolecheck Regenstrief licence/terms and attribution requirements
HL7 FHIRexchange-resource pattern and profilesimplementation guides can be jurisdiction/vendor-specific
IDMPstructure: MPID/PhPID/Substance/PCID and SPOR ideaISO texts are paywalled; regulator implementation data may have its own terms
GO/OBOopen ontology and annotation patternkeep attribution, evidence, version and source; individual OBO ontologies can differ in exact licence

The mental model: SNOMED says what the clinician meant, ICD says how it is classified for reporting/billing, LOINC says which observation was measured, FHIR carries the data, IDMP identifies the medicine, and GO/OBO explains biological function with evidence.

Reflect

OBO Foundry is the most successful large-scale federation of ontologies in existence — proof that the hard part isn't any one ontology, but agreeing the shared rules (open, orthogonal, BFO-anchored) that let dozens of them compose.

  • What does 'orthogonality' buy a community of ontology authors — and what does it cost them?
  • Where in your domain do overlapping vocabularies fight over the same terms for lack of a shared rulebook?

Reading in progress · 0 of 2 activities done