The OPMW Ontology

Release 1 August 2012

This version:
http://www.opmw.org/model/OPMW_20123107
Latest version:
http://www.opmw.org/model/OPMW
Previous version
http://www.opmw.org/model/OPMW_20123003
Revision
Revision 3
Authors:
Daniel Garijo, Universidad Politécnica de Madrid
Yolanda Gil, Information Sciences Institute, University of Southern California, US
Imported Ontologies:
The Open Provenance Model Ontology (OPMO)
The Open Provenance Model Vocabulary (OPMV)
Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.0 Generic License.

Abstract

The Open Provenance Model for Workflows (OPMW) is an ontology for describing workflow traces and their templates based on the Open Provenance Model. It has been designed as a profile for OPM, extending and reusing OPM's core ontologies OPMV (OPM-Vocabulary) and OPMO (OPM-Ontology).

This document specifies the classes, properties and dataproperties of OPMW.

The OWL encoding of the OPMW Ontology can be found here

Table of Contents

1. Introduction back to ToC

OPMW is an OWL-DL ontology developed to represent abstract workflows in addition to workflow execution traces. This requirement was motivated by the goal of publishing workflows of scientific articles and their results.

OPMW is based on the Open Provenance Model [Moreau el al 11], a widely-used domain-independent provenance model result of the Provenance Challenge Series and years of workflow provenance standardization and exchange in the scientific workflow community.

There are several reasons to use OPM: OPM has been already used successfully in many scientific workflow systems, its core definitions are domain independent and extensible to accommodate other purposes and OPM can be considered the basis of the emerging W3C Provenance Interchange Language (PROV), which is currently being developed by the W3C Provenance Working Group as a standard for representing and publishing provenance on the Web.

The OPMW profile aims to be simple and easy to use, following OPMV's style.

2. OPMW Overview back to ToC

OPMW extends OPM to fit in the scientific workflow domain. The next tables summarize the classes, properties and data properties that have been used to extend or complement the OPM core to our domain:

Classes

Object properties

Datatype properties

3. OPMW Description back to ToC

The Open Provenance model offers several core concepts and relationships to represent provenance. It models the resources (datasets) as artifacts (immutable pieces of state), processes (action or series of actions performed on artifacts), and agents (controllers of processes). Their relationships are modeled in a provenance graph with five causal edges: used (a process used some artifact), wasControlledBy (an agent controlled some process), wasGeneratedBy (a process generated an artifact), wasDerivedFrom (an artifact was derived from another artifact) and wasTriggeredBy (a process was triggered by another process). It also introduces the concept of roles to assign the type of activity that artifacts, processes or agents played when interacting with each other, and the notion of accounts and provenance graphs to group sets of OPM assertions into different subgraphs. An account represents a particular view on the provenance of an artifact based on what was executed.

OPMW extends the previous relationships in order to capture the execution traces of a workflow template (process view provenance), plus the metadata of the template and execution itself (attribution provenance).

3.1 Process view provenance back to ToC

OPMW describes the traces of the execution of a workflow along with the abstract workflow (template) used for its design. The trace is described by extending opmv:Artifact with opmw:WorkflowExecutionArtifact; opmv:Process with WorkflowExecutionProcess; and reusing OPM relationships to link them(opmv:used, opmv:wasControlledBy and opmv:wasGeneratedBy). All the assertions from an execution are grouped in a opmw:WorkflowExecutionAccount, a subclass of opmo:Accoount that represents the view of the system on the execution.

Templates are defined with new terms in OPMW, in a similar way to the traces. In this case, the reuse of OPM is not appropriate since we are describing the plan of the workflow(which may be executed in the future or not), not the execution. Templates have opmw:WorkflowTemplateArtifacts (which can be either opmw:DataVariables or opmw:ParameterVariables) and opmw:WorkflowTemplateProcesses, which represent an abstraction of the method that is being executed.

The opmw:WorkflowTemplateArtifacts are connected to opmw:WorkflowTemplateProcesses by opmw:uses and opmw:isGeneratedBy properties. These properties define which type of opmw:WorkflowTemplateArtifact is used by each opmw:WorkflowTemplateProcess and the type of the expected result. The next figure shows a brief example.

Figure 1: An example of process view workflow provenance.

Figure 1 shows a process view high level diagram of the OPM and OPMW representation of an abstract workflow on the left and a workflow execution on the right. The example workflow shown here has one step (executionNode1), which runs the workflow component (specComp1) that has one input (execInput1) and one output (executionOutput1).

3.2 Attribution provenance back to ToC

