Log in | Register
Navigation
User Group Management
Administration
Credits

Introduction to ontologies

AIM@SHAPE ontologies

Common ontologies
Shape ontology
Tool ontology

Domain ontologies
Virtual Humans ontology
Shape Acquisition and Processing ontology
Product Design ontology

VISIONAIR ontologies
Workflow ontology
Virtual Manufacturing ontology

Medical ontology

The Workflow Ontology

Overview
Activity specifications
Workflow Creation and Visualization
next

Introduction

The ontology for workflows captures workflow related metadata and constitutes an ontology-driven evolution of the metadata in the Workflow Repository. A high level view of the ontology is shown in the following diagram.

The diagram shows the main concepts in the ontology. Even if only static workflows have been implemented in the repository till now, the possibility of storing metadata also for dynamic ones has been taken into account for further researches.

The concept Person Info is shared with the common ontology for shapes and captures information regarding a person that is associated (as creator) with the various workflows that are stored in the repository.

The central concept in the ontology is Workflow, which describes the various workflows that are stored in the repository. As just said, only static workflows (elements of WorkflowStatic) have been developed till now.

A workflow has a purpose, an element of the concept WorkflowDomain: even if the workflow ontology started for storing those workflows useful to describe the process from a CAD model to Virtual Reality, its generality may allow to describe workflows for different domains.

A (static) workflow is described as a sequence of elements of the concept Activity, which specify the steps of the workflow. Their consequentiality is described by the follows and precedes properties. Activities may be either elements of Macro-Activity or of Simple-Activity concepts: an element of the first may be a container for some elements of the second, which become sub-activities of the main activity.

Macro-activities may be or may not be correlated to a functionality, which can be either an element of the concept Functionality shared with the common ontology for tools, or an element of the concept MicroFunctionality, which is a sub-concept of the first and stores new functionalities mainly related with workflows. Micro-functionalities, on the other hand, are mandatorily linked to a functionality, actually representing and extending it.

Functionalities are related to tools, either elements of the concept SoftwareTool, shared with the common ontology for tools, or of the concept Tool, which contains either new tools or copies of existing tools to which some micro-functionality has been related to. In the last case, the new tool is related to its copy by a suitable object property.

next