Evaluation results


There are three levels of importance in pitfalls according to their impact on the ontology:
  • 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.

Pitfalls detected:


The relationship "is" is created in the ontology instead of using OWL primitives for representing the subclass relationship (rdfs:subClassOf), class membership (rdf:type), or the equality between instances (owl:sameAs). When concerning a class hierarchy, this pitfall is related to the guidelines for understanding the "is-a" relation provided in [2].

• This pitfall appears in the following elements:
› http://lemon-model.net/lemon#isA

This pitfall consists in creating an ontology element and failing to provide human readable annotations attached to it. Consequently, ontology elements lack annotation properties that label them (e.g. rdfs:label, lemon:LexicalEntry, skos:prefLabel or skos:altLabel) or that define them (e.g. rdfs:comment or dc:description). This pitfall is related to the guidelines provided in [5].

• The following elements have neither rdfs:label or rdfs:comment (nor skos:definition) defined:
› http://lemon-model.net/lemon#LemonElement
› http://lemon-model.net/lemon#HasPattern

• The following elements have no rdfs:label defined:
› http://lemon-model.net/lemon#ComponentList
› http://lemon-model.net/lemon#HasLanguage

• The following elements have neither rdfs:comment or skos:definition defined:
› http://lemon-model.net/lemon#MorphTransform
› http://lemon-model.net/lemon#MorphPattern
› http://lemon-model.net/lemon#Prototype
› http://lemon-model.net/lemon#generates
› http://lemon-model.net/lemon#example
› http://lemon-model.net/lemon#transform
› http://lemon-model.net/lemon#nextTransform
› http://lemon-model.net/lemon#formVariant
› http://lemon-model.net/lemon#constituent
› http://lemon-model.net/lemon#tree
› http://lemon-model.net/lemon#pattern
› http://lemon-model.net/lemon#rule

Object and/or datatype properties without domain or range (or none of them) are included in the ontology.

• This pitfall appears in the following elements:
› http://lemon-model.net/lemon#isReferenceOf
› http://lemon-model.net/lemon#altRef
› http://lemon-model.net/lemon#tree
› http://lemon-model.net/lemon#extrinsicArg
› http://lemon-model.net/lemon#propertyDomain
› http://lemon-model.net/lemon#propertyRange
› http://lemon-model.net/lemon#hiddenRef
› http://lemon-model.net/lemon#reference
› http://lemon-model.net/lemon#prefRef
› http://lemon-model.net/lemon#value

• 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!

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://lemon-model.net/lemon#senseRelation could be inverse of http://lemon-model.net/lemon#subsense

• Sorry, OOPS! has no suggestions for the following relationships without inverse:
› http://lemon-model.net/lemon#subjOfProp
› http://lemon-model.net/lemon#abstractForm
› http://lemon-model.net/lemon#prefRef
› http://lemon-model.net/lemon#generates
› http://lemon-model.net/lemon#element
› http://lemon-model.net/lemon#example
› http://lemon-model.net/lemon#otherForm
› http://lemon-model.net/lemon#entry
› http://lemon-model.net/lemon#transform
› http://lemon-model.net/lemon#canonicalForm
› http://lemon-model.net/lemon#decomposition
› http://lemon-model.net/lemon#hiddenRef
› http://lemon-model.net/lemon#nextTransform
› http://lemon-model.net/lemon#lexicalForm
› http://lemon-model.net/lemon#topic
› http://lemon-model.net/lemon#context
› http://lemon-model.net/lemon#formVariant
› http://lemon-model.net/lemon#constituent
› http://lemon-model.net/lemon#lexicalVariant
› http://lemon-model.net/lemon#condition
› http://lemon-model.net/lemon#edge
› http://lemon-model.net/lemon#propertyRange
› http://lemon-model.net/lemon#property
› http://lemon-model.net/lemon#propertyDomain
› http://lemon-model.net/lemon#synBehavior
› http://lemon-model.net/lemon#semArg
› http://lemon-model.net/lemon#extrinsicArg
› http://lemon-model.net/lemon#objOfProp
› http://lemon-model.net/lemon#phraseRoot
› http://lemon-model.net/lemon#tree
› http://lemon-model.net/lemon#altRef
› http://lemon-model.net/lemon#pattern
› http://lemon-model.net/lemon#leaf
› http://lemon-model.net/lemon#definition
› http://lemon-model.net/lemon#isA
› http://lemon-model.net/lemon#synArg
› http://lemon-model.net/lemon#marker

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://lemon-model.net/lemon#Form, http://lemon-model.net/lemon#Frame
› http://lemon-model.net/lemon#NodeConstituent, http://lemon-model.net/lemon#Component

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://lemon-model.net/lemon#generates

This pitfall consists in declaring neither the ontology URI nor the xml:base namespace. If this is the case, the ontology namespace is matched to the file location. This situation is not desirable, as the location of a file might change while the ontology should remain stable, as proposed in [12].

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

Suggestions or warnings:




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:




References


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.

Ontology development 101: A guide to creating your first ontology.

Evaluation of Taxonomic Knowledge in Ontologies and Knowledge Bases. Proceedings of the Banff Knowledge Acquisition for Knowledge-Based Systems Workshop. Alberta, Canada.

Style guidelines for naming and labeling ontologies in the multilingual web.

Ontology Evaluation. PhD thesis.

Ontology evaluation. In Handbook on ontologies, pages 251-273. Springer.

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.

Weaving the pedantic web. In Proceedings of the WWW2010 Workshop on Linked Data on the Web, LDOW 2010, Raleigh, USA, April 27, 2010.

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.

“Linked Data - Design issues”. http://www.w3.org/DesignIssues/LinkedData.html

Linked Data: Evolving the Web into a Global Data Space. Morgan & Claypool, 1st edition.

Is your linked data vocabulary 5-star?. http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html


Enter your ontology to scan:

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

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





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} 
	}



OEG logo
ESTIINF logo


Escuela Técnica
Superior de
Ingenieros Informáticos

UPM logo


Universidad
Politécnica
de Madrid