OOPS! Ontology Pitfall Scanner!

I just learned about this tool, which I'm finding very useful.

OOPS: http://www.oeg-upm.net/oops

Below are results when applied on some of the ontologies generated with ORR tools. These results will certainly help improve these tools in future versions.

http://mmisw.org/ont/cf/parameter

This is generated by our conversion tool from the original XML file.

 

Results for P08: Missing annotations.2 cases

Ontology terms lack annotations properties. This kind of properties improves the ontology understanding and usability from a user point of view. 

• The following elements have neither rdfs:label or rdfs:comment defined: 
› http://mmisw.org/ont/cf/parameter/canonical_units 

• The following elements have no rdfs:comment defined: 
› http://mmisw.org/ont/cf/parameter/Standard_Name 

 

 

http://mmisw.org/ont/secoora/parameter

 

This is an ontology generated with the voc2rdf tool in the ORR. 

 

 

Results for P08: Missing annotations.5 cases

Ontology terms lack annotations properties. This kind of properties improves the ontology understanding and usability from a user point of view. 

• The following elements have no rdfs:comment defined: 
› http://mmisw.org/ont/secoora/parameter/Parameter 
› http://mmisw.org/ont/secoora/parameter/Term 
› http://mmisw.org/ont/secoora/parameter/Definition 
› http://mmisw.org/ont/secoora/parameter/Reference 
› http://mmisw.org/ont/secoora/parameter/Units 

Results for P11: Missing domain or range in properties.4 cases

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 appears in the following elements: 
› http://mmisw.org/ont/secoora/parameter/Units 
› http://mmisw.org/ont/secoora/parameter/Reference 
› http://mmisw.org/ont/secoora/parameter/Definition 
› http://mmisw.org/ont/secoora/parameter/Term 

• Tip: Solving this pitfall may lead to new results for other pitfalls and suggestions. We encourage you to solve all cases when needed and see what else you can get from OOPS! 

 

http://mmisw.org/ont/ioos/map_ioos_cf

This ontology is generated by the mapping tool.

 

Results for P08: Missing annotations.7 cases

Results for P10: Missing disjointness [1, 2, 3].ontology*

The ontology lacks disjoint axioms between classes or between properties that should be defined as disjoint. For example, we can create the classes ìOddî and ìEvenî (or the classes ìPrimeî and ìCompositeî) without being disjoint; such representation is not correct based on the definition of these types of numbers. 

*This pitfall applies to the ontology in general instead of specific elements.

Results for P11: Missing domain or range in properties.4 cases

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 appears in the following elements: 
› http://mmisw.org/ont/ioos/parameter/Units 
› http://mmisw.org/ont/ioos/parameter/Term 
› http://mmisw.org/ont/ioos/parameter/Reference 
› http://mmisw.org/ont/ioos/parameter/Definition 

• Tip: Solving this pitfall may lead to new results for other pitfalls and suggestions. We encourage you to solve all cases when needed and see what else you can get from OOPS!