On Wed, May 20, 2009 at 11:01, Alan Williams <[email protected]> wrote: > Stian Soiland-Reyes wrote: > [snip] >> So I agree that we can skip the 'deeper' provenance for now - for most >> users they would care more about where their actual results came from >> - but for 'correct' provenance we would really need to store the >> result of *all* the layers - as in a way each layer makes a decision. >> (The "control" part of the workflow). > > Doesn't that imply that rather than provenance being seen as its own > specific layer, or two layers, it is something that always goes between > layers (and on the outside of the stack)? i.e. it should not be done as > a layer.
Yes - in a way it should go between each layer so it can trace what happened inside the layer. This would however mean lots of semi-redundant provenance for most of the cases where there's no retry, etc. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ taverna-hackers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/taverna-hackers Developers Guide: http://www.mygrid.org.uk/usermanual1.7/dev_guide.html FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq
