Vocabulario para la representación de datos sobre lugares de interés turístico, rutas, viajes, etc.

Title: Vocabulario para la representación de datos sobre lugares de interés turístico, rutas, viajes, etc.
URI: http://vocab.linkeddata.es/datosabiertos/def/hacienda/presupuesto
Description: Vocabulario para la representación de datos de lugares de interés turístico, viajes, rutas, etc., en España Este vocabulario ha sido desarrollado en el contexto del grupo sobre Turismo, Cultura y Ocio, y Comercio de AENOR. El estado del vocabulario es todavía muy inicial y sufrirá cambios Reutiliza términos de varios vocabularios y modelos que actualmente se utilizan para propósitos similares (y por tanto se irá actualizando de acuerdo con la evolución de estos vocabularios), incluyendo: - schema.org - geoNames
License: Creative Commons CC-BY
Languages: es

The following evaluation results have been generated by the RESTFul web service provided by OOPS! (OntOlogy Pitfall Scanner!). OOPS! is a software on development, and we will be happy to receive your feedbak. If you notice any issue in the evaluation, please contact us at oops@delicias.dia.fi.upm.es.

It is obvious that not all the pitfalls are equally important; their impact in the ontology will depend on multiple factors. For this reason, each pitfall has an importance level attached indicating how important it is. We have identified three levels:

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.

Evaluation results

P04. Creating unconnected ontology elements1 case detected. Minor

Ontology elements (classes, object properties and datatype properties) are created isolated, with no relation to the rest of the ontology.

This pitfall affects to the following ontology elements:

http://www.w3.org/2004/02/skos/core#ConceptScheme

P08. Missing annotations8 cases detected. Minor

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].

This pitfall affects to the following ontology elements:

P10. Missing disjointness ontology *Important

The ontology lacks disjoint axioms between classes or between properties that should be defined as disjoint. This pitfall is related with the guidelines provided in [6], [2] and [7].

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

P11. Missing domain or range in properties9 cases detected. Important

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

This pitfall affects to the following ontology elements:

P13. Inverse relationships not explicitly declared10 cases detected. Minor

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.

This pitfall affects to the following ontology elements:

P20. Misusing ontology annotations2 cases detected. Minor

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 affects to the following ontology elements:

P40. Namespace hijacking1 case detected. Critical

It refers to reusing or referring to terms from another namespace that are not defined in such namespace. This is an undesirable situation as no information can be retrieved when looking up those undefined terms. This pitfall is related to the Linked Data publishing guidelines provided in [11]: "Only define new terms in a namespace that you control" and to the guidelines provided in [5].

This pitfall affects to the following ontology elements:

http://creativecommons.org/ns#license

References:

[1] Gómez-Pérez, A. Ontology Evaluation. Handbook on Ontologies. S. Staab and R. Studer Editors. Springer. International Handbooks on Information Systems. Pp: 251-274. 2004.
[2] Noy, N.F., McGuinness. D. L. Ontology development 101: A guide to creating your first ontology. Technical Report SMI-2001-0880, Standford Medical Informatics. 2001.
[3] Rector, A., Drummond, N., Horridge, M., Rogers, J., Knublauch, H., Stevens, R.,; Wang, H., Wroe, C. ''Owl pizzas: Practical experience of teaching owl-dl: Common errors and common patterns''. In Proc. of EKAW 2004, pp: 63–81. Springer. 2004.
[4] Hogan, A., Harth, A., Passant, A., Decker, S., Polleres, A. Weaving the Pedantic Web. Linked Data on the Web Workshop LDOW2010 at WWW2010 (2010).
[5] Archer, P., Goedertier, S., and Loutas, N. D7.1.3 – Study on persistent URIs, with identification of best practices and recommendations on the topic for the MSs and the EC. Deliverable. December 17, 2012.
[6] Heath, T., Bizer, C.: Linked data: Evolving the Web into a global data space (1st edition). Morgan & Claypool (2011).