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:

Several classes whose identifiers are synonyms are created and defined as equivalent (owl:equivalentClass) in the same namespace. This pitfall is related to the guidelines presented in [2], which explain that synonyms for the same concept do not represent different classes.

• This pitfall appears in the following elements:
› https://saref.etsi.org/saref4ehaw/Contact

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://purl.org/vocommons/voaf#Vocabulary
› http://xmlns.com/foaf/0.1/Agent
› https://saref.etsi.org/saref4envi/Frequency
› https://saref.etsi.org/saref4envi/FrequencyUnit

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://purl.org/vocommons/voaf#Vocabulary
› https://saref.etsi.org/saref4envi/Frequency
› http://xmlns.com/foaf/0.1/Agent
› https://saref.etsi.org/saref4envi/FrequencyUnit
› http://www.w3.org/ns/ssn/systems/Precision

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/hasPrice
› https://saref.etsi.org/core/accomplishes
› https://saref.etsi.org/core/hasTime
› https://saref.etsi.org/core/consistsOf
› https://saref.etsi.org/core/hasDescription
› https://saref.etsi.org/core/hasModel
› https://saref.etsi.org/core/hasTimestamp
› https://saref.etsi.org/core/hasValue
› https://saref.etsi.org/core/hasManufacturer

• 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 relations could be defined as equivalent:
› https://saref.etsi.org/saref4ehaw/hasMeasurement, https://saref.etsi.org/core/hasMeasurement

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/saref4ehaw/hasPosture
› https://saref.etsi.org/saref4ehaw/inCurrentMode
› https://saref.etsi.org/saref4envi/hasFrequencyMeasurement
› https://saref.etsi.org/saref4ehaw/hasParticipant
› https://saref.etsi.org/saref4ehaw/hasHabit
› https://saref.etsi.org/core/consistsOf
› https://saref.etsi.org/saref4ehaw/hasInterface
› https://saref.etsi.org/saref4ehaw/hasLocation
› https://saref.etsi.org/saref4ehaw/hasComputingPower
› https://saref.etsi.org/saref4ehaw/hasAgeCategory
› https://saref.etsi.org/saref4ehaw/hasBanCommunicationType
› https://saref.etsi.org/saref4ehaw/uom
› https://saref.etsi.org/saref4ehaw/hasBanApplicationDomain
› https://saref.etsi.org/saref4ehaw/hasPhysicalLocation
› https://saref.etsi.org/saref4ehaw/hasDataConstraint
› https://saref.etsi.org/saref4ehaw/hasPowerSource
› https://saref.etsi.org/saref4ehaw/hasTimeSeriesMesurement
› https://saref.etsi.org/saref4ehaw/hasImpairment
› https://saref.etsi.org/saref4ehaw/supports
› https://saref.etsi.org/saref4ehaw/isAttachedTo
› https://saref.etsi.org/saref4ehaw/hasPatient
› https://saref.etsi.org/saref4ehaw/hasActivity
› https://saref.etsi.org/saref4ehaw/hasOperatingConstraint
› https://saref.etsi.org/saref4ehaw/hasMeasurement
› https://saref.etsi.org/saref4ehaw/interfaceProtocol
› https://saref.etsi.org/saref4ehaw/contains
› https://saref.etsi.org/saref4ehaw/hasChronicDisease
› https://saref.etsi.org/saref4ehaw/hasDeviceCharacteristic
› https://saref.etsi.org/saref4ehaw/hasResponsibleParty
› https://saref.etsi.org/saref4ehaw/usesBan
› https://saref.etsi.org/saref4ehaw/followsUser
› https://saref.etsi.org/saref4ehaw/presents
› https://saref.etsi.org/saref4ehaw/isDescribedBy
› https://saref.etsi.org/saref4ehaw/hasContact
› https://saref.etsi.org/saref4ehaw/hasData
› https://saref.etsi.org/saref4ehaw/groundingProtocol
› https://saref.etsi.org/saref4ehaw/hasMode
› https://saref.etsi.org/saref4ehaw/hasHub
› https://saref.etsi.org/saref4ehaw/precision
› 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/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

An ontology element (a class, an object property or a datatype property) is used in its own definition. Some examples of this would be: (a) the definition of a class as the enumeration of several classes including itself; (b) the appearance of a class within its owl:equivalentClass or rdfs:subClassOf axioms; (c) the appearance of an object property in its rdfs:domain or range rdfs:range definitions; or (d) the appearance of a datatype property in its rdfs:domain definition.

• This pitfall appears in the following elements:
› https://saref.etsi.org/core/Profile
› https://saref.etsi.org/core/Device

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:
› https://saref.etsi.org/core/Time, https://saref.etsi.org/core/Meter

Suggestions or warnings:

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:

	<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

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:

Evaluation results

Pitfalls detected:

Results for P02: Creating synonyms as classes. Minor1 case 1 case

Results for P04: Creating unconnected ontology elements. Minor 4 cases

Results for P08: Missing annotations. Minor 5 cases

Results for P11: Missing domain or range in properties. Important 13 cases

Results for P12: Equivalent properties not explicitly declared. Important1 case 1 case

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

Results for P24: Using recursive definitions. Important 2 cases

Results for P30: Equivalent classes not explicitly declared. Important1 case 1 case

Suggestions or warnings:

References

[1] Aguado-De Cea, G., Montiel-Ponsoda, E., Poveda-Villalón, M., and Giraldo-Pasmin, O.X. (2015).

[2] Noy, N. F., McGuinness, D. L., et al. (2001).

[3] Gómez-Pérez, A. (1999).

[4] Montiel-Ponsoda, E., Vila Suero, D., Villazón-Terrazas, B., Dunsire, G., Escolano Rodríguez, E., Gómez-Pérez, A. (2011).

[5] Vrandecic, D. (2010).

[6] Gómez-Pérez, A. (2004).

[7] Rector, A., Drummond, N., Horridge, M., Rogers, J., Knublauch, H., Stevens, R., Wang, H., and Wroe, C. (2004).

[8] Hogan, A., Harth, A., Passant, A., Decker, S., and Polleres, A. (2010).

[9] Archer, P., Goedertier, S., and Loutas, N. (2012).

[10] Bernes-Lee Tim. (2006).

[11] Heath, T. and Bizer, C. (2011).

[12] Vatant, B. (2012).

How to cite OOPS!