On Apr 19, 2012, at 8:55 AM, Ross Gardler wrote:

> Thanks for your reply. At this point I think I need to connect the two
> projects to explore further. You've already expressed a willingness to
> help, so I'll put the ball in their court and encourage them to come
> here. If you want to follow up yourself you can find more about the
> project in question at http://www.wf4ever-project.org/ (let me know if
> you want any introductions). The discussion that led to this was
> actually in another project (called DataFlow), but I'll not confuse
> things  by introducing that project yet (I work on it myself and am
> evaluating opportunities).

Hi Ross,

I will wait for a few days before the folks on the other side get a chance to 
absorb what you already might have sent them. If we don't hear back, I will 
certainly take on your offer and request for introduction. This weekend I want 
to get the release out of the way first.

Thanks for all your time and efforts in syncing projects,
Suresh

> 
> Ross
> 
> On 19 April 2012 13:17, Suresh Marru <[email protected]> wrote:
>> 
>> On Apr 19, 2012, at 7:48 AM, Ross Gardler wrote:
>> 
>>> I've been asked by a representative of another project whether XBaya
>>> has "reasonably competent handling of provenance metadata"
>>> specifically, although not limited to, the work of the W3C provenance
>>> group.
>>> 
>>> What should I tell them?
>> 
>> Hi Ross,
>> 
>> XBaya uses a workflow tracking schema [1] for all metadata exchanges for 
>> workflow monitoring. The scheme is designed right from the onset to meet 
>> both the provenance and workflow orchestration goals. If the question is 
>> does Airavata also bundles provenance tools, then the answer is no. But if 
>> the question is literally 'reasonably competent handling of provenance 
>> metadata' the answer is a clear yes. XBaya is designed right from the onset 
>> with provenance goals. XBaya was part of the Provenance Challenge [2] and 
>> features in first and second challenges [3], but once the group moved to OPM 
>> and later to W3C provenance, the Xbaya code did not retain compatibility. 
>> But Prof. Beth Plale and team at IU lead the Karma provenance efforts which 
>> is available from sourceforge [4].
>> 
>> If the follow on question is what it takes to integrate XBaya with 
>> provenance tools like Karma and make it OPM or W3C Provenance complaint 
>> (which I personally consider is too lean to do any meaningful provenance) is 
>> very minimal, almost at the scale of a GSoC project.  I will be happy to 
>> mentor/guide any such efforts.
>> 
>> Cheers,
>> Suresh
>> 
>> [1] - 
>> https://svn.apache.org/repos/asf/incubator/airavata/trunk/modules/commons/workflow-tracking/
>> [2]  - http://twiki.ipaw.info/bin/view/Challenge/
>> [3] - https://pti.iu.edu/sites/default/files/SimmhanIPAW06.pdf
>> [4] - http://sourceforge.net/projects/karmatool/
>> 
>> 
>>> 
>>> Ross
>>> --
>>> Ross Gardler (@rgardler)
>>> Programme Leader (Open Development)
>>> OpenDirective http://opendirective.com
>> 
> 
> 
> 
> -- 
> Ross Gardler (@rgardler)
> Programme Leader (Open Development)
> OpenDirective http://opendirective.com

Reply via email to