There's been a discussion for the Next Gen Taverna Workbench regarding components - and if they should be implemented as nested workflows or simply merged into a flat workflow.
As a quick intro - think of a component as a T2 service with additional input and output helpers/shims - allowing it to easily connect to other components. Components will be discovered from component registries - and ideally components in the same "component family" will form 'lego bricks' which easily fits together to build a workflow within a particular field. The considerations below highlight advantages and disadvantages of using nested workflows. This might be a bit technical - but could also be relevant for Taverna 2 workflow designers on wether to use a nested workflow or not. http://www.mygrid.org.uk/dev/wiki/display/TNG/Nested+workflow+consideration Feel free to comment - we've not yet decided on which one to go for! -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/ Developers Guide: http://www.taverna.org.uk/developers/
