The eNanoMapper ontologies aim to provide a comprehensive suite of ontologies for the nanomaterial safety assessment domain (see http://www.enanomapper.net for project information). The full suite of ontologies can be found assembled by imports in the primary enanomapper.owl
file.
The ontology is being developed and maintained by the following EU H2020 projects (see also the below funding info):
- NanoCommons
- OpenRiskNet (project ended)
- eNanoMapper (project ended)
Other NanoSafety Cluster projects that have contributed by providing feedback and collaborations include NANoREG, NanoReg2, GRACIOUS, and NanoSolveIT.
We import slices from third party ontologies. The Slimmer tool is used to extract the bits we include in the eNanoMapper ontology. The slimmed files can be found in the external folder. The full list of ontologies it includes is:
- Adverse Outcome Pathways Ontology (AOP)
- BioAssay Ontology (BAO)
- Basic Formal Ontology (BFO)
- Cell Culture Ontology (CCONT)
- Chemical Entities of Biological Interest (CHEBI)
- Chemical Information Ontology (CHEMINF)
- Chemical Methods Ontology (CHMO)
- Citation Typing Ontology (CITO)
- Experimental Factor Ontology (EFO)
- Environment Ontology (ENVO)
- FRBR-aligned Bibliographic Ontology (FABIO)
- Gene Ontology (GO)
- Information Artifact Ontology (IAO)
- National Cancer Institute Thesaurus (NCIT)
- NanoParticle Ontology (NPO)
- Ontology of Adverse Events (OAE)
- Ontology of Biological and Clinical Statistics (OBCS)
- Ontology for Biomedical Investigations (OBI)
- Phenotype And Trait Ontology (PATO)
- Semanticscience Integrated Ontology (SIO)
- Uber Anatomy Ontology (UBERON)
- Unit Ontology (UO)
The stable version can be opened in Protégé with the following step:
- File → Open from URL...
- enter the URL http://enanomapper.github.io/ontologies/enanomapper.owl
The development version is opened in the same way, but with a different URL:
- File → Open from URL...
- enter the URL http://enanomapper.github.io/ontologies/enanomapper-dev.owl
During (and after) the eNanoMapper project the ontology was autobuilt using scripts on
a Jenkins server. The main OWL file (enanomapper.owl)
refers to slimmed versions of external ontologies, complemented with internal files adding additional
terms. The extensions are OWL files themselves and you can load them in Protege
and use the internal/Makefile
to run xmllint
on the extensions to see of the OWL
files are well-formed.
The slimming of the external ontologies is done with the Slimmer tool, with these commands (for the BioAssay Ontology):
rm -f *.owl
rm -f *.owl.*
wget -O bao_complete.owl http://www.bioassayontology.org/bao/bao_complete.owl
rm -f bao.props*
rm -f bao.iris*
wget https://raw.githubusercontent.com/enanomapper/ontologies/master/config/bao.props
wget https://raw.githubusercontent.com/enanomapper/ontologies/master/config/bao.iris
java -cp ../Slimmer/target/slimmer-0.0.1-SNAPSHOT-jar-with-dependencies.jar com.github.enanomapper.Slimmer .
The bao.props and bao.iris files contain all the information needed to describe which parts of the BAO ontology is retained in the slimmed version.
Please also check out these tutorials, developed by eNanoMapper, NanoCommons, and OpenRiskNet:
- Update external ontologies
- Download slimmed results from Jenkins workspace (artifacts) for each of the external ontologies
- Replace the old
*-slim.owl
inontologies/external/
- Test if the
enanomapper.owl
can be loaded without errors in Protege- And run the Makefile with
make check
in theinternal/
folder
- And run the Makefile with
- check if the metadata in the enanomapper.owl is up to data (e.g. names of people who submitted PRs)
- Copy the internal ontologies in
ontologies/internal-dev/
toontologies/internal
- Update the owl.versionInfo of
enanomapper.owl
- Update the owl.versionInfo of
enanomapper-dev.owl
- Write markdown for the release with the changes since the previous release
- Release the whole repository in GitHub https://github.com/enanomapper/ontologies/releases
- Update the DOI number for new release: https://zenodo.org/record/260098
The project has had contributions from various European Commission projects. The eNanoMapper project was funded by the European Union’s Seventh Framework Programme for research, technological development and demonstration (FP7-NMP-2013-SMALL-7) under grant agreement no. 604134. NanoCommons has received funding from European Union Horizon 2020 Programme (H2020) under grant agreement nº 731032. OpenRiskNet is funded by the European Commission within Horizon 2020 EINFRA-22-2016 Programme under grant agreement no. 731075. NanoSolveIt has received funding from European Union Horizon 2020 Programme (H2020) under grant agreement no. 814572.