Attribution is key for scientists who publish the workflow. Thus, OPMW was designed to include metadata from the specification as well as from the execution itself. Figure 2 shows an attribution view on the provenance of the same workflow of Figure 1.

Figure 2: An example of attribution provenance

The abstract workflow contains information of the authors of the original article, the contributors of the workflow, the version, the date of creation and documentation of the abstract workflow (that may include a pointer to the publication). OPMW reuses terms from the Dublin Core (DC) Metadata Terms Vocabulary . The executed workflow links to the workflow systems used to create and execute it, the license, date of start and end of the run and the final status (succeeded or failed execution).

4. Cross reference for OPMW classes, properties and dataproperties

This section provides details for each class, property and dataproperty defined by the OPMW Ontology.

4.1 Classes

Data Variablec back to ToC or Class ToC

IRI: http://www.opmw.org/ontology/DataVariable

A Data variable is a workflow template artifact that represents a variable in the workflow specification.

Example: 

	@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
	@prefix opmw: <http://www.opmw.org/ontology/> .

	<http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_NTM_SUM_CORRDO>
			a opmw:WorkflowTemplateArtifact , opmw:DataVariable ;
			rdfs:label "Data variable Sum_CorrDO" ;
			opmw:hasDimensionality "0"^^xsd:int ;
			opmw:isGeneratedBy <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_NTM_CREATEPLOTS> ;
			opmw:template              <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> .

has super-classes

Parameter Variablec back to ToC or Class ToC

IRI: http://www.opmw.org/ontology/ParameterVariable

An parameter variable represents a description of an input parameter of a process. Parameter variables can only be used by process.

Example: 

	@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
	@prefix opmw: <http://www.opmw.org/ontology/> .
	<http://www.opmw.org/export/resource/ParameterVariable/AQUAFLOW_NTM_LATITUDE>
			a opmw:/WorkflowTemplateArtifact , opmw:ParameterVariable ;
			rdfs:label "Parameter variable Latitude" ;
			opmw:template <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> .

has super-classes

Workflow Execution Accountc back to ToC or Class ToC

IRI: http://www.opmw.org/ontology/WorkflowExecutionAccount

A workflow execution account represents the execution view from the perspective of the system.

Example: 

	@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335533097598>
			a       opmo:Account , opmw:WorkflowExecutionAccount> ;
			rdfs:label "Execution account created on 1335533097598" ;
			opmw:executedInWorkflowSystem
			
	<http://www.opmw.org/export/resource/Agent/SHELL> ;
			opmw:hasEndTime "2012-04-25T07:17:48-07:00"^^xsd:dateTime ;
			opmw:hasExecutionDiagram "http://wind.isi.edu/marbles/assets/components/Water/runs/run_144.png"^^xsd:anyURI ;
			opmw:overallStartTime               "2012-04-25T07:17:05-07:00"^^xsd:dateTime ;
			opmw:hasStatus "SUCCESS" ;

has super-classes
  • opmo:Account c
is in domain of
executed in workflow system op, overall End Time dp, has Execution Diagram dp, overall Start Time dp, has Status dp, has Original Log File dp

Workflow Execution Artifactc back to ToC or Class ToC

IRI: http://www.opmw.org/ontology/WorkflowExecutionArtifact

A Workflow Execution Artifact represents a resource used or generated in the execution of a workflow.

Example: 

	@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmv: <http://purl.org/net/opmv/ns#> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .
								
	<http://www.opmw.org/export/resource/WorkflowExecutionArtifact/25F1016C12EBE301EE7AADBC0B085C45>
			a       opmw:WorkflowExecutionArtifact , opmv:Artifact;
			rdfs:label "Execution artifact with id: 25f1016c12ebe301ee7aadbc0b085c45" ;
			opmo:account              <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335533097598> ;
			opmv:wasGeneratedBy     <http://www.opmw.org/export/resource/WorkflowExecutionProcess/p1> ;
			opmw:hasLocation     "http://wings.isi.edu/opmexport/resource/1/144/Formatted_SMN_2010_03_10Z"^^xsd:anyURI ;
			opmw:hasSize "8618"^^xsd:int ;
			opmw:correspondsToTemplateArtifact              <http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_EDM_FORMATTEDDATA>.

has super-classes
  • opmv:Artifact c
is in domain of
has Dimensionality dp, has File Name dp, has Location dp, has Size dp, corresponds to Template Artifact op, has value dp

Workflow execution processc back to ToC or Class ToC

IRI: http://www.opmw.org/ontology/WorkflowExecutionProcess

