Uberon - a multi-species anatomy ontology
Documents the Uberon multi-species anatomy ontology repository for editors and developers, including taxonomic scope, build status badges, and release instructions.
What this file does
Documents the Uberon multi-species anatomy ontology repository for editors and developers, including taxonomic scope, build status badges, and release instructions.
When to use it
- You are an Uberon ontology editor or developer
- You need to understand the taxonomic scope for term requests
- You want to trigger an automated diff on a pull request
Assumes this stack
Uberon - a multi-species anatomy ontology
This repository contains the ontology source, and is primarily of relevance to Uberon editors/developers.
For an overview of the ontology, plus usage instructions on how to download the compiled versions of the ontology, please visit uberon.org.
A note on the taxonomic scope of Uberon
Uberon has a set of upper level terms that are universal. These are indicated with the common_anatomy tag. However,
Uberon editors will not take requests for terms from outside of the Metazoa. Plant anatomy term requests should be directed to the PO, fungal anatomy terms to FAO.
Uberon also gives preference to anatomy term requests for vertebrates over invertebrates. Wherever possible term requesters are encouraged to work directly with existing invertebrate anatomy ontologies to get the terms they need.
Content
This repository contains the editors version of the ontology (src/ontology/uberon-edit.obo), and the material required to make a release.
GitHub Actions Triggers
To trigger an automated human readable diff, add the following tag to a comment in your pull request: #gogoeditdiff
Editors:
See the file README-editors.txt
What's inside
5 badges, 4 sections (taxonomic scope, content, triggers, editors), 2 links to editor docs
Change this for your project
- Replace
src/ontology/uberon-edit.obowith your own editor file path - Replace
bridge/../README-editors.txtandbridge/../docs/uberon-editor-sop.mdwith your own editor docs - Replace
#gogoeditdiffwith your own pull request trigger tag
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Worth borrowing
- Use badges for CI, DOI, and OBO dashboard status
- Clearly state taxonomic scope to filter term requests
- Provide a simple trigger phrase for automated diffs in PRs
Related Documents
Comprehensive AI Assistant Tools Reference
Lists 80+ tools with MCP server associations, bulk support, parallel capability, resource impact, and execution type for AI agent workflows.
iOS Deployment Guide
Walks through setting up an iOS development environment, building a Tauri app for iOS, and publishing to the App Store or alternative channels.
How to Add Resources to Your FastMCP Server
Teaches how to add static and dynamic MCP resources to a FastMCP server, with six ready-to-copy examples for a GitHub crawler.
PCI Compliance Guide
Explains PCI DSS compliance via tokenization, lists forbidden and allowed data, and provides code examples for BigCommerce and Stripe.