Right - many, many levels of provenance... provenance of source code is not very much different from provenance of workflow definitions. We already did quite a bit of work with that on a social level with our generic workflow sharing platform myExperiment - http://www.myexperiment.org/home -- e.g. "Version 4 of this workflow - attributed to this other workflow by someone else". This might be of interest to other "Workflow-like" projects within Apache - as myExperiment can deal with any workflow type.
For instance, my workflow at http://www.myexperiment.org/workflows/3860 attributes http://www.myexperiment.org/workflows/3369 because I have embedded it as a nested workflow. I have therefore also given the original authors credit on my workflow. Lots of this information can be deduced by inspecting the definitions, looking at hashes and identifiers, etc. (Taverna workflow definitions includes a chain of identifiers throughout its evolution - so you can even tell if an earlier, unpublished version of a workflow has been reused). Provenance of a workflow *execution* is also quite related to, but still quite distinct from, the higher level provenance of research data and of the scientific analysis it has been going through. Similarly the provenance of a command line tool can be on system-level "Ran for 14 seconds on a Linux host asdkjasd using 1127 MB of memory and these shared libraries" - or on a semantic level like "Aligned these two biological sequences from mouse and rat". The big challenge is trying to bind these kinds of provenance together, and to infer one level of provenance from another. But I am digressing! My apologies to the rest of the list.. but do let me know if you are interested in workflows, provenance, versioning and semantics, and we can put together some kind of interest group. On 23 October 2014 07:41, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > Hi, > > Thanks for the clarifications. > > On Thu, Oct 23, 2014 at 4:43 AM, Stian Soiland-Reyes > <soiland-re...@cs.manchester.ac.uk> wrote: > > ...Provenance exchange - I am thinking in particular if it would be > > possible to combine our W3C PROV-O provenance support - > > https://github.com/taverna/taverna-prov (which describes a workflow > > run) - with exposing service-level provenance... > > Ok got it now. We sometimes talk about the provenance of our code, > which must be traceable etc. so I was confused why you'd exchange > provenance with other projects ;-) > > All clear now. > -Bertrand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester http://soiland-reyes.com/stian/work/ http://orcid.org/0000-0001-9842-9718
