What is an ontology?

An ontology is a formal, computational representation of knowledge in a particular domain or area of knowledge, such as diseases or anatomy. Terms are arranged in a hierarchy, and the terms and relationships between them are defined using both human readable and machine readable definitions, allowing logical inference and sophisticated queries. They are expressed in a knowledge representation language like RDF or OWL.

I want to request a new term or request a change to Mondo, how do I do so?

All requests should go on our GitHub issue tracker. You will need to create a free GitHub account if you do not already have one.

What kind of information should I include when I create a ticket on the GitHub tracker?

We have guidelines on how to make a good term request. Also note, when you click New Issue on our issue tracker, it will give you options to chose a pre-formatted template that will suggest the type of information to include on a ticket. If none of the templates fit your issue, you can open a blank issue.

How often is Mondo released?

Mondo is released around the first of each month. See the latest release here.

When will I see the latest release of Mondo in OLS?

A new release can be expected in OLS within 7 business days usually.

Am I allowed to change the content in Mondo?

Mondo is a community-driven project and we welcome your feedback and suggested changes. We request that all proposed changed be suggested on GitHub issue tracker, so they can be seen and discussed by the Mondo community. Note, you will need sign up for a free GitHub account, if you do not already have one.

Why and how are terms obsoleted from Mondo?

Why are terms obsoleted

Terms in Mondo may be obsoleted when they are no longer needed, considered out of scope, if they are duplicates, or if they have been obsoleted in a source ontology and merged with another term. Mondo terms are never deleted, instead are obsoleted, so that any MONDO ID ever created remains in the ontology.

To ensure minimal disruption to curation and annotations using Mondo terms, if a term is to be considered for obsoletion in Mondo, we inform users before obsoletion. Our workflow entails 1) adding an ‘obsoletion candidate’ subset tag in Mondo ontology file, 2) including a link to the GitHub ticket that describes the reason for obsoletion (and is a place for community comments), 3) add the date for proposed obsoletion (for example, 2022–01–01), and 4) a comment that indicates the reason and terms to be considered for replacement or an actual replacement term (in the case of a merge). We provide an obsoletion report (for example, see the November report here) with each release and will wait at least two months before obsoleting any class, to allow our users time to update their annotations or make comments (or request the term be kept instead).

Further description and a discussion board on obsoletions is available here. Anyone with a GitHub account can contribute to the discussion.

How are terms obsoleted?

Our workflow for obsoleting terms is evolving to meet the needs of our users. When a term is to be obsoleted (or merged), the term will be annotated with a subset tag obsoletion candidate, and will include an annotation with a link to a relevant GitHub ticket and a comment describing the obsoletion reason. The Mondo curation team will send a report around the first of each month, along with the latest release to inform users of potential obsoletions. Users will have at least 2 months to review the obsoletion candidates. If there are no objections from the community, the curation team will obsolete the term.

How can I collaborate with Mondo?

We welcome the participation of interested colleagues. We anticipate that the structure of Mondo will continue to be refined and completed for some time to come. Groups or persons with expert knowledge in a particular domain of disease(s) are invited to contribute their knowledge on a collaborative basis. See issues that need input from medical experts here. Please contact us to discuss details.

Join the Mondo users group here.

Mondo is the disease ontology for the Monarch Initiative, which is an NIH supported project that integrates, aligns, and re-distributes cross-species gene, genotype, variant, disease, and phenotype data. The Monarch Browser allows users to browse not only human diseases but to see their links to other organisms, genes, phenotypes, and pathways, which may be of special interest to translational researchers.

Is the latest version of Mondo displayed in the Monarch Initiative website?

The latest release of Mondo is not always displayed in the Monarch website, as the release cycles are not in sync. To see the latest version of Mondo online, we recommend using the Ontology Lookup Service (OLS).

Mondo is co-developed with HPO, to ensure interoperability and alignment between the two ontologies and create a more holistic semantic disease resource. A subset of HPO classes are imported into Mondo. HPO terms are used in the logical definitions for the disease terms, where applicable. For example, MONDO:0003337 ‘acute hemorrhagic encephalitis’ is computationally defined as encephalitis and ('disease has feature' some 'Abnormal bleeding') (Abnormal bleeding is an HPO term, HP:0001892).

What is the difference between a disease and a phenotype?

