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://www.w3.org/2003/01/geo/wgs84_pos#Point
https://saref.etsi.org/saref4syst/System

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

• This pitfall appears in the following elements:
https://saref.etsi.org/core/hasCommandOfInterest may not be inverse of https://saref.etsi.org/core/isCommandOfInterestOf
https://saref.etsi.org/core/isStateOf may not be inverse of https://saref.etsi.org/core/hasState
https://saref.etsi.org/core/isCommandOfInterestOf may not be inverse of https://saref.etsi.org/core/hasCommandOfInterest
https://saref.etsi.org/core/isActedUponBy may not be inverse of https://saref.etsi.org/core/actsUpon
https://saref.etsi.org/core/hasState may not be inverse of https://saref.etsi.org/core/isStateOf

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://www.w3.org/2006/time#TemporalPosition
https://saref.etsi.org/saref4syst/System
http://www.w3.org/2006/time#TemporalEntity
http://www.w3.org/2004/02/skos/core#narrower
http://www.w3.org/2004/02/skos/core#broader

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://www.w3.org/2004/02/skos/core#broader
https://saref.etsi.org/core/hasTypicalConsumption
https://saref.etsi.org/core/hasApplicableTime
https://saref.etsi.org/core/hasInput
https://saref.etsi.org/core/hasResult
https://saref.etsi.org/core/hasPhenomenonTime
https://saref.etsi.org/core/controls
https://saref.etsi.org/core/hasOptionalCommand
https://saref.etsi.org/core/accomplishes
https://saref.etsi.org/core/isAbout
http://www.w3.org/2004/02/skos/core#narrower
https://saref.etsi.org/core/produces
https://saref.etsi.org/core/isStoredBy
https://saref.etsi.org/core/observes
https://saref.etsi.org/core/isObservedBy
https://saref.etsi.org/core/stores
https://saref.etsi.org/core/hasPrice
https://saref.etsi.org/core/hasTime
https://saref.etsi.org/core/consistsOf
https://saref.etsi.org/core/consumes
https://saref.etsi.org/core/isConsumedBy
https://saref.etsi.org/core/hasMandatoryCommand
https://saref.etsi.org/core/hasOutput
https://saref.etsi.org/core/isAccomplishedBy
https://saref.etsi.org/core/isProducedBy
https://saref.etsi.org/core/isControlledBy
https://saref.etsi.org/saref4envi/encapsulates
https://saref.etsi.org/saref4envi/usesCommunicationInterface
https://saref.etsi.org/saref4envi/hasTransmissionPeriod
https://saref.etsi.org/saref4envi/hasGeometry
https://saref.etsi.org/saref4envi/usesCommunicationProtocol
https://saref.etsi.org/saref4envi/hasComponent
https://saref.etsi.org/saref4envi/isContainedIn
https://saref.etsi.org/saref4envi/hasDigitalRepresentation
https://saref.etsi.org/saref4envi/hasColor
https://saref.etsi.org/saref4envi/affectsProperty
https://saref.etsi.org/saref4envi/projectsLight
https://saref.etsi.org/saref4envi/contains
https://saref.etsi.org/saref4envi/hasLightPoint
http://www.w3.org/2003/01/geo/wgs84_pos#location
https://saref.etsi.org/core/isMeasuredIn
https://saref.etsi.org/saref4envi/isAccesibleThrough
https://saref.etsi.org/saref4envi/isProjectedFromHeight
https://saref.etsi.org/saref4envi/isProjectedInDirection
https://saref.etsi.org/saref4envi/hasFrequencyMeasurement
https://saref.etsi.org/saref4envi/isComponentOf
https://saref.etsi.org/saref4envi/isConnectedTo
https://saref.etsi.org/core/hasDescription
https://saref.etsi.org/core/hasModel
https://saref.etsi.org/core/hasIdentifier
https://saref.etsi.org/core/hasValue
https://saref.etsi.org/saref4envi/hasTag
https://saref.etsi.org/saref4envi/hasVersion
https://saref.etsi.org/saref4envi/hasRevisionNumber
https://saref.etsi.org/saref4envi/hasFlash
https://saref.etsi.org/saref4envi/hasCreationDate
https://saref.etsi.org/core/hasManufacturer
https://saref.etsi.org/saref4envi/hasProjectionAngle
https://saref.etsi.org/saref4envi/hasShield
https://saref.etsi.org/saref4envi/hasIdentifier

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!