A workflow execution process represents the execution of a step in workflow template. The execution process also describes the specific method used to acomplish the task described in the proces template.

Example: 

	@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmv: <http://purl.org/net/opmv/ns#> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionProcess/CONVERTTOSTANDARDFORMAT133553> 
			a opmw:/WorkflowExecutionProcess , opmv:Process ;
			rdfs:label "Execution process ConvertToStandardFormat" ;
			opmo:account <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335533097598> ;
			opmv:used <http://www.opmw.org/export/resource/WorkflowExecutionArtifact/6C7CF277338D9590EE18534D4D78924F> ;
			opmv:wasControlledBy <http://www.opmw.org/export/resource/Agent/ADMIN> ;
			opmw:correspondsToTemplateProcess <http://www.opmw.org/export/resource/WorkflowTemplateProcess/CONVERTTOSTANDARDFORMAT> .

has super-classes
  • opmv:Process c
is in domain of
has Executable Component op, corresponds to Template Process op

Workflow Templatec back to ToC or Class ToC

IRI: http://www.opmw.org/ontology/WorkflowTemplate

A workflow template represents the design of the workflow. In such design, the different steps and inputs don't have to be bound to a specific tool or dataset. It is a generic view of the workflow, which is instantiated in each execution.

Example: 

	@prefix dc:  <http://purl.org/dc/terms/> .
	@prefix opmw: <http://www.opmw.org/ontology/> .

	<http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> 
			a opmw:WorkflowTemplate;
			rdfs:label "AquaFlow_NTM" ;
			dc:contributor	<http://www.opmw.org/export/resource/Agent/WATER> ;
			dc:modified  "2011-06-08T09:57:12-07:00"^^xsd:dateTime ;
			opmw:hasVersion "2"^^xsd:int .

has super-classes
  • owl:Thing c
is in domain of
created in Workflow System dp, has Documentation dp, has Template Diagram dp, has Native System Template dp
is in range of
corresponds to Template op

Workflow Template Artifactc back to ToC or Class ToC

IRI: http://www.opmw.org/ontology/WorkflowTemplateArtifact

A workflow template artifact is part of a workflow template. It explains what kind of artifact is used or generated by the process template, along with possible restrictions that it may have.

There are two different types of workflow template artifacts: data variables and parameter variables.

has super-classes
  • owl:Thing c
has sub-classes
Data Variable c, Parameter Variable c
is in domain of
is generated by op
is in range of
corresponds to Template Artifact op, uses op

Workflow Template Processc back to ToC or Class ToC

IRI: http://www.opmw.org/ontology/WorkflowTemplateProcess

A workflow process template is an abstraction of the workflow execution process step that aims to describe the method followed by the scientist instead of its specific instantiation.

Example:

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix water: <http://www.isi.edu/ac/Water/library.owl#> .

	<http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_NTM_CALCULATEHOURLYAVERAGES> 
			a opmw:ProcessTemplate, water:CalculateHourlyAverages;
			opmw:template <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> ;
			opmw:uses <http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_NTM_FILTEREDDATA>.

has super-classes
  • owl:Thing c
is in domain of
uses op
is in range of
corresponds to Template Process op, is generated by op

4.2 Object Properties

executed in workflow systemop back to ToC or Object Property ToC

IRI: http://www.opmw.org/ontology/executedInWorkflowSystem

Property to bind an execution account to the system where it was executed (which could be different from the one used for designing its workflow template).

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionAccount/acc1> 
			a opmo:Account, opmw:executionAccount;
			opmw:executedInWorkflowSystem <http://www.opmw.org/export/resource/Agent/SHELL>.

	<http://www.opmw.org/export/resource/Agent/SHELL> 
			a opmw:Agent.

has characteristics: functional

has domain
has range
  • opmv:Agent c

has Executable Componentop back to ToC or Object Property ToC

IRI: http://www.opmw.org/ontology/hasExecutableComponent

Property that binds a workflow execution process to the specific component (code, scripts, etc.) used in the execution.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmv: <http://purl.org/net/opmv/ns#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionProcess/REAERATIONEDM133549210450086>
			a opmv:Process, opmw:WorkflowExecutionProcess;
			opmw:hasExecutableComponent <http://www.opmw.org/export/resource/ReaerationEDM/COMPONENTREAERATIONEDM>.

has characteristics: functional

has super-properties
  • owl:topObjectProperty op
has domain

corresponds to Templateop back to ToC or Object Property ToC

IRI: http://www.opmw.org/ontology/correspondsToTemplate

