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:


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://ontology.it/itsmo/v1#LifeCycle
http://ontology.it/itsmo/v1#QualitativeValue

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://ontology.it/itsmo/v1#datatypeDependencyProperty

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://ontology.it/itsmo/v1#uses could be inverse of http://ontology.it/itsmo/v1#requires

• Sorry, OOPS! has no suggestions for the following relationships without inverse:
http://ontology.it/itsmo/v1#hasDependencyStrength
http://ontology.it/itsmo/v1#hasSnapshot
http://ontology.it/itsmo/v1#hasTemplate
http://ontology.it/itsmo/v1#hasDependency
http://ontology.it/itsmo/v1#hasPublishingProcess
http://ontology.it/itsmo/v1#hasStatus
http://ontology.it/itsmo/v1#hasDeliverable
http://ontology.it/itsmo/v1#hasDesignProcess
http://ontology.it/itsmo/v1#hasDependentObject
http://ontology.it/itsmo/v1#hasPriority
http://ontology.it/itsmo/v1#hasConfiguration
http://ontology.it/itsmo/v1#hasDesignDocument
http://ontology.it/itsmo/v1#qualitativeServiceProperty
http://ontology.it/itsmo/v1#hasOperationProcess
http://ontology.it/itsmo/v1#hasWarranty
http://ontology.it/itsmo/v1#hasCriticality
http://ontology.it/itsmo/v1#hasProjectOwner
http://ontology.it/itsmo/v1#hasAgreement
http://ontology.it/itsmo/v1#hasProvider
http://ontology.it/itsmo/v1#hasInformed
http://ontology.it/itsmo/v1#hasManagementPlan
http://ontology.it/itsmo/v1#directReportOf
http://ontology.it/itsmo/v1#hasServiceOption
http://ontology.it/itsmo/v1#hasConsole
http://ontology.it/itsmo/v1#hasResponsible
http://ontology.it/itsmo/v1#hasParty
http://ontology.it/itsmo/v1#hasBaseline
http://ontology.it/itsmo/v1#hasConsulted
http://ontology.it/itsmo/v1#hasProvisioningProcess
http://ontology.it/itsmo/v1#hasCustomer
http://ontology.it/itsmo/v1#links
http://ontology.it/itsmo/v1#hasServiceScope
http://ontology.it/itsmo/v1#hasAccountable
http://ontology.it/itsmo/v1#hasUtility
http://ontology.it/itsmo/v1#hasManagementProcess
http://ontology.it/itsmo/v1#hasCMDB
http://ontology.it/itsmo/v1#hasReferenceBaseline
http://ontology.it/itsmo/v1#hasSystemOwner
http://ontology.it/itsmo/v1#hasEditingProcess

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://ontology.it/itsmo/v1#hasEditingProcess
http://ontology.it/itsmo/v1#hasProvisioningProcess

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.

Suggestions or warnings:


The domain and range axioms are equal for each of the following object properties. Could they be symmetric or transitive?
| http://ontology.it/itsmo/v1#uses
| http://ontology.it/itsmo/v1#directReportOf
| http://ontology.it/itsmo/v1#hasConsole
| http://ontology.it/itsmo/v1#requires


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:




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