The WICUS Workflow Execution Requirements ontology


Title
The WICUS Workflow Execution Requirements ontology
URI
http://purl.org/net/wicus-reqs
Description
The WICUS Workflow Execution Requirements ontology relates a Scientific Workflow to the execution requirements and dependencies for executing it. This ontology is part of the WICUS Ontology network.
License
Creative Commons CC-BY-NC-SA
Creation Date
2013-06-14
Last modified
2013-07-08
Languages
en

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

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:

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:


References: