isStepOfPlan
p-plan:isStepOfPlan links a p-plan:Step to the p-plan:Plan which it corresponds to.
Step
A p-plan:Step represents the planned execution activity
Specialization of p-plan:Variable in order to be able to assert specific properties. A wf-invoc:Variable refers to those p-plan:Variables related to the scientific workflow invocation.
Variable
hasOutputVar
p-plan:hasOutputVar binds a p-plan:Step to the p-plan:Variable that will be produced as output in the planned execution
The P-Plan ontology
PROV extension for linking Plans and parts of plans to their respective executions. Created by Daniel Garijo and Yolanda Gil
PROV extension for linking Plans and parts of plans to their respective executions.
Entity
A p-plan:Entity represents the input of the execution of a p-plan:Activity. It corresponds to a p-plan:Variable.
isInputVarOf
p-plan:isInputVarOf links an input variable of a step to the step.
A p-plan:Variable represents a description of the input of the planned Activity (p-plan:Step)
Data property used to link a wf-invoc:Step with the Literal representing the invocation line of the current Step.
has Invocation Line
isOutputVarOf
p-plan:isOutputVarOf is intended to link an output variable of a step to the step.
MultiStep
A multi step is the representation of a plan that appears as a step of another plan.
Data property used to bind a wf-invoc:Variable with the path or URL where the data is available for the execution.
has Data Binding
Wf-invoc is a simple profile of the P-plan ontology to describe how workflow steps are invoked within a workflow execution.
The Workflow Invocation Ontology
Workflow Invocation Ontology, an extension of P-Plan for representing the invocation of the workflow steps when submitting a template to an execution engine.
Workflow Invocation Ontology
hasInputVar
p-plan:hasInputVar binds a p-plan:Step to the p-plan:Variable that takes as input for the planned execution
isSubPlanOfPlan
A p-plan:Plan may be a subplan of another bigger p-plan:Plan. p-plan:isSubPlanOfPlan is used to state the link among the two different plans. Note that if p1 is a p-plan:subPlan of p2, p1will not necessarily be a step of p2. A multistep will represent p1 in p2, and link to p1 with the p-plan.hasStepDecomposition relationship.
Activity
A p-plan:Activity represents the execution process planned in a p-plan:Step
correspondsToVariable
p-plan:correspondsToVariable binds a p-plan:Entity (used by a p-plan:Activity in the execution of a plan) to the p-plan:Variable it represented it in the p-plan:Plan.
Data property used to link a wf-invoc:Step with any particular metadata that will be used in the execution of the Step (e.g., environment requirements, memory, etc.)
has Custom Data
isVariableofPlan
p-plan:IsVariableOfPlan binds a p-plan:Variable to the p-plan:Plan it corresponds to.
Data property used to bind a wf-invoc:Step to the code/library/software used to execute the workflow step.
has Code Binding
correspondsToStep
p-plan:correspondsToStep links a p-plan:Activity to its planned p-plan:Step
Plan
A p-plan:Plan is a specific type of prov:Plan. It is composed of smaller steps that use and produce Variables.
isDecomposedAsPlan
The p-plan:isDecomposedAsPlan relationship binds a p-plan:MultiStep to the p-plan:Plan holding the definition of that step. That is, p-plan:isDecomposedAsPlan links the MultiStep to the Plan sptecification where it is decomposed.
isPrecededBy
Property that asserts which Step preceeds the current one.
Bundle
A p-plan:Bundle is a specific type of prov:Bundle that contains the provenance assertions of the execution of a p-plan:Plan
Specialization of p-plan:Step in order to be able to assert domain specific properties. A wf-invoc:Step refers to those p-plan:Steps related to the scientific workflow invocation.