The following evaluation results have been generated by the RESTFul web service provided by OOPS! (OntOlogy Pitfall Scanner!).
It is obvious that not all the pitfalls are equally important; their impact in the ontology will depend on multiple factors. For this reason, each pitfall has an importance level attached indicating how important it is. We have identified three levels:
Ontology terms lack annotations properties. This kind of properties improves the ontology understanding and usability from a user point of view.
This pitfall affects to the following ontology elements:
Relationships and/or attributes without domain or range (or none of them) are included in the ontology. There are situations in which the relation is very general and the range should be the most general concept "Thing". However, in other cases, the relations are more specific and it could be a good practice to specify its domain and/or range. An example of this type of pitfall is to create the relationship "hasWritten" in an ontology about art in which the relationship domain should be "Writer" and the relationship range should be "LiteraryWork". This pitfall is related to the common error when defining ranges and domains described in [3].
This pitfall affects to the following ontology elements:
This pitfall appears when a relationship (except for the symmetric ones) has not an inverse relationship defined within the ontology. For example, the case in which the ontology developer omits the inverse definition between the relations "hasLanguageCode" and "isCodeOf", or between "hasReferee" and "isRefereeOf".
This pitfall affects to the following ontology elements:
The contents of some annotation properties are swapped or misused. An example of this type of pitfall is to include in the Label annotation of the class "Crossroads" the following sentence ���the place of intersection of two or more roads���; and to include in the Comment annotation the word 'Crossroads'.
This pitfall affects to the following ontology elements:
References: