General advice

Dos and don'ts of Ontology building

Don't redefine things. That means there is no need to define something general like chromosome since there are a lot of ontologies where you have import it from. Follow a IRI logic. You don't have influence ont the IRI you import but the terms you define yourself. The most semantic way to define an IRI will be something like http://bio.scai.fraunhofer.de/ontologies/ADO/myTerm . Another way is the use consecutive numbers like http://bio.scai.fraunhofer.de/ontologies/ADO/000211 Don't use UUIDs for IRIs like http://bio.scai.fraunhofer.de/ontologies/ADO/eijei_39_din_3jn_ijdi4_84hfkjsd_08dc9u8hs_oujsc8_ousndcoui

Don’t have redundant annotation properties like hasDefinition, definition or hasdefinition. Choose one from a major ontology and then go for that one. If you import those from other ontologies then you can't do anything about it. But this should not occur too often if you use OBO ontologies. Try to use as many object properties as possible from the relations ontology (RO). [https://www.ebi.ac.uk/ols/ontologies/ro] If you are starting from scratch consider the basic formula ontology (BFO) as a starting ontology

How do I quality check my Ontology ?

Fraunhofer SCAI provides an ontology checker web service you can use to quality check your ontology. (Not published yet 18.6.21)

How is Fraunhofer using Ontologies?

A major task Fraunhofer is using Ontologies for is SCAI View.

Additional Resources

The OBO Foundry provides a lot of useful resources for ontologies in general and how to build ontologies with great quality