IRI:
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
Current version:
1.0
Imported Ontologies:
http://www.ontologydesignpatterns.org/cp/owl/sequence.owl (visualise it with LODE)
http://www.ontologydesignpatterns.org/cp/owl/taskexecution.owl (visualise it with LODE)
Other visualisation:
Ontology source

Table of Content

  1. Classes
  2. Annotation Properties
  3. Namespace Declarations

Classes

Abstract merging taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#AbstractMergingTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
An abstract merging task is a merging aimed at 'formally' joining the tasks that are direct successor to a case task. Differently from synchronization tasks, which are expected to be executed, abstract mergings only provide abstract boundaries to a task structure, because in a case task, only one action task is supposed to be executed.
has super-classes
Merging taskc
followsop some Case taskc

Action taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#ActionTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
An action task is an elementary task that sequences non-planning activities, like: moving, exercising forces, gathering information, etc. Planning activites are mental events involving some rational event.
has super-classes
taskc
is disjoint with
Control taskc

Activation taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#ActivationTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A control task aimed at starting an activity. It is specialized either by a beginning task or a reactivation task.
has super-classes
Control taskc
directly precedesop some taskc
is disjoint with
Branching taskc, Deliberation taskc, Loop taskc, Synchro taskc

Boolean case taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#BooleanCaseTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
E.g. a yes-or-no case task, requiring exactly two deliberation tasks.
has super-classes
Case taskc
directly precedesop exactly 2

Branching taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#BranchingTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A task that articulates the plan into an ordered set of tasks.
has super-classes
Control taskc
directly precedesop min 2
has sub-classes
Case taskc, Concurrency taskc
is disjoint with
Activation taskc, Deliberation taskc, Ending taskc, Loop taskc, Synchro taskc

Case taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#CaseTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A case task is a control task branched to a set of tasks that are not executable concurrently. In order to choose which task has to be undertaken, preliminary deliberation tasks should be executed, possibly based on information-gathering and decision rationales.
has super-classes
Branching taskc
directly precedesop some Deliberation taskc
directly precedesop only Deliberation taskc
has sub-classes
Boolean case taskc
is disjoint with
Concurrency taskc

Concurrency taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#ConcurrencyTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A concurrent task is a task branched to a set of tasks executable concurrently -the sequenced perdurants can overlap-, which means that no deliberation task is performed in order to choose among them. A concurrent task has at least one successor synchronization task, which is aimed at waiting for the execution of all -except the optional ones- tasks direct successor to the concurrent -or any order, see below- one.The axioms cannot be expressed fully in OWL-DL (no value mapping available).
has super-classes
Branching taskc
precedesop some Synchro taskc
is disjoint with
Case taskc

Control taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#ControlTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A control task is a task executed during a planning activity, e.g. an activity aimed at (cognitively or via simulation) anticipating other activities. Therefore, control tasks have usually at least one direct successor task (the controlled one), with the exception of ending tasks.The reification of control constructs allows to represent procedural knowledge into the same ontology including controlled action. Besides conceptual transparency and independency from a particular grounding system, a further advantage is enabling the representation of coordination tasks. For example, a manager that coordinates the execution of several related activities can be represented as a role with a responsibility (duty+right) towards some complex task.
has super-classes
taskc
has sub-classes
Activation taskc, Branching taskc, Deliberation taskc, Ending taskc, Loop taskc, Merging taskc
is disjoint with
Action taskc

Decision activityc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#DecisionActivity

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
An activity related to planning. It is supposed to execute a 'case task', and can contain an information gathering activity.
has super-classes
actionc
executes taskop some Case taskc

Decision statec back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#DeliberationState

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A state related to planning. It finalizes the execution of a 'deliberation task', and is preceded by a decision activity.
has super-classes
actionc
executes taskop some Deliberation taskc
followsop some Decision activityc

Deliberation taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#DeliberationTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A deliberation task is a control task that is executed in a deliberation state (a decision taken during a case task execution, e.g. a yes or a no, or a known value, etc.).
has super-classes
Control taskc
is executed inop only Decision statec
directly followsop some Case taskc
is disjoint with
Activation taskc, Branching taskc, Ending taskc, Loop taskc, Synchro taskc

Ending taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#EndingTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
An ending task is a control task that has no successor tasks defined in the plan.
has super-classes
Control taskc
is disjoint with
Branching taskc, Deliberation taskc, Loop taskc, Synchro taskc

Loop taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#LoopTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A loop task is a control task that has as successor an action -or complex- task that sequences at least two distinct activities sharing a minimal common set of properties -they have a MinimalCommonType. Notice that MinimalCommonType cannot be formalised as a first-order predicate, and then neither in OWL-DL. It can be considered a trivial guideline: when sequencing looped actions, choose a definite action class from the ground ontology. Some relations typically hold for loop tasks. Exit condition can be used to state what deliberation task causes to exit the cycle; iteration interval can be used to state how much time should be taken by each iteration of the looped activity; iteration cardinality can be used to state how many times the action should be repeated.
has super-classes
Control taskc
is disjoint with
Activation taskc, Branching taskc, Deliberation taskc, Ending taskc, Synchro taskc

Merging taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#MergingTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A task that joins a set of tasks after a branching.
has super-classes
Control taskc
has sub-classes
Abstract merging taskc, Synchro taskc

Synchro taskc back to ToC or Class ToC

IRI: http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#SynchroTask

is defined by
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl
A synchronization task is a merging aimed at waiting for the execution of all (except the optional ones) tasks that are direct successor to a concurrent or any order task.
has super-classes
Merging taskc
followsop some Concurrency taskc
is disjoint with
Activation taskc, Branching taskc, Deliberation taskc, Ending taskc, Loop taskc

Annotation Properties

commentap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2000/01/rdf-schema#comment

extracted fromap back to ToC or Annotation Property ToC

IRI: http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl#extractedFrom

has authorap back to ToC or Annotation Property ToC

IRI: http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl#hasAuthor

has intentap back to ToC or Annotation Property ToC

IRI: http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl#hasIntent

is defined byap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2000/01/rdf-schema#isDefinedBy

labelap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2000/01/rdf-schema#label

version infoap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2002/07/owl#versionInfo

Namespace Declarations back to ToC

default namespace
http://www.ontologydesignpatterns.org/cp/owl/controlflow.owl#
cpannotationschema
http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl#
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
sequence-owl
http://www.ontologydesignpatterns.org/cp/owl/sequence.owl#
taskexecution-owl
http://www.ontologydesignpatterns.org/cp/owl/taskexecution.owl#
taskrole-owl
http://www.ontologydesignpatterns.org/cp/owl/taskrole.owl#
xsd
http://www.w3.org/2001/XMLSchema#

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