On Tue, Jan 18, 2011 at 10:11, Stian Soiland-Reyes <[email protected]> wrote: > 2011/1/17 Mikołaj Rybiński <[email protected]>: >> can I have in Taverna 2 workflow format a referenced nested workflow >> (i.e. not implicitly included in the workflow file) like >> 'xscufllocation' tag in SCUFL? If yes, how can I do that? > > I'm afraid the answer is no.
Ok, thanks. > > We did not include support for this as we found it generally caused > problems when distributing workflows, with references like > file:///F:/My USB stick/ not working very well across machines. I guess that's just poor workflow build, not the feature defect. > > > If you want to do this for the purpose of using the 'latest' nested > workflow, you can in Taverna 2.2 right click on a nested workflow and > say "Replace with.." and select a nested workflow from file. However, > the filename itself is not kept, so you would have to repeat this > procedure every time the nested workflow file changed. > I simply don't want to multiply entities (workflows), especially when they're currently subjects to some minor changes. I guess I'll stick to SCUFL for now. > > > We're in the process of working out the details of the replacement > workflow format for Taverna 2 called SCUFL2. If you would like to > place 'workflow import' as a requirement for that, please let us know > - in particular a use-case of when it would be useful to you would be > helpful. Yes, I would like to see 'xscufllocation' feature in SCUFL2. The use-case is in principle as stated above. For example, I have a small workflow which converts XML results lists to plot data series XML, based on the results list XML itself and some filtering parameters for the plot (plotted args and values). I use it in two other workflows and it would desired not to manually update-them when I do some backward compatible changes to the XML-converting workflow, e.g. changes that do not alter interface (input and output ports). Other use case are workflows which wrap Web services, so that constructing some of the input parameters is more convenient for the user. I guess, workflows aren't much different from processor and could be treated as so, especially that there is myExperiment infrastructure which, among many other things, exposes submitted workflow file under public URL. Any idea regarding version of Taverna in which SCUFL2 will be available? Greetz, Mikołaj > > > -- > Stian Soiland-Reyes, myGrid team > School of Computer Science > The University of Manchester > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > taverna-users mailing list > [email protected] > [email protected] > Web site: http://www.taverna.org.uk > Mailing lists: http://www.taverna.org.uk/about/contact-us/ > ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