There is a lot of overlap between diseases and phenotypes. Mondo and Human Phenotype Ontology (HPO) define a disease as an entity that has all four of the following features:

  • an etiology (whether identified or as yet unknown)
  • a time course
  • a set of phenotypic features
  • if treatments exist, there is a characteristic response to them

A phenotype (or a phenotypic feature) is a component of a disease, and HPO terms can be used to describe the set of phenotypic features that characterize a disease. There is a grey zone between diseases and phenotypic features. For instance, diabetes mellitus can be conceptualized as a disease, but it is also a feature of other diseases such as Bardet Biedl syndrome. In some cases like this, Mondo may label the disease entity with (disease) after the disease name, to distinguish it from the HPO phenotype term (for example, MONDO:0005466 ‘hypersomnia (disease)’ and HP:0100786 Hypersomnia).

What are disease naming conventions in Mondo?

Please refer to our page on disease naming.

How can we know what’s in OMIM/NCIt/Orphanet/Disease Ontology that’s not in Mondo or what’s in Mondo that is not in OMIM/NCIt/Orphanet/Disease Ontology? Is there an easy way to know this?

Mondo IDs are mapped to OMIM, NCIt, Orphanet and DOIDs, so this can be used to compare coverage.

Since there are several source ontologies, how does Mondo manage the mappings? Is there a resource that contains all of the mappings?

We use semi-automated process to map the sources, but these are always manually evaluated by a curator. The mappings are distributed with the ontology (see releases and we will soon be releasing these using a new format called A Simple Standard for Sharing Ontology Mappings, SSSOM.

How do Mondo and Disease Ontology (DO) differ in terms of their classifications of cancer?

Mondo and DO have slightly different approaches to classifying cancer; Mondo’s approach is based on NCIT’s, and Mondo is more closely aligned with NCIT when it comes to cancer.

How do I cite Mondo?

Please cite: Mungall, Christopher J., et al. 2017 The Monarch Initiative: An Integrative Data and Analytic Platform Connecting Phenotypes to Genotypes across Species. Nucleic Acids Research 45 (D1): D712–22.

Why do we need Mondo?

Please see our blog post that describes why we created Mondo.

Does the definition of ‘equivalent-class’ mapping require that the Mondo/Other relationship is strictly 1:1?

The semantics of owl equivalentClass are such that all concepts are strictly identical in meaning. This always translates to a 1:1 mapping, except when we do a ‘proxy merge’ - we decide that two concepts in an external resource mean the same thing. This is not very common, and the numbers usually come down as we work with the source ontologies to resolve this. See ticket.

What is the difference between MONDO:equivalentTo and skos:exactMatch?

MONDO:equivalentTo and skos:exactMatch conceptually overlap but they have entirely different semantics. Mondo:equivalentTo is much stronger than skos:exactMatch. Mondo uses skos:exactMatch to bridge semantic spaces which conceptually overlap, but are not (necessarily) logically coherent according to OWL semantics. For example, Mondo defines X (an example here of a disease) which is an exact match to Y (add mapped MeSH term) in MeSH, which is not an OWL ontology - trying to apply an equivalent relation with OWL semantics would not make much sense.

Moreover, merging Mondo with another disease ontology, even if both are maintained in OWL, is not guaranteed to produce a coherent result, i.e one that contains no logical errors. This is a very fundamental feature of Mondo: integrating various disease classification to create a harmonised classification. This harmonised classification may, by design, partially disagree with any particular source. Therefore, applying strong OWL semantics with owl:equivalentClass is, usually, inappropriate.

What are the different types of synonyms in Mondo?

  • Exact synonym: an alternative term that has the same meaning.
    name: hereditary Wilms’ tumor
    exact synonym: familial Wilms’ tumor
  • Narrow synonym: a more specific term.
    name: asthma
    exact synonym: exercise-induced asthma
  • Broad synonym: a more general term.
    name: autoimmune hepatitis
    exact synonym: autoimmune liver disease
  • Related synonym: A word of phrase has been used synonymously with the primary term name in the literature, but the usage is not strictly correct. (Note - we have a lot of synonyms in Mondo currently that are marked related but should really be exact and we’re actively working on cleaning this up).
    name: AGAT deficiency
    exact synonym: disorder of glycine amidinotransferase activity