Author: gnaylor
Date: Wed Jul 13 21:40:50 2016
New Revision: 1752544

URL: http://svn.apache.org/viewvc?rev=1752544&view=rev
Log:
Make minor edits

Modified:
    incubator/taverna/site/trunk/content/documentation/interaction/index.md

Modified: 
incubator/taverna/site/trunk/content/documentation/interaction/index.md
URL: 
http://svn.apache.org/viewvc/incubator/taverna/site/trunk/content/documentation/interaction/index.md?rev=1752544&r1=1752543&r2=1752544&view=diff
==============================================================================
--- incubator/taverna/site/trunk/content/documentation/interaction/index.md 
(original)
+++ incubator/taverna/site/trunk/content/documentation/interaction/index.md Wed 
Jul 13 21:40:50 2016
@@ -18,79 +18,79 @@ Notice:    Licensed to the Apache Softwa
 
 ##Interacting with a workflow in your browser
 
-Many workflows, when run, require interaction with a user. 
-This can be to enter data values, confirm that intermediate results are OK to 
proceed with the 
-   run, or to control the functionality of a service. 
+Many workflows, when run, require interaction with a user.
+This can be to enter data values, confirm that intermediate results are OK to 
proceed with the
+   run, or to control the functionality of a service.
 
 ### Beanshells
-When running a workflow in [Taverna Workbench](/download/workbench) you can 
use beanshells 
+When running a workflow in [Taverna Workbench](/download/workbench) you can 
use beanshells
    to show Java swing components. Taverna Workbench includes a set of 
pre-defined beanshells to,
    for example, [Ask](http://dev.mygrid.org.uk/wiki/display/taverna/Ask) the 
user for data.
 
 
 ### BioVeL interaction service
-If you run your workflow in a portal or on a [server](/download/server), then 
using beanshells 
-   for interaction will not work. Attempts to use Swing will either fail or, 
worse, 
+If you run your workflow in a portal or on a [server](/download/server), then 
using beanshells
+   for interaction will not work. Attempts to use Swing will either fail or, 
worse,
    open dialogs on the machine where the workflow is running.
 
 To support interaction with workflows running on a server, the 
[BioVeL](http://www.biovel.eu)
-   project developed a new 
-   [interaction 
service](http://dev.mygrid.org.uk/wiki/display/taverna/Interaction+service). 
-This interaction service allows users to interact with a running workflow 
within a standard web 
-   browser. 
-The interaction can be as simple as acknowledging a message, 
-   or as complex as controlling a tool running on a remote machine. 
-The interaction can be parameterized by data from the workflow and can return 
data from the 
+   project developed a new
+   [interaction 
service](http://dev.mygrid.org.uk/wiki/display/taverna/Interaction+service).
+This interaction service allows users to interact with a running workflow 
within a standard web
+   browser.
+The interaction can be as simple as acknowledging a message,
+   or as complex as controlling a tool running on a remote machine.
+The interaction can be parameterized by data from the workflow and can return 
data from the
    browser to the workflow.
 
-<iframe src="http://www.youtube.com/embed/S9X6E4PdFcM?start=60"; 
frameborder="0" 
+<iframe src="http://www.youtube.com/embed/S9X6E4PdFcM?start=60"; frame 
border="0"
         width="420" height="315"></iframe>
 
 Interactions have already been used for many purposes. These include:
 
- - to manipulate data inside [Open Refine](http://openrefine.org/) (previously 
Google Refine),
- - to show information on maps and
- - to show the results of species population modelling
-
-##Notification of interaction requests
-
-One of the advantages of running workflows on a server is that you do not need 
to monitor them 
-   constantly. 
-However, you then need a way to be alerted that a workflow requires an 
interaction. 
-The interaction service uses 
[ATOM](http://en.wikipedia.org/wiki/Atom_(standard)) feeds to send 
-   out notifications. 
-ATOM feeds can be read by many different clients, including mobile phone Apps 
and mail readers. 
+ - manipulating data inside [Open Refine](http://openrefine.org/) (previously 
Google Refine),
+ - showing information on maps, and
+ - showing the results of species population modelling.
+
+## Notification of interaction requests
+
+One of the advantages of running workflows on a server is that you do not need 
to monitor them
+   constantly.
+However, you then need a way to be alerted that a workflow requires an 
interaction.
+The interaction service uses 
[ATOM](http://en.wikipedia.org/wiki/Atom_(standard) feeds to send
+   out notifications.
+ATOM feeds can be read by many different clients, including mobile phone Apps 
and mail readers.
 The ATOM message will include a link to the HTML page for the interaction 
required.
 
-##Usage scenarios
+## Usage scenarios
 
-The interaction service combines standard protocols such as ATOM and HTML. 
+The interaction service combines standard protocols such as ATOM and HTML.
 As a result there are many ways in which users can interact with their 
workflow run.
 
-###On your phone
+### On your phone
 
-Most modern mobile/cell phones support web browsers and also ATOM feed Apps. 
-If you subscribe to the ATOM feed for a workflow run, 
-   then you can open the HTML page in the phone's browser, interact with the 
workflow run, 
+Most modern mobile/cell phones support web browsers and also ATOM feed Apps.
+If you subscribe to the ATOM feed for a workflow run,
+   you can open the HTML page in the phone's browser, interact with the 
workflow run,
    and then go back to whatever you were doing.
 
-This has been demonstrated for simple interactions; complex interactions can 
be limited a 
+This has been demonstrated for simple interactions. Complex interactions can 
be limited by a
   phone's screen resolution.</p>
 
-###Inside another web page
+### Inside another web page
 
-It is common to use a web page to run workflows on a server. 
-This could be, for example, within a 
-   [Taverna Player](/documentation/taverna-player), 
-   or a more complex portal such as the Taverna 2.4 Server Demonstrator. 
-When a workflow is run, the page creates a subscription to the run&'s ATOM 
feed. 
-When a notification is sent on the feed, the page can then show the 
interaction. 
-An example of this is demonstrated in this video.
+It is common to use a web page to run workflows on a server.
+This could be, for example, within a
+   [Taverna Player](/documentation/taverna-player),
+   or a more complex portal such as the Taverna 2.4 Server Demonstrator.
+When a workflow is run, the page creates a subscription to the run's ATOM feed.
+When a notification is sent on the feed, the page can then show the 
interaction.
+An example of this is demonstrated in the video.
 
-###In the workbench
+### In the workbench
 
-The Taverna Workbench is also able to run interaction services. 
-When a notification is sent, it opens up the HTML page in your preferred 
browser. 
+The Taverna Workbench is also able to run interaction services.
+When a notification is sent, it opens up the HTML page in your preferred 
browser.
 You can choose to use <a title="Jetty" 
href="http://www.eclipse.org/jetty/";>Jetty</a> to handle the feed and hosting 
of pages, or an external site.</p>
 
 <h2>Installing the interaction service</h2>


Reply via email to