Property that binds an execution account to the template of the whole workflow. The template contains the plan for the workflow.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionProcess/acc1>
			a opmo:Account, opmw:workflowExecutionAccount;
			opmw:correspondsToTemplate <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_EDM>.

has characteristics: functional

has domain
  • opmo:Account c
has range

corresponds to Template Artifactop back to ToC or Object Property ToC

IRI: http://www.opmw.org/ontology/correspondsToTemplateArtifact

Property that binds a workflow execution artifact to its correspondant workflow template artifact.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmv: <http://purl.org/net/opmv/ns#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DEPTH1.2150836> 
			a opmv:Artifact, opmw:WorkflowExecutionArtifact;
			opmw:correspondsToTemplateArtifact <http://www.opmw.org/export/resource/ParameterVariable/AQUAFLOW_EDM_DEPTH>.

has characteristics: functional

has domain
has range

corresponds to Template Processop back to ToC or Object Property ToC

IRI: http://www.opmw.org/ontology/correspondsToTemplateProcess

Property that binds a workflow execution process to its correspondant process template.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmv: <http://purl.org/net/opmv/ns#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionProcess/REAERATIONEDM133549210450086>
			a opmv:Process, opmw:WorkflowExecutionProcess;
			opmw:correspondsToTemplateProcess <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_REAERATIONEDM>.

has characteristics: functional

has domain
has range

is generated byop back to ToC or Object Property ToC

IRI: http://www.opmw.org/ontology/isGeneratedBy

Property that binds a workflow template artifact to the workflow template process that generates it.

Example: 

							
	@prefix opmw: <http://www.opmw.org/ontology/> .

	<http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_EDM_REAERATIONPARAMS>
			a opmw:DataVariable, opmw:WorkflowTemplateArtifact;
			opmw:isGeneratedBy <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_REAERATIONEDM>.

has domain
has range

belongs to Templateop back to ToC or Object Property ToC

IRI: http://www.opmw.org/ontology/belongsToTemplate

Property used to dessignate which artifactTemplates and processTemplates belong to a workflow template.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
								
	<http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_REAERATIONEDM>
			a opmw:WorkflowTemplateProcess;
			opmw:belongsToTemplate <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_EDM>.

usesop back to ToC or Object Property ToC

IRI: http://www.opmw.org/ontology/uses

Property that binds a workflow template process to the workflow template artifact that generates it.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .

	<http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_REAERATIONEDM>
			a opmw:WorkflowTemplateProcess;
			opmw:uses <http://www.opmw.org/export/resource/DataVariable/PARAMETERSFILE>.

has domain
has range

4.3 Data Properties

created in Workflow Systemdp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/createdInWorkflowSystem

This data property binds a workflow template to the tool used for its design and creation. The tool is represented by its URL.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	<http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_EDM>
				a opmw:WorkflowTemplate;
				opmw:createdInWorkflowSystem "http://wings.isi.edu"^^xsd:anyURI.

has characteristics: functional

has domain
has range
  • xsd:anyURI

has Dimensionalitydp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasDimensionality

Property that represents the dimensionality of the artifact: 0 is a single file, 1 for a collection, etc.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	<http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_NTM_DAILYDATA>
			a opmw:DataVariable, opmw:WorkflowTemplateArtifact;
			opmw:hasDimensionality "1"^^xsd:int.

has characteristics: functional

has domain
has range
  • xsd:int

has Documentationdp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasDocumentation

Property that binds a workflow template to its documentation.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .

	<http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM>
			a opmw:WorkflowTemplate;
			opmw:hasDocumentation "A copy of the documentation related to this template "^^xsd:string.

has domain
has range
  • xsd:string

overall End Timedp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/overallEndTime

Property that indicates that the last of the activities in the account finished finished executing before this time.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .
								
	<http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949>
			a opmw:WorkflowExecutionAccount,opmo:Account;
			opmw:overallEndTime "2012-04-25T10:28:55-07:00"^^xsd:dateTime.

has characteristics: functional

has domain
has range
  • xsd:dateTime

has Execution Diagramdp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasExecutionDiagram

Property that links an execution account to its diagram. The diagram shows how the template has been instantiated with different components.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949>
			a opmw:WorkflowExecutionAccount,opmo:Account;
			opmw:hasExecutionDiagram "http://wind.isi.edu/marbles/assets/components/Water/runs/run_148.png"^^sxd:anyURI.

has characteristics: functional

has domain
has range
  • xsd:anyURI

has File Namedp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasFileName

