W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > July 2006

OpenWFE - other workflow formalisms and engines

From: William Bug <William.Bug@DrexelMed.edu>
Date: Tue, 18 Jul 2006 14:54:04 -0400
Message-Id: <18E1E7ED-E5DF-406B-AC0D-202F5D35E138@DrexelMed.edu>
Cc: Chimezie Ogbuji <ogbujic@bio.ri.ccf.org>, Joanne Luciano <jluciano@predmed.com>
To: w3c semweb hcls <public-semweb-lifesci@w3.org>
Hi All,

I must say, I really like the looks of OpenWFE.  It certainly is a  
worthy alternative to Taverna and Kepler - though each provide  
specific advantages and disadvantages.  I endorse Joanne's request  
for some guidance on what the pros & cons are here.

One question worth asking in this context is which best supports the  
use of semantic web tech as a means of using formal semantic  
knowledge to navigate decision trees and modify run-time algorithmic  
parameters in the workflow?

I really have no idea myself, but I'd expect there are others on this  
list who could answer that question in some detail.

There are a few other workflow formalisms in use in the world beyond  
life sciences that can be useful to be aware of.

Some of these may in fact underlie OpenWFE and Taverna.  I've not had  
the chance to dig into this yet, either, but I'm certain there are  
others on this list who can tell us.

Some may also not have survived the e-business process debates of  
several years back - or the more recent re-orientation toward SOA,  
though I do believe most of these are in use in fairly large  
application spaces.

Web Services Flow Language (WSFL)

Business Process Execution Language for Web Services (BPEL4WS)

or it's more recent SOA-informed decendent - WS-BPEL 2.0

GRID Services Flow Language (GSFL) - built on OGSA and, therefore,  
quite compatible with the Globus libraries

e-Business Process ML (ebPML)

On the BIRN project, we've been using workflow engines to help  
leverage GRID resources for high-throughput, large-scale brain image  
data processing tasks - e.g.,:



(see also Kepler's parent project - Ptolemy)

There are also the two following community sites worth checking out,  
though they have a distinct bent toward the commercial sector:

The Workflow Management Coalition (WfMC)

Workflow Management Systems yellow pages


On Jul 18, 2006, at 1:39 PM, jluciano@predmed.com wrote:

> Hi Chimezie,
> Thanks for sending the information about OpenWFE.  Do you know how  
> OpenWFE compares to Taverna?  I've been using Taverna (just a  
> little) so far for some exploratory work in Diabetes.
> Joanne
>> -----Original Message-----
>> From: Chimezie Ogbuji [mailto:ogbujic@bio.ri.ccf.org]
>> Sent: Tuesday, July 18, 2006 12:04 PM
>> To: 'w3c semweb hcls'
>> Subject: Re: HCLS-ACPP Tcon today
>> I've added links for OpenWFE's Workflow Patterns (as well as
>> the XML schema it uses to represent workflow patterns) to the
>> ACPPTaskForce Wiki. Part of the task objectives on the ACPP wiki  
>> includes
>> collecting core vocabularies for expressing workflow modeling
>> constructs. There are many well established patterns in this field  
>> that
>> could be captured in an RDF/OWL vocabulary for use with pathway and
>> protocol decision making.
>> One of the immediate advantages (in this case)
>> of using a XML dialect (that could be mapped to such a
>> vocabulary directly), is in using pre-existing workflow management  
>> tools (such
>> as OpenWFE's web-based editor) to construct a workflow document. The
>> existing ER Stroke Management usecase could be modelled this way.
>> OpenWFE is an open source workflow engine.
>> * http://demo.openwfe.org/droflo/ [Droflo Demo]
>> Chimezie Ogbuji
>> Lead Systems Analyst
>> Thoracic and Cardiovascular Surgery
>> Cleveland Clinic Foundation
>> 9500 Euclid Avenue/ W26
>> Cleveland, Ohio 44195
>> Office: (216)444-8593
>> ogbujic@ccf.org

Bill Bug
Senior Analyst/Ontological Engineer

Laboratory for Bioimaging  & Anatomical Informatics
Department of Neurobiology & Anatomy
Drexel University College of Medicine
2900 Queen Lane
Philadelphia, PA    19129
215 991 8430 (ph)
610 457 0443 (mobile)
215 843 9367 (fax)

Please Note: I now have a new email - William.Bug@DrexelMed.edu

This email and any accompanying attachments are confidential. 
This information is intended solely for the use of the individual 
to whom it is addressed. Any review, disclosure, copying, 
distribution, or use of this email communication by others is strictly 
prohibited. If you are not the intended recipient please notify us 
immediately by returning this message to the sender and delete 
all copies. Thank you for your cooperation.
Received on Tuesday, 18 July 2006 18:54:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:20:17 UTC