Provenance challenge

Second provenance challenge design overview

This page describes our approach to answer the queries of the Second Provenance Challenge

We have developed a new, general API for querying provenance models used by different scientific workflow systems.

Scientific Workflow Provenance Data Model (SWPDM): Overview

The SWDM aims to capture entities and relationships that are relevant to both the definition and execution of workflows. The goal is to define a general model that is able to represent provenance information obtained by different workflow systems.

Module definition is a description of a processor that takes inputs and generates outputs.

Workflow definition is a description of a simple workflow that contains modules and connections between them through ports. It also contains the evolution of the workflow through a parent relation as used by VisTrails.

Execution log is the information about a workflow execution. It contains information about the processors that were executed and the data items that were created.

Model Entities

name	description
dataitem	A dataitem that is input/output to a module execution. This could be a local file, a file on the internet with a url, or some internal representation of the file in the workflow system.
module	the module/service that is to be executed. This could be a local program, a web service, a sub-workflow or some other kind of processing entity.
moduleInstance	the instance of a module in the workflow. This instance is connected with other instances through module ports.
moduleExecution	The execution of a module as recorded internally by the workflow-system or externally in some other way.
workflow	a description of the process containing the module instances and connections
workflowExecution	Executions are grouped into a workflowExecution that is associated with a workflow.
inputPort	represents an input/parameter of a module
outputPort	represents an output/result of a module
connection	represents a connection between module Instances on specific ports

API Functions

The relations among the model entities are shown in the diagram above. Note that few of the current provenance systems capture all of this information. For example, some lack information about data products, and some do not explicitly store the workflow definition. Thus, in designing API bindings for the different systems, the goal is to extract (and map) as much information as possible from each source.

The model ER-diagram above suggest the following API functions.

Execution:

• getDataFromOutPort
• getOutPortFromData
• getDataFromInPort
• getInPortFromData
• getExecutionFromInData
• getInDataFromExecution
• getExecutionFromOutData
• getOutDataFromExecution
• getInstanceFromExecution
• getExecutionFromInstance
• getRunFromExecution
• getExecutionFromRun
• getRunFromWorkflow
• getWorkflowFromRun
• getInstanceFromWorkflow
• getWorkflowFromInstance
• getParentDataItem
• getChildDataItem
• getParentExecution
• getChildExecution

Workflow:

• getModuleFromInstance - Get the motule this is an instance of
• getInstanceFromModule
• getStartConnectionFromInstance
• getEndConnectionFromInstance
• getStartInstanceFromConnection
• getEndInstanceFromConnection
• getConnectionFromWorkflow
• getWorkflowFromConnection
• getParentWorkflow
• getChildWorkflow
• getConnectionFromInPort
• getInPortFromConnection
• getConnectionFromOutPort
• getOutPortFromConnection
Derived:
• getParentInstance
• getChildInstance

Module:

• getOutPortFromModule
• getInPortFromModule
• getModuleFromOutPort
• getModuleFromInPort

Global functions:

• getAll(type)
• getAll(type, annotation restriction)
• getAnnotation

Upstream

The most common use of provenance data will be to perform the transitive closure of some connected executions or data items i.e. to track data dependencies back and forward in time. We call this upstream for tracking back in time and downstream for tracking forward in time.

We have identified 4 primitives to which upstream/downstream tracking is relevant:

primitive	description
dataitem	tracking data dependencies
moduleExecution	tracking execution dependencies
moduleInstances	tracking module dependencies within a workflow
workflow	tracking workflow design history e.g. different workflow versions in the VisTrails action tree

For a general transitive function we propose:

• traverse(start, end, limit, stop)

The definition is: start is the start point and end is the endpoint. Limit is the max number of steps to search where 0 means no limit. Stop is an optional list of nodes which should not be explored further. 'Stop' is needed by some queries in the challenge and also adds to the expressiveness of the queries.

The function shold return all elements between start and end with a maximum length of 'limit' and excluding branches after 'stop'. If start or end is omitted e.g. '*', the function should continue to traverse until no more results are found or limit is reached.

Examples:

• traverse(start, *, 0) (downstream)
• traverse(*, end, 0) (upstream)
• traverse(start, end, 0) (find all elements in between)
• traverse(*, end, 0, softmean) (upstream excluding nodes after softmean)

There should also exist a way of checking if two nodes are related to each other

• related(start,end,limit) (Return true if a path exist between the nodes)

Implementation

The implementation is done in python. Currently the API has been partially implemented for XML using XPath and RDF using SPARQL.

There are currently three ways to implement the transitive closure:

1. Natively in the Query processor (not implemented yet)
2. As an extra graph structure as described below
3. An implementation in python using basic relation queries on the source. (Very slow)

For small data stores any implementation is possible. For large data stores (2) might not be possible. If (1) is not possible in the query engine, your only choice is (3), which might be very slow. An assumption would be that an implementation of a provenance store would probably support (1). Or implement its own version of (2).

For query processors not capable of transitive closure (like the ones above), we have implemented a Graph structure. During initialization it loads the transitive relations in the data store. All upstream/downstram queries will then be directed to that Graph structure for fast computation.

System overview

The structure of the system can be summarized in the figure below.

PQObject represents a node in the provenance data by storing its id and namespace (Its PId). It can call methods in PQueryFactory to traverse the data as a graph. PQueryFactory contains the sources and forwards queries to the correct source by comparing namespaces.

All data source inherits from PStore. It contains functions implementing data aliases, execution dependencies in other sources and sending queries to the right functions. It also provides access to PGraph that implements a structure for storing and querying transitive relations. This structure can be used if the query engine does not support efficient querying of transitive closure. It works by loading the transitive data during initialization and then direct all transitive queries to it. It is thus not suited for very large data.

There are currently 2 classes implementing specific data type access: XMLStore implements loading of an XML data file and provides access through XPath. RDFStore implements access to an RDF server using SPARQL. Other data types i.e. relational DB can be implemented in a similar way.

The figure shows TavernaStore and TavernaRDFStore. They are both implementing the API for the MyGrid team data files. The MyGrid Taverna data is in XML/RDF which makes it possible to process it using both XPath and SPARQL. Having two versions makes comparison between implementations easy without having to worry about different data formats.

Another partially implemented XML source is the Southampton team.

--Tommy 03:40, 13 April 2007 (MDT)--