OBO Foundry
- Stage boundary
- No direct role is recorded for Acquire, Exchange.
- Known limitation
- Coverage and maintenance vary by ontology; overlap, versioning, and term-selection policy still require local stewardship.
Decision support
Compare standards by the job they do
Place up to three profiles side by side. Focus on architectural role, evidence, and the first limitation to test—not on finding a single all-purpose standard.
Working set
Choose profiles
1 of 3 selected
OBO FoundryOntology ecosystem
Decision lens
Compare roles before you compare maturity.
The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”
- Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
- Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
- Test the boundary
Read what each option leaves unresolved before judging maturity, confidence, or implementation fit.
Three-part assessment
See the reach, the gaps, and the evidence.
Read left to right. Lifecycle reach comes first; maturity remains an editorial roll-up, not certification.
01 · Lifecycle reach
Where each profile contributes directly
Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.
| Profile | Plan | Acquire | Harmonize | Exchange | Learn + reuse |
|---|---|---|---|---|---|
| OBO FoundryOntology ecosystem | OBO Foundry has a direct role in Plan. | OBO Foundry has no direct role recorded in Acquire. | OBO Foundry has a direct role in Harmonize. | OBO Foundry has no direct role recorded in Exchange. | OBO Foundry has a direct role in Learn + reuse. |
Direct role recordedNo direct role recorded
02 · Boundaries
What each option does not cover
These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.
03 · Detailed assessment
Check the fit and evidence behind the map
Use the source, status, and limitation together. A higher maturity label does not erase a scope mismatch.
| Assessment | OBO FoundryOBO Foundry |
|---|---|
| Purpose & coverage | A family of interoperable biological and biomedical ontologies governed by principles for openness, scope, identifiers, relations, and maintenance. Best fitSemantic annotation, knowledge graphs, terminology normalization, and cross-dataset integration. |
| Readiness stages | PlanHarmonizeLearn + reuse |
| AI-ready contribution | Stable identifiers and logical relationships support semantic features and retrieval, but ontology choice can encode unwanted granularity or bias. |
| First limitation to test | Coverage and maintenance vary by ontology; overlap, versioning, and term-selection policy still require local stewardship. |
| Evidence | E1 + E3 High confidence Formal statusEvolving principles + live registry ReviewSource-checked |
| Maturity | Established Established ecosystem; assess each ontology separately |
| Sources & links | OBO Foundry principles (opens in a new tab)Read full profile |