Phenoscape KB

The Phenoscape Knowledgebase (KB) is an integrated dataset, and software infrastructure and services, bringing together evolutionary data matrices annotated by Phenoscape curators, model organism phenotype and gene expression annotations, and a collection of ontologies providing a common semantic framework. The entire dataset is expressed in the OWL Web Ontology Language, and, when used as a database, stored in an RDF triplestore.

This page describes the in-development version of the KB built on OWL and RDF technologies, not the legacy Phenoscape Knowledgebase built on OBD.

Data sources

Comparative data

Phenoscape

• Evolutionary data matrices annotated by Phenoscape curators

Model organism data

ZFIN

Gene expression and genetic phenotype annotations for zebrafish (Danio rerio). ZFIN data downloads can be found at http://zfin.org/downloads.

• Gene identifiers and names
  • http://zfin.org/downloads/genetic_markers.txt
  • http://zfin.org/downloads/aliases.txt
• Gene expression annotations
  • http://zfin.org/downloads/wildtype-expression.txt
• Genetic phenotype annotations
  • http://zfin.org/downloads/phenoGeneClean.txt

MGI

Gene expression and genetic phenotype annotations for mouse (Mus musculus). MGI data downloads can be found at ftp://ftp.informatics.jax.org/pub/reports/index.html.

• Gene identifiers and names
  • ftp://ftp.informatics.jax.org/pub/reports/MRK_List2.rpt
• Gene expression annotations
  • Custom report provided by Terry Hayamizu. We are working with MGI to establish continually updated downloadable reports.
• Genetic phenotype annotations
  • Custom report provided by Terry Hayamizu. We are working with MGI to establish continually updated downloadable reports.

Xenbase

Gene expression and genetic phenotype annotations for frog (Xenopus laevis and X. tropicalis). Xenbase data downloads can be found at ftp://ftp.xenbase.org/pub.

• Gene identifiers and names
  • ftp://ftp.xenbase.org/pub/GenePageReports/GenePageGeneralInfo_ManuallyCurated.txt
  • ftp://ftp.xenbase.org/pub/GenePageReports/XenbaseGenepageToGeneIdMapping.txt
• Gene expression annotations
  • ftp://ftp.xenbase.org/pub/GenePageReports/GeneExpression_laevis.txt
  • ftp://ftp.xenbase.org/pub//GenePageReports/GeneExpression_tropicalis.txt
• Genetic phenotype annotations
  • A preliminary annotation file has been provided by Xenbase curators. Not yet imported into the KB.

HPO

Genetic phenotype annotations for human (Homo sapiens). HPO data downloads can be found at http://www.human-phenotype-ontology.org/contao/index.php/downloads.html.

• Genetic phenotype annotations
  • http://compbio.charite.de/hudson/job/hpo.annotations.monthly/lastStableBuild/artifact/annotation/genes_to_phenotype.txt

Ontologies

• Uberon cross-species anatomy ontology, with Phenoscape extensions
  • http://purl.obolibrary.org/obo/uberon/ext.owl
  • Imports http://purl.obolibrary.org/obo/uberon/merged.owl
  • Imports http://purl.obolibrary.org/obo/uberon/references/references.owl
• Zebrafish anatomy
  • http://purl.obolibrary.org/obo/zfa.owl
  • Bridge axioms to Uberon: http://purl.obolibrary.org/obo/uberon/bridge/uberon-ext-bridge-to-zfa.owl
• Mouse annotations provided by Terry directly reference Uberon; no mouse-specific ontologies are used at this time.
• Xenopus anatomy
  • http://purl.obolibrary.org/obo/xao.owl
  • Bridge axioms to Uberon: http://purl.obolibrary.org/obo/uberon/bridge/uberon-bridge-to-xao.owl
• Human phenotypes
  • http://purl.obolibrary.org/obo/hp.owl
  • Logical definitions for human phenotype classes (FMA + PATO): http://purl.obolibrary.org/obo/hp/hp-equivalence-axioms.obo
    • This file is converted to OWL after introducing a special header, logical-definition-view-relation: involves, which is used by the oboformat converter.
  • Bridge axioms from FMA (human anatomy) to Uberon: http://purl.obolibrary.org/obo/uberon/bridge/uberon-bridge-to-fma.owl
  • FMA itself is not used (should it be? are there FMA classes used in the HP definitions that don't have direct mappings in the bridge file?)
• Gene Ontology
  • http://purl.obolibrary.org/obo/go.owl
• Biospatial ontology
  • http://purl.obolibrary.org/obo/bspo.owl
• Phenotypic quality ontology
  • http://purl.obolibrary.org/obo/pato.owl
• Vertebrate taxonomy
  • http://purl.obolibrary.org/obo/vto.owl
  • An individual-based taxonomy is generated from this class hierarchy, and both are loaded into the KB.
• Ontology metadata
  • http://purl.obolibrary.org/obo/iao/ontology-metadata.owl

Production tools

All of the inputs to the Phenoscape KB are processed to create a coherent semantic model in OWL. For OWL-based ontology files, processing may be minimal. For input datasets, we have written conversion tools which generate OWL-formatted data from input tables.

Phenoscape OWL tools

This project provides a collection of Scala classes which implement various ontology manipulations, as well as OWL converters for the various data formats used by our data providers.

• https://github.com/phenoscape/phenoscape-owl-tools

Phenoscape builder

This project provides an Ant build script which orchestrates download of data sources and ontologies, conversion to OWL, and pre-reasoning tasks using the Phenoscape OWL tools and other code libraries. The result is a set of OWL files, constituting the Phenoscape KB, which can be loaded together into an RDF triplestore.

• https://github.com/phenoscape/phenoscape-builder

Reasoning process

The OWL ontologies and data files constituting the Phenoscape KB are ultimately loaded into an RDF triplestore for use as a database back-end for the KB web application. The SPARQL query language provides a natural interface to semantic web data; however, support for query-time reasoning within RDF triplestores is severely limited in both performance (in the face of large, complex ontologies) and OWL expressivity. Further, while SPARQL and RDF are perfectly "aligned" with OWL instance data and property assertions, queries that require direct manipulation of the RDF serialization implementation details of OWL class expressions and complex axioms are over-complicated, error-prone, and bound to result in attempts to embed OWL reasoning logic into the structure of the query.