Henriette's Notes

Home » 2022

Yearly Archives: 2022

Biological ontology use guidelines

This short guideline aims to

  • Explain the difference between a domain ontology versus an application ontology;
  • Provide some guidelines for choosing a single ontology or a small set of ontologies;
  • Explain when to consider creating a new domain ontology; and 
  • Give guidance as to when to create an application ontology.

An upfront disclaimer: I am working at EBI and hence those are the tools I am most familiar with. I have tried where possible to include tools from the biological/biomedical community outside EBI. But I might have missed some. Moreover, this post is not about punting any tools. Rather, it is to describe a general guideline wrt choosing ontologies.

Domain ontologies versus application ontologies

A domain ontology has terms that only concern a single well defined domain and aims to address the general requirements of the community of that domain. It is my understanding that domain ontologies adhere to Principle 5 of the OBO principles. The Data Use Ontology (DUO) is an example of a domain ontology.

An application ontology tends to serve the specific needs for a specific application and often spans different domains, though it may deal with a single domain. The Experimental Factor Ontology (EFO) is an example of an application ontology.

Guidelines for choosing an ontology or ontologies

Here some basic guidelines are given for choosing an ontology. 

  1. Evaluate potential target ontologies using the guidelines of  Ten Simple Rules for Selecting a Bio-ontology and Which biomedical ontologies should we use? Potential target ontologies can be found using tools like the Ontology Lookup Service (OLS), Ontobee and Bioportal. The Open Biological and Biomedical Ontology (OBO) Foundry is a community driven effort to create interoperable biological ontologies. It is therefore a good starting point for identifying viable ontologies that are used and supported by an active community.
  2. Try to identify 1 ontology or as few as possible target ontologies that may address your application needs. This can be done using a tool like Zooma to map strings of text to terms in ontologies based on manual curated data or some machine learning algorithm. Based on these terms a single ontology or multiple target ontologies can be identified. 
  3. Try to map terms from less preferred ontologies to terms in preferred target ontologies using a tool like OxO. If such mappings cannot be found, but to the best of your knowledge term A in ontology A should map to term B in ontology B, consider opening tickets against both ontology A and ontology B to have the respective mappings added. It is only by the community actively contributing to these ontologies that the full FAIR value proposition of ontologies are realised.
  4. As far as possible try to use or contribute to existing ontologies rather than introduce your own ontology. This means when an ontology fits your needs reasonably well, but it is missing some terms required by your use case, it is best to collaborate with the relevant ontology designers to try and add the missing terms. For this purpose most of the ontologies in the biological and biomedical community make use of GitHub Issue trackers where you can open new issues, give your input to existing issues and get latest release information. Remember, the main value proposition of ontologies wrt FAIR principles is realised exactly when an ontology is used, reused and extended as part of a community that has some shared objectives.
  5. Try to keep the number of ontologies you want to use as small as is sensible (that is the smallest set of ontologies that are well aligned with the needs of your use case).  The reason for this is that you will want to engage with the designers of the ontologies you use to extend and amend these ontologies for your use case. The more ontologies you use, the chances are that you will need to communicate with a larger community to affect change for your use case. This may increase development times. However, using an ontology that is not well aligned with your use case will also increase communication and timelines. Thus, the reason for keeping the number of ontologies as small as is sensible.

When to create a domain ontology

If after a review of the existing ontologies you find that your domain is not covered by any of the existing ontologies, you have a strong case for creating your own ontology. At this point you can decide to create the ontology yourself from scratch. When you are just starting down the path of creating your own ontology, it may seem quicker and easier than to have external collaborators involved. However, if you can create your ontology in collaboration with ontology designers that have a deep understanding of the creation and long term maintenance of biological ontologies, it will help you to avoid various pitfalls in ontology creation. Such collaborations can seem long-winded, but will save a lot of time and effort in the long run. A key point to keep in mind when designing an ontology is not only to be concerned with the initial creation of the ontology, but also with its long term maintainability.

When to create an application ontology

