OOPS! - OntOlogy Pitfall Scanner!

Evaluation results

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:

Critical : It is crucial to correct the pitfall. Otherwise, it could affect the ontology consistency, reasoning, applicability, etc.
Important : Though not critical for ontology function, it is important to correct this type of pitfall.
Minor : It is not really a problem, but by correcting it we will make the ontology nicer.

Results for P04: Creating unconnected ontology elements. 2 cases | Minor

Ontology elements (classes, object properties and datatype properties) are created isolated, with no relation to the rest of the ontology.

• This pitfall appears in the following elements:
› http://schema.org/Intangible
› http://purl.org/dc/dcmitype/Collection

Results for P05: Defining wrong inverse relationships. 3 cases | Critical

Two relationships are defined as inverse relations when they are not necessarily inverse.

• This pitfall appears in the following elements:
› http://comicmeta.org/cbo/series may not be inverse of http://comicmeta.org/cbo/seriesOf
› http://comicmeta.org/cbo/contains may not be inverse of http://comicmeta.org/cbo/inBox
› http://comicmeta.org/cbo/adaptation may not be inverse of http://comicmeta.org/cbo/adaptationOf

Results for P08: Missing annotations. 36 cases | Minor

Results for P10: Missing disjointness. ontology* | Important

The ontology lacks disjoint axioms between classes or between properties that should be defined as disjoint. This pitfall is related with the guidelines provided in [6], [2] and [7].

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

Results for P11: Missing domain or range in properties. 20 cases | Important

Results for P13: Inverse relationships not explicitly declared. 65 cases | Minor

Results for P19: Defining multiple domains or ranges in properties. 5 cases | Critical

The domain or range (or both) of a property (relationships and attributes) is defined by stating more than one rdfs:domain or rdfs:range statements. In OWL multiple rdfs:domain or rdfs:range axioms are allowed, but they are interpreted as conjunction, being, therefore, equivalent to the construct owl:intersectionOf. This pitfall is related to the common error that appears when defining domains and ranges described in [7].

• This pitfall appears in the following elements:
› http://comicmeta.org/cbo/creator
› http://comicmeta.org/cbo/state
› http://comicmeta.org/cbo/owner
› http://comicmeta.org/cbo/ownerOf
› http://comicmeta.org/cbo/pageCount

Results for P30: Equivalent classes not explicitly declared. 3 cases | Important

This pitfall consists in missing the definition of equivalent classes (owl:equivalentClass) in case of duplicated concepts. When an ontology reuses terms from other ontologies, classes that have the same meaning should be defined as equivalent in order to benefit the interoperability between both ontologies.

• The following classes might be equivalent:
› http://comicmeta.org/cbo/Publication, http://comicmeta.org/cbo/Issue
› http://comicmeta.org/cbo/Character, http://comicmeta.org/cbo/Role, http://comicmeta.org/cbo/Quality
› http://comicmeta.org/cbo/Event, http://comicmeta.org/cbo/Issue

Results for P31: Defining wrong equivalent classes. 1 case | Critical

Two classes are defined as equivalent, using owl:equivalentClass, when they are not necessarily equivalent.

• The following classes might not be equivalent:
› http://comicmeta.org/cbo/Issue, http://schema.org/ComicIssue

SUGGESTION: symmetric or transitive object properties. 19 cases

According to the highest importance level of pitfall found in your ontology the conformace bagde suggested is "Critical pitfalls" (see below). You can use the following HTML code to insert the badge within your ontology documentation:

<p>
<a href="http://oops.linkeddata.es"><img
	src="http://oops.linkeddata.es/resource/image/oops_critical.png"
	alt="Critical pitfalls were found" height="69.6" width="100" /></a>
</p>

References:

[1] Aguado-De Cea, G., Montiel-Ponsoda, E., Poveda-Villalón, M., and Giraldo-Pasmin, O.X. (2015). Lexicalizing Ontologies: The issues behind the labels. In Multimodal communication in the 21st century: Professional and academic challenges. 33rd Conference of the Spanish Association of Applied Linguistics (AESLA), XXXIII AESLA.
[2] Noy, N. F., McGuinness, D. L., et al. (2001). Ontology development 101: A guide to creating your first ontology.
[3] Gómez-Pérez, A. (1999). Evaluation of Taxonomic Knowledge in Ontologies and Knowledge Bases. Proceedings of the Banff Knowledge Acquisition for Knowledge-Based Systems Workshop. Alberta, Canada.
[4] Montiel-Ponsoda, E., Vila Suero, D., Villazón-Terrazas, B., Dunsire, G., Escolano Rodríguez, E., Gómez-Pérez, A. (2011). Style guidelines for naming and labeling ontologies in the multilingual web.
[5] Vrandecic, D. (2010). Ontology Evaluation. PhD thesis.
[6] Gómez-Pérez, A. (2004). Ontology evaluation. In Handbook on ontologies, pages 251-273. Springer.
[7] Rector, A., Drummond, N., Horridge, M., Rogers, J., Knublauch, H., Stevens, R., Wang, H., and Wroe, C. (2004). Owl pizzas: Practical experience of teaching owl-dl: Common errors & common patterns. In Engineering Knowledge in the Age of the Semantic Web, pages 63-81. Springer.
[8] Hogan, A., Harth, A., Passant, A., Decker, S., and Polleres, A. (2010). Weaving the pedantic web. In Proceedings of the WWW2010 Workshop on Linked Data on the Web, LDOW 2010, Raleigh, USA, April 27, 2010.
[9] Archer, P., Goedertier, S., and Loutas, N. (2012). D7. 1.3-study on persistent URIs, with identification of best practices and recommendations on the topic for the Mss and the EC. PwC EU Services.
[10] Bernes-Lee Tim. (2006). “Linked Data - Design issues”. http://www.w3.org/DesignIssues/LinkedData.html
[11] Heath, T. and Bizer, C. (2011). Linked Data: Evolving the Web into a Global Data Space. Morgan & Claypool, 1st edition.
[12] Vatant, B. (2012). Is your linked data vocabulary 5-star?. http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html

How to cite OOPS!

Poveda-Villalón, María, Asunción Gómez-Pérez, and Mari Carmen Suárez-Figueroa. "OOPS!(Ontology Pitfall Scanner!): An on-line tool for ontology evaluation." International Journal on Semantic Web and Information Systems (IJSWIS) 10.2 (2014): 7-34.

BibTex:

@article{poveda2014oops,
 title={{OOPS! (OntOlogy Pitfall Scanner!): An On-line Tool for Ontology Evaluation}},
 author={Poveda-Villal{\'o}n, Mar{\'i}a and G{\'o}mez-P{\'e}rez, Asunci{\'o}n and Su{\'a}rez-Figueroa, Mari Carmen},
 journal={International Journal on Semantic Web and Information Systems (IJSWIS)},
 volume={10},
 number={2},
 pages={7--34},
 year={2014},
 publisher={IGI Global}
}

Please, help us making OOPS! better. Feedback is more than welcome!
In addition, you can also suggest new pitfalls so that they can be detected in future evaluations.

Want to help?

Documentation:

Web services:

REST Web Service

Developed by:

Follow @OOPSoeg