BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20111011T140000Z
DTEND:20111011T150000Z
DTSTAMP:20111011T095018Z
ORGANIZER;[email protected]:mailto:[email protected]
UID:[email protected]
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;[email protected];X-NUM-GUESTS=0:mailto:mygrid@lists
 erv.manchester.ac.uk
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;[email protected];X-NUM-GUESTS=0:mailto:taverna
 [email protected]
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Stian Soiland-Reyes;X-NUM-GUESTS=0:mailto:[email protected]
CREATED:20111011T095017Z
DESCRIPTION:As you might know\, we are developing Scufl2 as the next langua
 ge and\nmodel for specifying Taverna workflow. We have already successfully
 \nused this model in an internal release of an OSGi-based command line\ntoo
 l for executing Taverna workflows\, and for Taverna 3 are working\ntowards 
 using this as the workflow model being edited by the\nworkbench.\n\n\nOne o
 f the motivations for moving from .t2flow to Scufl2 is to allow\nthird-part
 y tools (like myExperiment) easier access to the workflow\nstructure\, for 
 reading\, inspection\, annotation and creation of\nworkflows. Ideally this 
 should also allow the development of\nalternative workflow building environ
 ments independent of the workflow\nengine\, like a simplified web-based edi
 tor.\n\n\nScufl2 as developed so far includes a Workflow Bundle format [1]\
 ,\nusing structured folders (normally archived in a ZIP-file for\ndistribut
 ion purposes) of RDF/XML files - which can also be\ncreated/parsed with an 
 XML Schema if the appropriate xsi:type\nattribute is included. [2]. (Note t
 hat the Scufl2 wiki pages are still\nat a draft stage)\n\n\nAlthough this f
 ormat allows for all the Taverna language features to\nbe specified and use
 d in an extensible manner\, for instance allowing\nbundling of data\, prove
 nance and runtime libraries\, plugins to specify\nwhich options they expect
 \, etc.\, this format is more of an exchange\nand bundling format than a fo
 rmat for manual editing.\n\nThe Scufl2 toolkit [3] allows reading and writi
 ng the common Scufl2\nworkflow model in many different formats\, this is fo
 r instance how it\nreads .t2flow and SCUFL 1 workflows at the moment. There
  is also an\ninternal textual "debug output" format. [4]\n\n\nIt has been r
 aised a requirement to develop a more user-fronted\ntextual format for edit
 ing workflows by hand in an editor. The current\nScufl2 development is very
  much enabled to do so.\n\n\nMy suggestion is to do this as an additional S
 CUFL2 format\, as a\nsimple text file in YAML or JSON\, for writing regular
  straight-forward\nworkflows\, with enough automagic (such as port depths a
 nd iteration\nstrategies) filled in by a combination of SCUFL2 tools and th
 e engine.\n\nFor instance in made-up-JSON using the external tool activity:
 \n\n{\n "workflow" : {\n     "inputs": ("name")\,\n     "outputs": ("greeti
 ng")\,\n     "processors": {\n         "hello": {\n              "type": "t
 ool"\,\n              "command": "echo Hello\, %%name%%"\n         }\n     
 }\n     "links": {\n         "name": "hello:name"\,\n         "hello:STDOUT
 ": "greeting"\n     }\n }\n}\n\n\n\nSuch a format would not be able to expr
 ess every .t2flow or Scufl2 WB\nworkflow\, but by limiting the scope we can
  avoid many details which\nwould make the format too verbose or magic\, for
  instance port mapping\,\nalternative activities\, and complex activity con
 figurations.\n\n\nI hereby propose a meeting/Skype call  to discuss the nee
 d and\nimplementation plan of such an alternative serialisation format for\
 nSCUFL2 workflows - with the aim of workflows to be easy to edit and\nread 
 by hand. If you are interested in attending the meeting (no\nmatter if you 
 are part of the myGrid team or not)\, please mark your\navailability in the
  Doodle poll [3].\n\n\n\n[1] http://www.mygrid.org.uk/dev/wiki/display/deve
 loper/Taverna+Workflow+Bundle\n[2] http://www.mygrid.org.uk/dev/wiki/displa
 y/developer/Scufl2-WorkflowBundle\n[3] https://github.com/mygrid/scufl2/\n[
 4] https://github.com/myGrid/scufl2/blob/master/scufl2-api/src/test/resourc
 es/uk/org/taverna/scufl2/api/io/HelloWorld.txt\n[5] http://www.doodle.com/y
 bruwger8mi5bnn7\nView your event at http://www.google.com/calendar/event?ac
 tion=VIEW&eid=aDU5bDYwYWlzcTAwaDA0MHRlNnY3MDJ1azggdGF2ZXJuYS1oYWNrZXJzQGxpc
 3RzLnNvdXJjZWZvcmdlLm5ldA&tok=MTkjc3RpYW5AbXlncmlkLm9yZy51azllZWExZjIwMjVmY
 2I2NjUyNjA1OTNmYmM4MWFjYTdiZjNlYjMzMGU&ctz=Europe%2FLondon&hl=en_GB.
LAST-MODIFIED:20111011T095017Z
LOCATION:Skype / myGrid
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Scufl2 alternative script-like workflow format
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

Attachment: invite.ics
Description: application/ics

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
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/

Reply via email to