The Workflow Infrastructure Conservation Using Semantics ontology

Release 28 08 2014

IRI:
http://purl.org/net/wicus
PREFIX:
wicus:
Current version:
2.0
Authors:
Idafen Santana-Perez, Ontology Engineering Group, Universidad Politécnica de Madrid
Imported Ontologies:
http://purl.org/net/wicus-hwspecs
http://purl.org/net/wicus-reqs
http://purl.org/net/wicus-stack
http://purl.org/net/wicus-sva
Other visualisation:
Ontology source
Machester Ontology Browser
Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.0 Generic License.

Abstract

    The WICUS ontology network is a set of ontologies designed to represent the information about the computational infrastructure involved on the execution of computational scientific experiments modelled as scientific workflows.

    The latest OWL encoding of the WICUS ontology network can be found here .
    A ZIP bundle containig all the files that compose the network can be found here

Table of Content

  1. Namespace declarations
  2. Introduction
  3. Object Properties

Namespace declarations

Table 1: Namespaces used in the document
owl<http://www.w3.org/2002/07/owl#>
rdfs<http://www.w3.org/2000/01/rdf-schema#>
terms<http://purl.org/dc/terms/>
wicus<http://purl.org/net/wicus#>
wsva<http://purl.org/net/wicus-sva#>
whw<http://purl.org/net/wicus-hwspecs#>
wstack<http://purl.org/net/wicus-stack#>
wreqs<http://purl.org/net/wicus-reqs#>

Introduction

    WICUS is a set of OWL2 ontologies designed for documenting computational scientific infrastructures, describing their relevant capabilities and how they can be deployed. This ontology network is composed of five ontologies; four domain ontologies, describing the differents concepts of a scientific workflow from the point of view of its infrastructure, plus the ontology described in this document, which links the previous four. This four ontologies are briefly introduced below. For more detailed information about them please refer to their links.


    As mentioned before we integrate these four ontologies into an ontology networks by the means of a set of relations defined in the WICUS ontology and described in this document.

    WICUS relations between the four domain ontologies.
    Figure 1. WICUS relations between the four domain ontologies.

    The following section introduce each of these relations in more detail.

Object Properties

wicus:composedByHardwareSpecop back to ToC or Object Property ToC

IRI: http://purl.org/net/wicus#composedByHardwareSpec

wicus:composedByHardwareSpec links a wreq:HardwareRequirements to a whw:HardwareSpec defining the required hardware characteristics.

has domain
wreqs:HardwareRequirementsc
has range
whw:HardwareSpecc

wicus:composedBySoftwareStackop back to ToC or Object Property ToC

IRI: http://purl.org/net/wicus#composedBySoftwareStack

wicus:composedBySoftwareStack links a wreq:SoftwareRequirements to a wstack:SoftwareStack defining the required software characteristics.

has domain
wreqs:SoftwareRequirementsc
has range
wstack:SoftwareStackc

wicus:hasHardwareSpecsop back to ToC or Object Property ToC

IRI: http://purl.org/net/wicus#hasHardwareSpecs

wicus:hasHardwareSpecs links a wsva:ImageAppliance to a whw:HardwareSpec that defines the image hardware capabilities.

has domain
wsva:ImageAppliancec
has range
whw:HardwareSpecc

wicus:hasSoftwareStackop back to ToC or Object Property ToC

IRI: http://purl.org/net/wicus#hasSoftwareStack

wicus:hasSoftwareStack links a wsva:ScientificVirtualAppliance to a wstack:SoftwareStack defining the software characteristics of a scientific appliance.

has domain
wsva:ScientificVirtualAppliancec
has range
wstack:SoftwareStackc

wicus:requiresHardwareop back to ToC or Object Property ToC

IRI: http://purl.org/net/wicus#requiresHardware

wicus:requiresHardware links a wstack:SoftwareComponent to a whw:HardwareSpec that defines the necessary hardware characteristics for deploying it.

has super-properties
terms:requiresop
has domain
wstack:SoftwareComponentc
has range
whw:HardwareSpecc

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.