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:
› https://saref.etsi.org/saref4ener/LoadControlEventAction
› http://www.w3.org/2006/time#DurationDescription
› http://www.w3.org/2006/time#TemporalEntity

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#DurationDescription
› http://xmlns.com/foaf/0.1/Agent
› http://www.w3.org/2006/time#Interval
› http://www.w3.org/2006/time#TemporalEntity

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:
› https://saref.etsi.org/core/isUsedFor
› https://saref.etsi.org/core/isAbout
› https://saref.etsi.org/core/hasTypicalConsumption
› https://saref.etsi.org/core/isAccomplishedBy
› https://saref.etsi.org/core/consistsOf
› https://saref.etsi.org/core/hasPrice
› https://saref.etsi.org/core/accomplishes
› https://saref.etsi.org/core/hasTime
› https://saref.etsi.org/saref4ener/hasEnergy
› https://saref.etsi.org/saref4ener/hasEnergyValueType
› https://saref.etsi.org/saref4ener/hasUsageForecast
› https://saref.etsi.org/saref4ener/receives
› https://saref.etsi.org/saref4ener/hasEventStateConsume
› https://saref.etsi.org/saref4ener/hasInstructionStatus
› https://saref.etsi.org/saref4ener/hasRecipient
› https://saref.etsi.org/saref4ener/triggersEventActionConsume
› https://saref.etsi.org/saref4ener/hasPowerLimitState
› https://saref.etsi.org/saref4ener/hasAppliedEventActionProduce
› https://saref.etsi.org/saref4ener/hasMessagingType
› https://saref.etsi.org/saref4ener/relatesToCommodityQuantity
› https://saref.etsi.org/saref4ener/hasDevice
› https://saref.etsi.org/saref4ener/hasEffectivePeriod
› https://saref.etsi.org/saref4ener/hasPowerSource
› https://saref.etsi.org/saref4ener/producedBy
› https://saref.etsi.org/saref4ener/includes
› https://saref.etsi.org/saref4ener/hasValueSource
› https://saref.etsi.org/saref4ener/hasEventStateProduce
› https://saref.etsi.org/saref4ener/belongsTo
› https://saref.etsi.org/saref4ener/hasUsage
› https://saref.etsi.org/saref4ener/hasOperationMode
› https://saref.etsi.org/saref4ener/triggersEventActionProduce
› https://saref.etsi.org/saref4ener/hasTier
› https://saref.etsi.org/saref4ener/hasValueType
› https://saref.etsi.org/saref4ener/hasPowerValueType
› https://saref.etsi.org/saref4ener/valueTendency
› https://saref.etsi.org/saref4ener/hasAppliedEventActionConsume
› https://saref.etsi.org/core/hasDescription
› https://saref.etsi.org/core/hasManufacturer
› https://saref.etsi.org/core/hasModel
› https://saref.etsi.org/core/hasTimestamp
› https://saref.etsi.org/core/hasValue
› https://saref.etsi.org/saref4ener/sequenceRemoteControllable
› https://saref.etsi.org/saref4ener/cheapest
› https://saref.etsi.org/saref4ener/slotActivated
› https://saref.etsi.org/saref4ener/hasActiveDurationSumMin
› https://saref.etsi.org/saref4ener/greenest
› https://saref.etsi.org/saref4ener/isPausable
› https://saref.etsi.org/saref4ener/hasDurationDefault
› https://saref.etsi.org/saref4ener/optionalSlot
› https://saref.etsi.org/saref4ener/abnormalConditionOnly
› https://saref.etsi.org/saref4ener/hasValue
› https://saref.etsi.org/saref4ener/hasActiveDurationSumMax
› https://saref.etsi.org/saref4ener/hasDuration
› https://saref.etsi.org/saref4ener/hasEarliestStartTime
› https://saref.etsi.org/saref4ener/serialNumber
› https://saref.etsi.org/saref4ener/requiresUpdate
› https://saref.etsi.org/saref4ener/softwareRevision
› https://saref.etsi.org/saref4ener/brandName
› https://saref.etsi.org/saref4ener/hasActiveDurationMin
› https://saref.etsi.org/saref4ener/hasActivationDelay
› https://saref.etsi.org/saref4ener/hasTemporalResolution
› https://saref.etsi.org/saref4ener/hasLatestEndTime
› https://saref.etsi.org/saref4ener/slotNumber
› https://saref.etsi.org/saref4ener/hasDurationMin
› https://saref.etsi.org/saref4ener/hasOperationModeFactor
› https://saref.etsi.org/saref4ener/hasActiveDurationMax
› https://saref.etsi.org/saref4ener/supportsReselection
› https://saref.etsi.org/saref4ener/maxCyclesPerDay
› https://saref.etsi.org/saref4ener/nodeRemoteControllable
› https://saref.etsi.org/saref4ener/hasEndTime
› https://saref.etsi.org/saref4ener/hasCreationTime
› https://saref.etsi.org/saref4ener/hasStartTime
› https://saref.etsi.org/saref4ener/deviceCode
› https://saref.etsi.org/saref4ener/hasUpdateRate
› https://saref.etsi.org/saref4ener/hardwareRevision
› https://saref.etsi.org/saref4ener/activeSlotNumber
› https://saref.etsi.org/saref4ener/vendorCode
› https://saref.etsi.org/saref4ener/isChangeable
› https://saref.etsi.org/saref4ener/hasIndex
› https://saref.etsi.org/saref4ener/vendorName
› https://saref.etsi.org/saref4ener/deviceName
› https://saref.etsi.org/saref4ener/repetitionsTotal
› https://saref.etsi.org/saref4ener/supportsSingleSlotSchedulingOnly
› https://saref.etsi.org/saref4ener/hasActivationDelayMax
› https://saref.etsi.org/saref4ener/activateSlot
› https://saref.etsi.org/saref4ener/isStoppable
› https://saref.etsi.org/saref4ener/activeRepetitionNumber
› https://saref.etsi.org/saref4ener/totalSequencesCountMax

