The WICUS Software Stack ontology

The WICUS Software Stack ontology
The WICUS Software Stack ontology have been developed to describe the software elements of a computational resource. These descriptions can be used to describe both, the already deployed software components and the software requiremens of a workflow. This ontology is part of the WICUS Ontology network.
Creative Commons CC-BY-NC-SA
Creation Date
Last modified

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! 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:

It is crucial to correct the pitfall. Otherwise, it could affect the ontology consistency, reasoning, applicability, etc.
Though not critical for ontology function, it is important to correct this type of pitfall.
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:

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: