All Projects → obophenotype → upheno

obophenotype / upheno

Licence: CC0-1.0 license
The Unified Phenotype Ontology (uPheno) integrates multiple phenotype ontologies into a unified cross-species phenotype ontology.

Programming Languages

Makefile
30231 projects
python
139335 projects - #7 most used programming language
shell
77523 projects
scala
5932 projects
ruby
36898 projects - #4 most used programming language
prolog
421 projects

Projects that are alternatives of or similar to upheno

COB
An experimental ontology containing key terms from Open Biological and Biomedical Ontologies (OBO)
Stars: ✭ 23 (-61.67%)
Mutual labels:  obofoundry
SEPIO-ontology
Ontology for representing scientific evidence and provenance information
Stars: ✭ 40 (-33.33%)
Mutual labels:  obofoundry
foodon
The core repository for the FOODON food ontology project. This holds the key classes of the ontology; larger files and the results of text-mining projects will be stored in other repos.
Stars: ✭ 137 (+128.33%)
Mutual labels:  obofoundry
cell-ontology
An ontology of cell types
Stars: ✭ 75 (+25%)
Mutual labels:  obofoundry
dead simple owl design patterns
A simple system for specifying OWL class design patterns for OBO-ish ontologies.
Stars: ✭ 34 (-43.33%)
Mutual labels:  obofoundry
plant-ontology
Repository for the Plant Ontology
Stars: ✭ 45 (-25%)
Mutual labels:  obofoundry
koza
Data transformation framework for LinkML data models
Stars: ✭ 21 (-65%)
Mutual labels:  obofoundry
MAxO
Medical action ontology
Stars: ✭ 26 (-56.67%)
Mutual labels:  obofoundry
knowledge-graph-change-language
Tools for working with KGCL
Stars: ✭ 14 (-76.67%)
Mutual labels:  obofoundry
OMOP2OBO
OMOP2OBO: A Python Library for mapping OMOP standardized clinical terminologies to Open Biomedical Ontologies
Stars: ✭ 55 (-8.33%)
Mutual labels:  obofoundry
biolink-model
Schema and generated objects for biolink data model and upper ontology
Stars: ✭ 83 (+38.33%)
Mutual labels:  obofoundry
agro
AgrO describes agronomic practices, techniques, and variables used in agronomic experiments.
Stars: ✭ 39 (-35%)
Mutual labels:  obofoundry
envo
A community-driven ontology for the representation of environments
Stars: ✭ 106 (+76.67%)
Mutual labels:  obofoundry
PheKnowLator
PheKnowLator: Heterogeneous Biomedical Knowledge Graphs and Benchmarks Constructed Under Alternative Semantic Models
Stars: ✭ 74 (+23.33%)
Mutual labels:  obofoundry
ontobio
python library for working with ontologies and ontology associations
Stars: ✭ 104 (+73.33%)
Mutual labels:  obofoundry
bco
Biological Collections Ontology
Stars: ✭ 17 (-71.67%)
Mutual labels:  obofoundry
mondo
Mondo Disease Ontology
Stars: ✭ 156 (+160%)
Mutual labels:  obofoundry
uberon
An ontology of gross anatomy covering metazoa. Works in concert with https://github.com/obophenotype/cell-ontology
Stars: ✭ 104 (+73.33%)
Mutual labels:  obofoundry
fastobo-py
Faultless AST for Open Biomedical Ontologies in Python.
Stars: ✭ 21 (-65%)
Mutual labels:  obofoundry
pronto
A Python frontend to (Open Biomedical) Ontologies.
Stars: ✭ 202 (+236.67%)
Mutual labels:  obofoundry

Build Status

This repository contains common files ontologies and workflows shared between multiple phenotype ontologies.

See the wiki for additional documentation

Inter-ontology Closest Matches

See mappings/README.md for explanation of fields

Background

Many databases use their own ontology geared towards their species of interest or an area of interest. The purpose of this repository is to provide a mechanism for integrating these together into a unified phenotype ontology. We do this primarily through OWL Axiomatization and OWL Reasoning.

This approach takes advantages of the fact that phenotype ontologies typically follow a compositional structure. If each contributing ontology makes the semantics of this composition transparent through OWL Axioms then a reasoner can piece the ontologies together and find the overarching classification.

For example, if a phenotype ontology A contains a class for limb size, and also provides an OWL axiom that maps onto a decomposed form, for example:

  • A:limb size equivalentTo pato:size and inheres in some limb

And if phenotype ontology B has a class short forelimb, with axiom:

  • B:short forelimb equivalentTo pato:short and inheres in some forelimb

Then a reasoner can infer that B:short forelimb is a subclass of A:limb size

The OWL Axioms we use follow a design pattern called EQ or Entity-Quality descriptions.

Furthermore, if a database C provides a row for a genotype described compositionally, the placement of these phenotypes can also be inferred.

For background on the original formulation, see:

C J Mungall, Georgios Gkoutos, Cynthia Smith, Melissa Haendel, Suzanna Lewis, Michael Ashburner (2010) Integrating phenotype ontologies across multiple species Genome Biology 11 (1)

Exploring uPheno

The Monarch website uses uPheno to group data from multiple species. See for example: https://monarchinitiative.org/phenotype/MP:0003631

You can also query this using Monarch SciGraph services: https://scigraph-ontology.monarchinitiative.org/scigraph/docs/

To understand the mechanics of how uPheno works, we recommend opening the OWL in Protege and exploring with a fast reasoner such as Elk running

The remainder of these docs assumes some familiarity with Protege/OWL

We provide various modules:

  • mammal.owl
  • vertebrate.owl
  • metazoa.owl

Contributing Ontologies

  • mp* - mouse // mammal.owl
  • hp* - human // mammal.owl
  • zp - zebrafish** // vertebrate.owl
  • wbphenotype - C elegans // metazoa.owl
  • dpo* - Drosophila // metazoa.owl
  • fypo* - Fission Yeast // eukaryote.owl

* -- this ontology provides their own OWL axiomatization ** -- separately generated ontology

External Imports Modules

The OWL axiomatization depends on a number of external ontologies, including

  • pato
  • uberon
  • cl
  • species-specific AOs
  • go
  • chebi

Many of these are large, so we create import modules in the upheno ontology purl space

See the imports directory

PURLs

This ontology has the OBO PURL upheno

A redirect at obolibrary.org maps

History

Previously we had various things on:

This was split across multiple github repos

Design patterns

The design patterns are grouped into three higher level groupings:

  1. anatomical entity (anatomical entities (Uberon), cells (CL))
  2. cellular component (from GO)
  3. chemical entity (includes chemicals (CHEBI), proteins (PRO))

Current structure of uPheno 1:

  1. mp-hp-kboom.owl: OBSOLETE
  2. mp-hp.ow: OBSOLETE
  3. upheno_root_alignments.owl: OBSOLETE

Current uPheno structure

  1. upheno.owl (TODO needs to be obsoleted):
    1. metazoa.owl
      1. Worm
        1. OBO:uberon/bridge/cl-bridge-to-wbbt.owl
        2. OBO:uberon/bridge/uberon-bridge-to-wbbt.owl
        3. OBO:wbphenotype/wbphenotype-full.owl
      2. Fly
        1. OBO:uberon/bridge/cl-bridge-to-fbbt.owl
        2. OBO:uberon/bridge/uberon-bridge-to-fbbt.owl
        3. OBO:dpo.owl
        4. OBO:upheno/dpo/dpo-bridge.owl
        5. OBO:upheno/imports/fbbt_phenotype.owl
      3. OBO:upheno/vertebrate.owl
        1. Zebrafish:
        2. OBO:zp.owl
        3. OBO:uberon/bridge/cl-bridge-to-zfa.owl
        4. OBO:uberon/bridge/uberon-bridge-to-zfa.owl
        5. OBO:upheno/imports/zfa_import.owl
        6. OBO:vt.owl (<- this currently points to uPheno, made ticket to change that)
        7. upheno internal:
          1. OBO:upheno/imports/uberon_import.owl
          2. OBO:upheno/mammal.owl
            1. OBO:mp.owl
            2. OBO:hp.owl
            3. upheno internal:
              1. OBO:upheno/hp-mp/mp_hp-align-equiv.owl (REMOVED)
              2. OBO:upheno/upheno_root_alignments.owl (covered, root terms under uPheno:"Phenotype")
              3. OBO:upheno/imports/go_phenotype.owl (TODO)
              4. OBO:upheno/imports/mpath_phenotype.owl (TODO)
              5. OBO:upheno/imports/nbo_phenotype.owl (TODO)
              6. OBO:upheno/imports/uberon_phenotype.owl (TODO)
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].