You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@taverna.apache.org by bu...@apache.org on 2015/01/29 16:02:16 UTC
svn commit: r938222 - in /websites/staging/taverna/trunk: cgi-bin/ content/
content/introduction/why-use-workflows.html
Author: buildbot
Date: Thu Jan 29 15:02:15 2015
New Revision: 938222
Log:
Staging update by buildbot for taverna
Added:
websites/staging/taverna/trunk/content/introduction/why-use-workflows.html
Modified:
websites/staging/taverna/trunk/cgi-bin/ (props changed)
websites/staging/taverna/trunk/content/ (props changed)
Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jan 29 15:02:15 2015
@@ -1 +1 @@
-1655685
+1655695
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jan 29 15:02:15 2015
@@ -1 +1 @@
-1655685
+1655695
Added: websites/staging/taverna/trunk/content/introduction/why-use-workflows.html
==============================================================================
--- websites/staging/taverna/trunk/content/introduction/why-use-workflows.html (added)
+++ websites/staging/taverna/trunk/content/introduction/why-use-workflows.html Thu Jan 29 15:02:15 2015
@@ -0,0 +1,198 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <title>Apache Taverna - Why use workflows?</title>
+
+ <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ <meta property="og:image" content="/img/taverna-logo-145x134.png" />
+
+ <link rel="shortcut icon" href="/favicon.ico">
+ <link rel="icon" type="image/png" sizes="145x134" href="/img/taverna-logo-145x134.png">
+ <link rel="apple-touch-icon" sizes="145x134" href="/img/taverna-logo-145x134.png">
+
+ <link rel="stylesheet" href="/lib/bootstrap/css/bootstrap.min.css">
+ <link rel="stylesheet" href="/lib/bootstrap/css/bootstrap-theme.min.css">
+ <link rel="stylesheet" href="/css/sticky-footer-navbar.css">
+ <link rel="stylesheet" href="/css/taverna.css">
+
+
+
+
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
+
+ <!-- JSON-LD markup for Google Structured Data -->
+
+ <!-- generic JSON-LD for this page -->
+ <script type="application/ld+json">
+ {
+ "@context" : "http://schema.org",
+ "@type" : ["CreativeWork"],
+ "@id": "",
+ "name" : "Why use workflows?",
+ "publisher" : {
+ "@type" : "Organization",
+ "url" : "http://www.apache.org/",
+ "name" : "The Apache Software Foundation (ASF)"
+ },
+ "license": {
+ "@type": "CreativeWork",
+ "@id": "http://www.apache.org/licenses/LICENSE-2.0",
+ "url": "http://www.apache.org/licenses/LICENSE-2.0",
+ "name": "Apache License, Version 2.0"
+ }
+ }
+</script>
+
+ </head>
+
+ <body>
+
+ <!-- Static navbar -->
+ <nav class="navbar navbar-default" role="navigation">
+ <div class="container">
+ <div class="navbar-header">
+ <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <a class="navbar-brand" href="/"><img src="/img/taverna-logo-145x134.png" alt="">Apache Taverna</a>
+
+ </div>
+ <div id="navbar" class="navbar-collapse collapse">
+ <ul class="nav navbar-nav">
+ <li><a href="/about/">About</a></li>
+ <li class="dropdown">
+ <a href="/download/" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Download<span class="caret"></span></a>
+ <ul class="dropdown-menu" role="menu">
+ <li><a href="/download/">Apache Taverna 3.x</a></li>
+ <li><a href="/download/pre-apache.html">Taverna 2.x (Pre-Apache)</a></li>
+ </ul>
+ </li>
+ <li><a href="/doc/">Documentation</a></li>
+ <li><a href="/code/">Code</a></li>
+ <li><a href="/contact/">Contact</a></li>
+ </ul>
+
+ <form >
+
+
+ <!--<input type="submit" id="submit" value="Search">-->
+ </form>
+
+ <form class="navbar-form navbar-right" role="search"
+ name="search" id="search" action="http://www.google.com/search" method="get">
+ <input value="taverna.incubator.apache.org" name="sitesearch" type="hidden"/>
+ <div class="form-group input-group">
+ <input type="text" name="q" id="query" placeholder="Search" class="form-control">
+ <span class="input-group-btn">
+ <button type="submit" class="btn btn-default">Search</button>
+ </span>
+ </div>
+ </form>
+
+ <ul class="nav navbar-nav navbar-right">
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">ASF<span class="caret"></span></a>
+ <ul class="dropdown-menu" role="menu">
+ <li><a href="http://www.apache.org/">Apache Software Foundation</a></li>
+ <li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+ <li><a href="http://incubator.apache.org/projects/taverna.html">Taverna Incubation Status</a></li>
+ </ul>
+ </li>
+ </ul>
+ </div><!--/.nav-collapse -->
+ </div><!--/.container-fluid -->
+ </nav>
+
+
+ <div id="page" class="container">
+ <h1>Why use workflows?</h1>
+ <div class="alert alert-info" role="alert"><p><span class="glyphicon glyphicon-info-sign" aria-hidden="true"></span>
+
+Taverna is transitioning to the Apache Incubator.
+This webpage reflects material not yet released under Apache Incubator.
+Instead it shows <a class="alert-link" href="http://www.taverna.org.uk/">taverna2</a> material that is expected to become part of the Apache Incubator project in the future.
+</div>
+
+
+ <div id="content"><h2 id="history">History</h2>
+<p>Workflow, as a concept, was defined in the business domain in 1996 by the Workflow Management Coalition as:</p>
+<blockquote>
+<p>âThe automation of a business process, in whole or part, during which documents,
+ information or tasks are passed from one participant to another for action,
+ according to a set of procedural rules.â</p>
+</blockquote>
+<h2 id="scientific-workflows">Scientific workflows</h2>
+<p>Scientific workflows are widely recognised as a âuseful paradigm to describe, manage,
+ and share complex scientific analysesâ. They are the method often used by the <a href="/introduction/what-is-in-silico-experimentation.html">in silico experimentation</a>.</p>
+<p>Scientific workflows have emerged to tackle the problem of excessive complexity in scientific experiments and
+ applications.
+They provide a high-level declarative way of specifying what a particular in silico experiment modelled
+by a workflow is set to achieve, not how it will be executed.</p>
+<p>Various types of tasks that can be performed within a workflow can be implemented by local services,
+ remote Web services, scripts, and sub-workflows (complete workflows used as subroutines in larger ones).
+Each component is only responsible for a small fragment of functionality,
+ therefore many components need to be chained in a pipeline in order to obtain a workflow that can perform
+ a useful task.</p>
+<p>The process of linking components is known as workflow composition,
+ a result of which a conceptual model of the described scientific analysis is produced.
+This model is often represented as a graph-like structure (example can be seen in Figure 1 below)
+ that defines the flow of data within the workflow â and thus its semantic meaning.
+Representations of all required heterogeneous resources are integrated into this single workflow,
+ thus abstracting superfluous detail and concentrating on the real goal of the experiment.</p>
+<p>An example of simple workflow that retrieves a weather forecast for the specified city</p>
+<p><img class="img-center" title="Get weather forecast for a city workflow" src="/img/get_weather_workflow.png"
+ alt="An example of simple workflow that retrieves a weather forecast for the specified city"
+ width="195" height="269" /></p>
+<p class="text-center">
+Figure 1. An example of a simple workflow that retrieves a weather forecast for the specified city
+</p>
+
+<p>The use of workflows allows offloading much of the data processing to remote components and
+ makes it feasible to execute even larger and more complex workflows on regular personal computers.
+This is the reason why Web services are normally chosen to perform most of the core computation in workflows,
+ whereas local services and scripts are used to perform data format conversion procedures and
+ other auxiliary tasks.</p>
+<p>A further advantage of using workflows is the potential to automate highly repetitive processing stages that
+ research work is known to involve. This, in turn, can stimulate the pace of research and
+ the overall productivity of experimentation through evident savings in time and effort.</p>
+<p>To learn more about scientific workflows and their role in data-intensive experiments, have a look at:</p>
+<ul>
+<li><a href="http://research.microsoft.com/en-us/collaboration/fourthparadigm/4th_paradigm_book_part3_goble_deroure.pdf">âThe impact of workflow tools on data-centric researchâ</a> chapter
+ by Carole Goble and David De Roure of the <a href="http://research.microsoft.com/en-us/collaboration/fourthparadigm/">âThe Fourth Paradigm: Data-Intensive Scientific Discoveryâ</a> book.</li>
+<li><a href="http://cnx.org/content/m32861/latest/content_info">âScientific workflowsâ</a> paper by Katy Wolstencroft, Paul Fisher, David De Roure and Carole Goble.</li>
+</ul>
+<p>Massive power, minimal complexity</p>
+<p>Because services within a workflow do not normally reside on the machine you use to create and run the workflow,
+ your local machine does not have to be a supercomputer.
+By installing and using the Taverna [Workflow Management System[5] you can tap into the resources of
+ a number of institutes, hundreds of analysis applications and literally thousands of CPUs worth of
+ computational power entirely for free, with no installation or support hassle for you.</p>
+<p>Of course, if you already have significant resource in house it is a relatively simple matter to
+ integrate these resources in Taverna with those available from other sites.</p></div>
+
+ </div>
+
+ <footer class="footer">
+ <div class="container">
+ <p id="copyright" class="text-muted">
+ Copyright © 2014 The Apache Software Foundation, Licensed under the
+ <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </footer>
+
+ <script src="/lib/jquery/jquery-1.11.1.min.js"></script>
+ <script src="/lib/bootstrap/js/bootstrap.min.js"></script>
+
+
+ </body>
+</html>
\ No newline at end of file