Non-Ontological Resource Metadata Vocabulary


Title
Non-Ontological Resource Metadata Vocabulary
URI
http://vocab.linkeddata.es/normv
Description
This vocabulary allows (1) describing the non-ontological resource available, (2) including in the ontology generated the provenance information by extending the Ontology Metadata Vocabulary
Creation Date
2012-01-24

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.

OOPS! logoIt 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

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:

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

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:

An ontology element is used as a class without having been explicitly declared as such using the primitives owl:Class or rdfs:Class. This pitfall is related with the common problems listed in [8].

This pitfall affects to the following ontology elements:


References: