The latest OWL encoding of the WICUS Workflow Execution Requirements ontology can be found here
owl | <http://www.w3.org/2002/07/owl#> |
rdfs | <http://www.w3.org/2000/01/rdf-schema#> |
wreqs | <http://purl.org/net/wicus-reqs#> |
terms | <http://purl.org/dc/terms/> |
p-plan | <http://purl.org/net/p-plan#> |
wreq:Workflow
, representing a Scientific Workflow, to a wreq:ExecutionEnvironment
defining its dependencies. Depending on whether the steps of the workflow are fully specified in terms of infrastructure or not we distinguish between wreq:ConcreteWorkflow
and wreq:AbstractWorkflow
.
These concepts are related with the wreq:requiresExecutionEnvironment
object property, which extends the terms:requires
. For the purpose of describing the execution infrastructure we consider that a wokflow can be composed of several subworkflows, defining each one of them their own infrastructure description. We do not describe the execution order of these workflows or their inner steps.
This ontology extends some of the concepts of the p-plan ontology. Concretely the p-plan:Plan
and p-plan:Step
classes and the p-plan:isStepOfPlan
object property.
The taxonomy of this ontology is depicted in Fig. 1. For more information about the classes and properties of the ontology check the following sections.
IRI: http://purl.org/net/wicus-reqs#AbstractWorkflow
IRI: http://purl.org/net/wicus-reqs#ConcreteWorkflow
A wreq:ConcreteWorkflow is a specific type of wreq:Workflow in which all its steps are fully specified.
IRI: http://purl.org/net/wicus-reqs#ExecutionEnvironment
A wreq:ExecutionEnvironment represents the computational resources that must be provided to support the execution of a workflow.
IRI: http://purl.org/net/wicus-reqs#HardwareRequirements
A wreq:HardwareRequirements is a specific type of wreq:ExecutionEnvironment, representing the hardware resources that must be provided to support the execution of a workflow.
IRI: http://purl.org/net/wicus-reqs#RequirementLevel
A wreq:RequirementLevel represents the degree of importance of a requirement.
IRI: http://purl.org/net/wicus-reqs#SoftwareRequirements
A wreq:SoftwareRequirements is a specific type of wreq:ExecutionEnvironment, representing the software resources that must be provided to support the execution of a workflow.
IRI: http://purl.org/net/wicus-reqs#Workflow
A wreq:Workflow is a specific type of p-plan:Plan, representing a computational scientific workflow from the point of view of its infrastructure.
IRI: http://purl.org/net/wicus-reqs#WorkflowStep
A wreq:WorkflowStep is a specific type of p-plan:Step, representing a single step of a workflow.
IRI: http://purl.org/net/wicus-reqs#requiresExecutionEnvironment
wreq:requiresExecutionEnvironment is a specific type of dcterms:requires that links a wreq:Worflow to the wreq:ExecutionEnvironment that must be available for executing it.
IRI: http://purl.org/net/wicus-reqs#hasConcreteWorkflow
wreq:hasConcreteWorkflow links an wreq:AbstractWorkflow to the set of wreq:ConcreteWorkflow that implements it.
IRI: http://purl.org/net/wicus-reqs#hasLevel
wreq:hasLevel links a wreq:ExecutionEnvironment to its corresponding wreq:RequirementLevel.
IRI: http://purl.org/net/wicus-reqs#hasSubworkflow
wreq:hasSubworkflow links a wreq:Workflow to the subworkflows that compose it.
IRI: http://purl.org/net/wicus-reqs#isStepOfWorkflow
wreq:isStepOfWorkflow is a specific type of p-plan:isStepOfPlan that relates a wreq:WorkflowStep to the wreqs:Workflow that it belongs to.
This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.
A wreq:AbstractWorkflow is a specific type of wreq:Workflow in which at least one of its steps is not fully specified.