Only consider introducing your own application ontology in the following cases:

  1. Your use case spans a number of domains that are served by subsets of terms coming from a number of ontologies. In this case the application typically uses much smaller subsets of terms from the original ontologies. For this scenario an application ontology can be introduced that imports the relevant terms from existing ontologies. An example of this is EFO that is used by a number of teams in EBI. Again, as far as possible terms should be used from existing ontologies rather than introducing terms in your own ontology (see 4 above). Note that when a use case spans a number of domains served by a number of ontologies and the number of terms used from the ontologies are very close to all terms in the ontologies, it is best to use the ontologies directly rather than to introduce your own application ontology.
  2. When you have application specific needs that cannot be addressed by any existing domain or application ontology, then only it may make sense to create your own application ontology.

Final thoughts

  1. As far as possible give preference to re-using ontologies rather than introducing you own.
  2. When you want to embark on creating either a domain or application ontology, I really strongly recommend reaching out the OBO Foundry. They have been developing biological and biomedical ontologies for years now, which means they have learned a lot of lessons over the years. By speaking to them it can help you avoid the typical problems people tend to run into when trying to create their first ontology.

The difference between Schema.org and OWL

In this blog post I describe some of the main differences between Schema.org vocabularies and OWL ontologies, the implications of these differences and the kind of steps you will need to take to translate Schema.org vocabularies to OWL ontologies.

Overall I keep this discussion at a high-level. For in-depth reviews of the differences between Schema.org and OWL I provide relevant links at the end of this post.

Key differences

There are 2 main differences between OWL and Schema.org.

  1. Intended purpose: The primary purpose of Schema.org is to enable sharing of structured data on the internet. The primary purpose of OWL is to enable sophisticated reasoning across the structure of your data.
  2. Difference in language: Due to the difference in purpose, there are substantial differences in language. The main reason being that the language for OWL can be translated into precise mathematical logic axioms, which allows for much richer inferences to be drawn. This is the reason for OWL preferring rdfs:domain/rdfs:range to schema:domainIncludes/schema:rangeIncludes. The benefit of using rdfs:domain/rdfs:range is that they have precise defined mathematical logic meaning, whereas schema:domainIncludes/schema:rangeIncludes do not have mathematical meaning.

What does this mean?

Using Schema.org you could draw some limited inferences. For example a reasoner can determine that the SNOMED concept http://purl.bioontology.org/ontology/SNOMEDCT/116154003 is a schema:Patient which is a schema:Person. But the language used in Schema.org by itself is not rich enough to detect inconsistencies. I.e., there is no way to say that schema:Person is disjoint from schema:Product. This allows for stating myexample:john a schema:Person and myexample:john a schema:Product without a reasoner being able to detect the inconsistency. Using OWL it is possible to state that schema:Person and schema:Product are disjoint.

Does this mean you should prefer OWL to Schema.org? No, not if your intended purpose of your ontology is to share data. Then it is best to use concepts from Schema.org and add the axioms that will provide the inferences you need. If reasoning is not your reason for wanting to use Schema.org/OWL, then just use Schema.org.

Can you translate Schema.org to OWL?

Strictly speaking, since RDF & RDFS is a subset of OWL, Schema.org is an OWL definition already, albeit one with limited reasoning capability. Any “translation” to OWL will mean adding axioms to Schema.org to increase the inferences that can be drawn from Schema.org documents. It is a pity that Schema.org does not (the current link to the OWL file is dead) provide an OWL file with the additional axioms that will enable richer reasoning.

  • Add rdfs:domain and rdfs:range restrictions rather than replacing schema:domainIncludes and schema:rangeIncludes. Replacing schema:domainIncludes and schema:rangeIncludes could result in search engines not finding information.
  • Add owl:disjointWith and owl:disjointObjectProperties respectively for all classes and properties that do not share individuals.
  • By looking at the documentation of Schema.org it gives the impression that classes have attributes. I.e., schema:Person has an attribute schema:givenName. However, there is nothing in the definition of schema:Person that enforces that the schema:Person class must have a schema:givenName attribute. I describe here, here and here how to define “attributes” for classes in a way that can be used by OWL reasoners.

Conclusion

Schema.org is mainly for sharing structured data on the Internet. OWL is used mainly to reason over structured data to determine inconsistencies in the schema.

For in-depth discussions on the differences between Schema.org and OWL I highly recommend reading the papers by Patel-Schneider and Hernich et al.