Opmw

9
Date: 14/11/2011 OPMW Daniel Garijo Ontology Engineering Group, Departamento de Inteligencia Artificial. Universidad Politécnica de Madrid Yolanda Gil Information Sciences and Institute University of Southern California, Marina del Rey

description

Brief description of the OPMW ontology for publishing workflow results. The two OPM slides are from the OPM tutorial: http://openprovenance.org/tutorial/ (edit 01-10-2013): OPMW has constantly been evolving since it was released in 2011. Some of the details of this presentation may be out of date. For the latest version please see: http://www.opmw.org/model/OPMW/

Transcript of Opmw

Page 1: Opmw

Date: 14/11/2011

OPMW

Daniel Garijo

Ontology Engineering Group, Departamento de Inteligencia Artificial. Universidad Politécnica de Madrid

Yolanda Gil

Information Sciences and Institute University of Southern California, Marina del Rey

Page 2: Opmw

1

Index of contents

Overview: 1. What are we exporting with OPMW?

• Publish abstract workflow in addition to executed workflow

2. OPM Overview

3. OPMW: Extending OPM to represent abstract workflows • Representing the process • Representing attribution

Page 3: Opmw

2

Abstract workflow and concrete workflow

We export the abstract workflow in addition to the executed workflow

Abstract workflow has conceptual steps and is independent of execution codes

Page 4: Opmw

3

Executed workflow and execution-ready workflow

SigR110293

FList100283

ChList1288

cOutPut09

NonSigResults1 SigResults1

We export the abstract workflow in addition to the executed workflow

Page 5: Opmw

4

OPM Overview

Nodes

• Artifact: Immutable piece of state, which may have a physical embodiment in a physical object, or a digital representation in a computer system.

• Process: Action or series of actions performed on or caused by artifacts, and resulting in new artifacts.

• Agent: Contextual entity acting as a catalyst of a process, enabling, facilitating, controlling, affecting its execution.

A

P

Ag

Page 6: Opmw

5

OPM Overview

Edges

A1 A2

P1 P2 wasTriggeredBy

wasDerivedFrom

A P used(R)

A P wasGeneratedBy(R)

Ag P wasControlledBy(R)

Edge labels are in the past to express that these are used to describe past executions

Page 7: Opmw

6

OPMW: (I) Representing the Process

opmo:account

opmo:

account

opmo: account

opmw:ProcessTemplatetemplateNode1

opmw:

WorkflowTemplatetemplate1

opmw:

ArtifactTemplateartifact1

opmw:ArtifactTemplateoutputArtifact1

ac:AbstractComponentabsComp1

opmw:ProcessInstanceexecutionNode1

opmw:ArtifactInstance

execInput1

opmw:ArtifactInstace

executionOutput1

ac:SpecificComponentspecComp1

opmw:ExecutionAccount

account1

Abstract Workflow Executable Workflow

opmv:Agentuser1

opmo:account

opmo:hasArtifact

opmo:hasArtifact

opmw:hasWorkflowTemplate

opmw:hasArtifactTemplate

opmw:hasProcessTemplate

opmw: hasArtifactTemplate

opmv:wasGeneratedBy opmv:wasGeneratedBy

opmv:used opmv:usedopmv:wasControlledBy

opmw:hasSpecificComponentopmw:hasTemplateComponent

opmo:hasProcess

opmv:Process

opmv:Artifact

opmv:Artifact

opmo:Account

opmo:OPMGraph

opmv:Process

opmv:Artifact

opmv:Artifact

Page 8: Opmw

7

OPMW: (II) Representing Attribution

opmw:WorkflowTemplate

template1

opmw:ExecutionAccount

account1

opmo:Account

opmo:OPMGraph

opmw:hasWorkflowTemplate

opmw:AgentDaniel

“This is thedocumentation

for template1….”

“2”

opmw:createdInWorkflowSystem

opmw:executedInWorkflowSystem

opmw:hasEndTime

opmw:hasStartTimeopmw:hasStatus

dc:rights

opmw:Agent

Pegasus

“1317342560”“1317341784”“SUCCESS”

“http://creativeco

mmons.org/licenses/by-sa/3.0/”

opmw:Agent

Condor

dc:contributor

opmw:

hasDocumentation

opmw:hasVersion

“2011-09-29T15:54:56-07:00”

opmw:lastUpdatedTime

opmw:

AgentPhil

dc:creator

opmw:

AgentWINGS

Page 9: Opmw

Date: 14/11/2011

OPMW

Daniel Garijo

Ontology Engineering Group, Departamento de Inteligencia Artificial. Universidad Politécnica de Madrid

Yolanda Gil

Information Sciences and Institute University of Southern California, Marina del Rey