Property used to link an execution artifact to its file name (independently of its URI).

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmv: <http://purl.org/net/opmv/ns#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DCF49186981194248009E24BAD6A6412>
			a opmv:Artifact, opmw:WorkflowExecutionArtifact.
			opmw:hasFileName "NTMParams_SMN_2010_03_14Z"^^xsd:string.

has characteristics: functional

has domain
has range
  • xsd:string

has Locationdp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasLocation

Property used to link an execution artifact to the physical location of its file in the server.

Example

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmv: <http://purl.org/net/opmv/ns#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DCF49186981194248009E24BAD6A6412>
			a opmv:Artifact, opmw:WorkflowExecutionArtifact.
			opmw:hasLocation "http://www.opmw.org/datasets/resource/1/148/NTMParams_SMN_2010_03_14Z"^^xsd:anyURI.

has domain
has range
  • xsd:anyURI

has Sizedp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasSize

Property used to annotate a workflow execution artifact with the size in bytes of its file.

Example 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmv: <http://purl.org/net/opmv/ns#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DCF49186981194248009E24BAD6A6412>
			a opmv:Artifact, opmw:WorkflowExecutionArtifact.
			opmw:hasLocation "68"^^xsd:int.

has characteristics: functional

has domain
has range
  • xsd:int

overall Start Timedp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/overallStartTime

Property that indicates that none of the processes in the account started executing before this time.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949>
			a opmw:WorkflowExecutionAccount,opmo:Account;
			opmw:overallStartTime "2012-04-25T10:28:07-07:00"^^xsd:dateTime.

has characteristics: functional

has domain
has range
  • xsd:dateTime

has Statusdp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasStatus

Property used to state whether all the processes in an account were successful or not.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949>
			a opmo:Account, opmw:ExecutionAccount;
			opmw:hasStatus "SUCCESS"^^xsd.string.

has characteristics: functional

has domain
has range
  • xsd:string

has Template Diagramdp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasTemplateDiagram

Property used to link a workflow template to its graphical representation.

Example: 

							
	@prefix opmw: <http://www.opmw.org/ontology/> .
	<http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM>
			a opmw:WorkflowTemplate;
			opmw:hasTemplateDiagram "http://wind.isi.edu/marbles/assets/components/workflow_portal/users/1/Water/runs/run_148.png"xsd:anyURI.

has domain
has range
  • xsd:anyURI

has valuedp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasValue

Property used to state the value of the artifact (in case of being a parameter).

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmv: <http://purl.org/net/opmv/ns#> .

	<http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DEPTH0.61959237>
			a opmv:Artifact, opmw:WorkflowExecutionArtifact;
			opmw:hasValue "0.61959237"^^xsd:string.

has characteristics: functional

has domain
has range
  • xsd:string

has Original Log Filedp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasOriginalLogFile

Property used to link an execution account to the log file produced by workflow engine where the original execution was performed.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
	@prefix opmo: <http://openprovenance.org/model/opmo#> .
								
	<http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949>
			 a opmw:WorkflowExecutionAccount,opmo:Account;
			 opmw:hasOriginalLogFile "http://wind.isi.edu/marbles/assets/components/Water/runs/run_148.ttl"^^sxd:anyURI.

has characteristics: functional

has domain
has range
  • xsd:anyURI

has Native System Templatedp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/hasNativeSystemTemplate

Property used to link a workflow template to its original template (encoded in the syntax of the workflow system where it was designed: scufl, owl, etc.).

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .

	<http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM>
		a opmw:WorkflowTemplate;
		opmw:hasNativeSystemTemplate "http://wind.isi.edu/marbles/assets/components/Water/AquaFlow_NTM.owl"xsd:anyURI.

has characteristics: functional

has domain
has range
  • xsd:anyURI

is Concretedp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/isConcrete

Property that specifies whether a component is abstract or not.

has characteristics: functional

has range
  • xsd:boolean

version numberdp back to ToC or Data Property ToC

IRI: http://www.opmw.org/ontology/versionNumber

Property used to annotate a resource with it version number.

Example: 

	@prefix opmw: <http://www.opmw.org/ontology/> .
									
	<http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM>
			 a opmw:WorkflowTemplate;
			 opmw:versionNumber "2"^^xsd:int.

has characteristics: functional

has range
  • xsd:int

5. Namespace Declarations back to ToC

opmv
http://purl.org/net/opmv/ns#
opmo
http://openprovenance.org/model/opmo#
opmw
http://www.opmw.org/ontology/
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#
xsd
http://www.w3.org/2001/XMLSchema#

6. References back to ToC

7. Acknowledgements back to ToC

We would like thank:

8. Change Log back to ToC