The ontology lacks information about equivalent properties (owl:equivalentProperty) in the cases of duplicated relationships and/or attributes.

• The following attributes could be defined as equivalent:
https://saref.etsi.org/saref4envi/hasIdentifier, https://saref.etsi.org/core/hasIdentifier

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:
https://saref.etsi.org/core/isMeasuredByDevice could be inverse of https://saref.etsi.org/core/measuresProperty
https://saref.etsi.org/core/measuresProperty could be inverse of https://saref.etsi.org/core/isControlledByDevice
https://saref.etsi.org/core/controlsProperty could be inverse of https://saref.etsi.org/core/isControlledByDevice

• Sorry, OOPS! has no suggestions for the following relationships without inverse:
https://saref.etsi.org/saref4envi/hasFrequencyMeasurement
https://saref.etsi.org/saref4envi/isProjectedInDirection
https://saref.etsi.org/saref4envi/isProjectedFromHeight
https://saref.etsi.org/saref4envi/isAccesibleThrough
https://saref.etsi.org/core/isMeasuredIn
http://www.w3.org/2003/01/geo/wgs84_pos#location
https://saref.etsi.org/saref4envi/hasLightPoint
https://saref.etsi.org/saref4envi/projectsLight
https://saref.etsi.org/saref4envi/affectsProperty
https://saref.etsi.org/saref4envi/hasColor
https://saref.etsi.org/saref4envi/usesCommunicationProtocol
https://saref.etsi.org/saref4envi/hasGeometry
https://saref.etsi.org/saref4envi/hasTransmissionPeriod
https://saref.etsi.org/saref4envi/usesCommunicationInterface
https://saref.etsi.org/core/hasMeterReadingType
https://saref.etsi.org/core/isValueOfProperty
https://saref.etsi.org/core/hasOutput
https://saref.etsi.org/core/hasSensingRange
https://saref.etsi.org/core/hasMandatoryCommand
https://saref.etsi.org/core/consistsOf
https://saref.etsi.org/core/hasTime
https://saref.etsi.org/core/hasPrice
https://saref.etsi.org/core/represents
https://saref.etsi.org/core/isExecutionOf
https://saref.etsi.org/core/hasFeatureKind
https://saref.etsi.org/core/hasPropertyKind
https://saref.etsi.org/core/hasFunctionKind
https://saref.etsi.org/core/hasMeterReading
https://saref.etsi.org/core/isAbout
https://saref.etsi.org/core/hasPropertyValue
https://saref.etsi.org/core/hasOptionalCommand
https://saref.etsi.org/core/hasThresholdMeasurement
https://saref.etsi.org/core/hasCommandKind
https://saref.etsi.org/core/whenState
https://saref.etsi.org/core/whenPropertyValue
https://saref.etsi.org/core/hasStateKind
https://saref.etsi.org/core/hasPhenomenonTime
https://saref.etsi.org/core/isUsedFor
https://saref.etsi.org/core/hasResult
https://saref.etsi.org/core/hasInput
https://saref.etsi.org/core/hasSensorType
https://saref.etsi.org/core/hasDeviceKind
https://saref.etsi.org/core/hasApplicableTime
https://saref.etsi.org/core/hasTypicalConsumption
https://saref.etsi.org/core/profileHasPrice

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:
https://saref.etsi.org/core/isMeasuredIn

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