scanning


OOPS! is scanning...

OOPS! (OntOlogy Pitfall Scanner!) helps you to detect some of the most common pitfalls appearing when developing ontologies.

To try it, enter a URI or paste an OWL document into the text field above. A list of pitfalls and the elements of your ontology where they appear will be displayed.

Scanner by URI:

Example: http://oops.linkeddata.es/example/swc_2009-05-09.rdf


Scanner by direct input:

Uncheck this checkbox if you don't want us to keep a copy of your ontology.

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 Critical : It is crucial to correct the pitfall. Otherwise, it could affect the ontology consistency, reasoning, applicability, etc.
  • Important Important : Though not critical for ontology function, it is important to correct this type of pitfall.
  • Minor 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 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/DataType
› http://semanticweb.cs.vu.nl/2009/11/sem/Core

Results for P07: Merging different concepts in the same class. 1 case | Minor Minor

A class whose name refers to two or more different concepts is created.

• This pitfall appears in the following elements:
› http://crimeanalytics.it/cem/CrimeAgainstPropertyAndPerson

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

This pitfall appears when any relationship (except for those that are defined as symmetric properties using owl:SymmetricProperty) does not have an inverse relationship (owl:inverseOf) defined within the ontology.

• OOPS! has the following suggestions for the relationships without inverse:
› http://www.w3.org/2000/01/rdf-schema#subClassOf could be inverse of http://semanticweb.cs.vu.nl/2009/11/sem/subTypeOf

• Sorry, OOPS! has no suggestions for the following relationships without inverse:
› http://semanticweb.cs.vu.nl/2009/11/sem/hasPlace
› http://schema.org/publisher
› http://crimeanalytics.it/cem/hasAuthor
› http://schema.org/articleBody
› http://crimeanalytics.it/cem/hasWeapon
› http://crimeanalytics.it/cem/hasOtherSubject
› http://crimeanalytics.it/cem/hasStolenObject
› http://schema.org/headline
› http://schema.org/mentions
› http://crimeanalytics.it/cem/hasVictim
› http://schema.org/inLanguage
› http://schema.org/datePublished
› http://semanticweb.cs.vu.nl/2009/11/sem/hasActor
› http://schema.org/hasurl
› http://semanticweb.cs.vu.nl/2009/11/sem/hasTime
› http://semanticweb.cs.vu.nl/2009/11/sem/eventProperty

Results for P20: Misusing ontology annotations. 6 cases | Minor Minor

The contents of some annotation properties are swapped or misused. This pitfall might affect annotation properties related to natural language information (for example, annotations for naming such as rdfs:label or for providing descriptions such as rdfs:comment). Other types of annotation could also be affected as temporal, versioning information, among others.

• This pitfall appears in the following elements:
› http://crimeanalytics.it/cem/Burglary
› http://crimeanalytics.it/cem/Corruption
› http://crimeanalytics.it/cem/Fraud
› http://crimeanalytics.it/cem/Robbery
› http://crimeanalytics.it/cem/Discrimination
› http://crimeanalytics.it/cem/Theft

Results for P21: Using a miscellaneous class. 1 case | Minor Minor

This pitfall refers to the creation of a class with the only goal of classifying the instances that do not belong to any of its sibling classes (classes with which the miscellaneous problematic class shares a common direct ancestor).

• This pitfall appears in the following elements:
› http://crimeanalytics.it/cem/OtherCrime

Results for P34: Untyped class. 3 cases | Important Important

An ontology element is used as a class without having been explicitly declared as such using the primitives owl:Class or rdfs:Class. This pitfall is related with the common problems listed in [8].

• This pitfall appears in the following elements:
› http://xmlns.com/foaf/0.1/Organization
› http://xmlns.com/foaf/0.1/Person
› http://purl.org/vocommons/voaf#Vocabulary

Results for P36: URI contains file extension. ontology* | Minor Minor

This pitfall occurs if file extensions such as ".owl", ".rdf", ".ttl", ".n3" and ".rdfxml" are included in an ontology URI. This pitfall is related with the recommendations provided in [9].

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

Results for P38: No OWL ontology declaration. ontology* | Important Important

This pitfall consists in not declaring the owl:Ontology tag, which provides the ontology metadata. The owl:Ontology tag aims at gathering metadata about a given ontology such as version information, license, provenance, creation date, and so on. It is also used to declare the inclusion of other ontologies.

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

SUGGESTION: symmetric or transitive object properties. 7 cases

The domain and range axioms are equal for each of the following object properties. Could they be symmetric or transitive?
› http://semanticweb.cs.vu.nl/2009/11/sem/subTypeOf
› http://semanticweb.cs.vu.nl/2009/11/sem/subTypeOf
› http://www.w3.org/2000/01/rdf-schema#subClassOf
› http://semanticweb.cs.vu.nl/2009/11/sem/subEventOf
› http://semanticweb.cs.vu.nl/2009/11/sem/subEventOf
› http://semanticweb.cs.vu.nl/2009/11/sem/hasSubEvent
› http://semanticweb.cs.vu.nl/2009/11/sem/hasSubEvent


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


Important pitfalls were found 
<p>
<a href="http://oops.linkeddata.es"><img
	src="http://oops.linkeddata.es/resource/image/oops_important.png"
	alt="Important 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:

Related papers:

Web services:

Developed by:

OEG logo