• 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/core/hasValue, https://saref.etsi.org/saref4ener/hasValue

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

• Sorry, OOPS! has no suggestions for the following relationships without inverse:
› https://saref.etsi.org/saref4ener/presentFillLevel
› https://saref.etsi.org/saref4ener/hasAppliedEventActionConsume
› https://saref.etsi.org/saref4ener/valueTendency
› https://saref.etsi.org/saref4ener/hasConsequenceType
› https://saref.etsi.org/saref4ener/hasPowerValueType
› https://saref.etsi.org/saref4ener/endOfRange
› https://saref.etsi.org/saref4ener/hasValueType
› https://saref.etsi.org/saref4ener/isBlockedBy
› https://saref.etsi.org/saref4ener/isActuatedBy
› https://saref.etsi.org/saref4ener/hasTier
› https://saref.etsi.org/saref4ener/hasRole
› https://saref.etsi.org/saref4ener/hasUpperBoundary
› https://saref.etsi.org/saref4ener/hasPowerEnvelope
› https://saref.etsi.org/saref4ener/hasNumberRange
› https://saref.etsi.org/saref4ener/triggersEventActionProduce
› https://saref.etsi.org/saref4ener/hasOperationMode
› https://saref.etsi.org/saref4ener/hasFailsafeConsumptionMax
› https://saref.etsi.org/saref4ener/hasRoleType
› https://saref.etsi.org/saref4ener/hasFillLevelTargetProfileElement
› https://saref.etsi.org/saref4ener/hasSupplyRange
› https://saref.etsi.org/saref4ener/hasUsage
› https://saref.etsi.org/saref4ener/hasScopeType
› https://saref.etsi.org/saref4ener/belongsTo
› https://saref.etsi.org/saref4ener/leakageRate
› https://saref.etsi.org/saref4ener/hasPowerLimitConsumptionMax
› https://saref.etsi.org/saref4ener/hasActiveOperationMode
› https://saref.etsi.org/saref4ener/hasEventStateProduce
› https://saref.etsi.org/saref4ener/hasTimer
› https://saref.etsi.org/saref4ener/hasPowerSequenceContainer
› https://saref.etsi.org/saref4ener/hasLeakageBehaviourElement
› https://saref.etsi.org/saref4ener/relatesToRequest
› https://saref.etsi.org/saref4ener/limitType
› https://saref.etsi.org/saref4ener/hasValueSource
› https://saref.etsi.org/saref4ener/includes
› https://saref.etsi.org/saref4ener/producedBy
› https://saref.etsi.org/saref4ener/hasRunningCosts
› https://saref.etsi.org/saref4ener/hasTransition
› https://saref.etsi.org/saref4ener/hasPowerSource
› https://saref.etsi.org/saref4ener/hasEffectivePeriod
› https://saref.etsi.org/saref4ener/fillRate
› https://saref.etsi.org/saref4ener/isProtectedBy
› https://saref.etsi.org/saref4ener/relatesToPowerProfileSequenceContainer
› https://saref.etsi.org/saref4ener/toOperationMode
› https://saref.etsi.org/saref4ener/hasDevice
› https://saref.etsi.org/saref4ener/hasIncentive
› https://saref.etsi.org/saref4ener/hasFailsafeProductionMax
› https://saref.etsi.org/saref4ener/startsTimer
› https://saref.etsi.org/saref4ener/relatesToPowerProfileSequence
› https://saref.etsi.org/saref4ener/hasDemandRate
› https://saref.etsi.org/saref4ener/hasContractualProductionMax
› https://saref.etsi.org/saref4ener/relatesToOffer
› https://saref.etsi.org/saref4ener/hasLeakageBehaviour
› https://saref.etsi.org/saref4ener/fromOperationMode
› https://saref.etsi.org/saref4ener/hasNominalConsumption
› https://saref.etsi.org/saref4ener/receivesPowerLimit
› https://saref.etsi.org/saref4ener/hasPowerRange
› https://saref.etsi.org/saref4ener/isLimitedWith
› https://saref.etsi.org/saref4ener/hasLowerBoundary
› https://saref.etsi.org/saref4ener/hasCost
› https://saref.etsi.org/saref4ener/hasEnvelope
› https://saref.etsi.org/saref4ener/relatesToCommodityQuantity
› https://saref.etsi.org/saref4ener/hasMessagingType
› https://saref.etsi.org/saref4ener/hasContractualConsumptionMax
› https://saref.etsi.org/saref4ener/hasPowerSequenceStatus
› https://saref.etsi.org/saref4ener/isBoundTo
› https://saref.etsi.org/saref4ener/hasAppliedEventActionProduce
› https://saref.etsi.org/saref4ener/hasOperationModeElement
› https://saref.etsi.org/saref4ener/hasFillLevelTargetProfile
› https://saref.etsi.org/saref4ener/allowedLimitRange
› https://saref.etsi.org/saref4ener/hasPowerLimitState
› https://saref.etsi.org/saref4ener/hasIncentiveType
› https://saref.etsi.org/saref4ener/hasFillLevelRange
› https://saref.etsi.org/saref4ener/hasActivationPlan
› https://saref.etsi.org/saref4ener/hasConstraints
› https://saref.etsi.org/saref4ener/triggersEventActionConsume
› https://saref.etsi.org/saref4ener/rangeBoundary
› https://saref.etsi.org/saref4ener/hasRecipient
› https://saref.etsi.org/saref4ener/hasPowerLimitProductionMax
› https://saref.etsi.org/saref4ener/hasPowerSequence
› https://saref.etsi.org/saref4ener/hasInstructionStatus
› https://saref.etsi.org/saref4ener/hasSlotValue
› https://saref.etsi.org/saref4ener/hasPowerEnvelopeElement
› https://saref.etsi.org/saref4ener/hasStorage
› https://saref.etsi.org/saref4ener/hasEventStateConsume
› https://saref.etsi.org/saref4ener/hasCommodity
› https://saref.etsi.org/saref4ener/startOfRange
› https://saref.etsi.org/saref4ener/receives
› https://saref.etsi.org/saref4ener/hasUsageForecast
› https://saref.etsi.org/saref4ener/hasNominalProduction
› https://saref.etsi.org/saref4ener/relatesToPowerProfile
› https://saref.etsi.org/saref4ener/hasPowerSequenceElement
› https://saref.etsi.org/saref4ener/hasDemandRateForecast
› https://saref.etsi.org/saref4ener/hasPreviousOperationMode
› https://saref.etsi.org/saref4ener/hasEnergyValueType
› https://saref.etsi.org/saref4ener/hasEnergy
› https://saref.etsi.org/core/actsUpon
› https://saref.etsi.org/core/hasTime
› https://saref.etsi.org/core/isMeasuredIn
› https://saref.etsi.org/core/hasProfile
› https://saref.etsi.org/core/hasPrice
› https://saref.etsi.org/core/consistsOf
› https://saref.etsi.org/core/hasMeterReading
› https://saref.etsi.org/core/hasMeterReadingType
› https://saref.etsi.org/core/hasState
› https://saref.etsi.org/core/represents
› https://saref.etsi.org/core/hasTypicalConsumption
› https://saref.etsi.org/core/hasFunction
› https://saref.etsi.org/core/isAbout
› https://saref.etsi.org/core/hasSensorType
› https://saref.etsi.org/core/hasSensingRange
› https://saref.etsi.org/core/isUsedFor
› https://saref.etsi.org/core/hasThresholdMeasurement
› https://saref.etsi.org/core/controlsProperty

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:
› https://saref.etsi.org/saref4ener/hasSlotValue
› https://saref.etsi.org/saref4ener/hasCost

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