ally interested in workflow engines in
general and feel that adding CWL support to Taverna is a great idea for
improving portability. Is there any part of the source code you can direct me
to so that I can get a better idea of how this support can be added?)
> GSOC: Add Common Workflow L
u can direct me to so that
I can get a better idea of how this support can be added?
> GSOC: Add Common Workflow Language support to Taverna
> -
>
> Key: TAVERNA-900
> URL: https://issues.apache.org/j
tool. I'm really interested in workflow engines in general
and feel that adding CWL support to Taverna is a great idea for improving
portability. Is there any part of the source code you can direct me to so that
I can get a better idea of how this support can be added?
> GSOC: Add Common
Hi all,
I hope you're doing well.
Please find in the link below the not finished proposal.
https://docs.google.com/document/d/1nwq1A_BUiXX8lKxwWg8-n-IuI_1F4dX7ZrmGOliTrXs/edit?usp=sharing
I am not sure how the proposal needs to be in terms of length, details and
content.
I am sending you the pro
Hi Stian,
Thank you so much for your reply.
I am really sorry for my late reply.
Thank you for the information you provided. I strongly agree with what you
said.
I am seeing the tutorials and reading the doc. Soon I will start preparing
the proposal and I will keep you in touch.
Thank you once a
Hi, Majdi, thank you for your intest in GSOC and Apache Taverna!
Apologies for late reply.
On Thu, 15 Feb 2018 05:08:55 +0100, Majdi Haouech
wrote:
> I have worked with different languages and technologies, to name a few:
> Java, C, C++, Python, JS, Git, OWL, JavaEE, RabbitMQ, Maven.
> I am also
for your interest in GSOC, Apache Taverna and CWL!
You can start with having a look at the [Common Workflow Language user
guide|http://www.commonwl.org/user_guide/] and try it using the
[cwltool|https://pypi.python.org/pypi/cwltool] reference implementation.
What this GSOC project is proposing i
ommon Workflow Language is close to what I'm doing for
Alien4Cloud. So this project is pretty interesting for me. Therefore, I'd like
to have some information to start this task.
Thank you
> GSOC: Add Common Workflow
Hello Michael,
Thank you so much for your reply.
I am a final year MS student and I have worked on several projects in
school and during my two internships at IBM.
I have worked with different languages and technologies, to name a few:
Java, C, C++, Python, JS, Git, OWL, JavaEE, RabbitMQ, Maven.
I
Hello Majdi,
Thank you for your interest and enthusiasm! Taverna internals are not my
expertise, but I can assist with CWL and general workflow questions.
Could you expand on:
> I am used to work with different technologies and dealing with different
specifications.
> I am also used to work with
Hi,
I am a software engineering MS student at Telecom SudParis in France.
I am really interested by this GSOC project.
Here's what I understand about the project.
In this project we need to create a plugin that exports and imports CWL
workflows.
First, I need to be familiar with the CWL specificat
onents: Taverna Language
>Reporter: Stian Soiland-Reyes
>Priority: Minor
> Labels: cwl, gsoc2016
>
> Common Workflow Language
> http://common-workflow-language.github.io/
> ..is an emerging standard for computational workflows with a focus on
> bioin
[
https://issues.apache.org/jira/browse/TAVERNA-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stian Soiland-Reyes updated TAVERNA-900:
Summary: GSOC: Add Common Workflow Language support to Taverna (was: Add
Common
add support for [Common Workflow
Language|http://commonwl.org/] (CWL) in [Apache
Taverna|http://taverna.incubator.apache.org/] (incubating).
The Apache Taverna community believe CWL support can be added to Taverna in a
progressive fashion, and therefore the GSOC student can achieve success in
add support for [Common Workflow
Language|http://commonwl.org/] (CWL) in [Apache
Taverna|http://taverna.incubator.apache.org/] (incubating).
The Apache Taverna community believe CWL support can be added to Taverna in a
progressive fashion, and therefore the GSOC student can achieve success in
onents: Taverna Language
>Reporter: Stian Soiland-Reyes
>Priority: Minor
> Labels: cwl, gsoc2016, gsoc2018
>
> Common Workflow Language
> http://common-workflow-language.github.io/
> ..is an emerging standard for computational workflows with a focus
: cwl docker gsoc2016 java json json-ld python workflow yaml)
> Add Common Workflow Language support to Taverna
> ---
>
> Key: TAVERNA-900
> URL: https://issues.apache.org/jira/browse/TAVERNA-900
>
gsoc2016 java json json-ld python workflow yaml)
> Add Common Workflow Language support to Taverna
> ---
>
> Key: TAVERNA-900
> URL: https://issues.apache.org/jira/browse/TAVERNA-900
> Proje
ng-a-proposal/
for suggestions for your proposal, and a template here:
http://community.staging.apache.org/gsoc#application-template
> Parser for Common Workflow Language workflows
> -
>
> Key: TAVERNA-877
> UR
ng-a-proposal/
for suggestions for your proposal, and a template here:
http://community.staging.apache.org/gsoc#application-template
> Add Common Workflow Language support to Taverna
> ---
>
> Key: TAVERNA-900
>
ng-a-proposal/
for suggestions for your proposal, and a template here:
http://community.staging.apache.org/gsoc#application-template
> Parser for Common Workflow Language workflows
> -
>
> Key: TAVERNA-877
> UR
[
https://issues.apache.org/jira/browse/TAVERNA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stian Soiland-Reyes updated TAVERNA-877:
Summary: Parser for Common Workflow Language workflows (was: SCUFL2-reader
for
[
https://issues.apache.org/jira/browse/TAVERNA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stian Soiland-Reyes updated TAVERNA-877:
Labels: cwl gsoc2016 (was: cwl)
> SCUFL2-reader for Common Workflow Langu
what you want to get out of GSOC this year.
> Add Common Workflow Language support to Taverna
> ---
>
> Key: TAVERNA-900
> URL: https://issues.apache.org/jira/browse/TAVERNA-900
> P
but I didn't receive any answer :(
> Add Common Workflow Language support to Taverna
> ---
>
> Key: TAVERNA-900
> URL: https://issues.apache.org/jira/browse/TAVERNA-900
> Project: Apac
support for [Common Workflow
Language|http://commonwl.org/] (CWL) in [Apache
Taverna|http://taverna.incubator.apache.org/] (incubating).
The Apache Taverna community believe CWL support can be added to Taverna in a
progressive fashion, and therefore the GSOC student can achieve success in
multiple
two of the tasks in detail. So,
perhaps you can look at the different tasks and choose which you are most
interested in.
Alan
> Add Common Workflow Language support to Taverna
> ---
>
> Key: TAVERNA-900
>
/jira/browse/AURORA-1164
Could you give me more guidelines about this?
Thanks!!
> Add Common Workflow Language support to Taverna
> ---
>
> Key: TAVERNA-900
> URL: https://issues.apache.org/jira/browse/TAVERNA-90
add support for [Common Workflow
Language|http://commonwl.org/] (CWL) in [Apache
Taverna|http://taverna.incubator.apache.org/] (incubating).
The Apache Taverna community believe CWL support can be added to Taverna in a
progressive fashion, and therefore the GSOC student can achieve success in
Stian Soiland-Reyes created TAVERNA-900:
---
Summary: Add Common Workflow Language support to Taverna
Key: TAVERNA-900
URL: https://issues.apache.org/jira/browse/TAVERNA-900
Project: Apache Taverna
>> > such a way.). CWL is a bit more on a "hacker level" - which I think
>> > we can be more comfortable with catering for.
>> >
>> >
>> > For CWL, Taverna is a valuable proposition as we know how to handle
>> > workflow provenance, we
Stian Soiland-Reyes created TAVERNA-877:
---
Summary: SCUFL2-reader for Common Workflow Language workflows
Key: TAVERNA-877
URL: https://issues.apache.org/jira/browse/TAVERNA-877
Project: Apache
s a valuable proposition as we know how to handle
> > workflow provenance, we can easily add preservation aspects (e.g.
> > packaging all the docker images used in a run). The Taverna Workbench
> > has a pluggable way to add service descriptions, so we could connect
> > to
istries and turn Taverna into a "CWL editor".
>
>
> On 4 December 2015 at 17:05, Alan Williams wrote:
>> On 04-Dec-15 15:28, Ian Dunlop wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA256
>>>
>>> Hello,
>>>
&g
On 10-Dec-15 09:35, Stian Soiland-Reyes wrote:
I've signed up for the CWL hackathon, but I hope others would join!
I will go - I just didn't care what date it is :)
Alan
-
>> Hash: SHA256
>>
>> Hello,
>>
>> Does anyone have views on how Apache Taverna fits into the goals of
>> the Common Workflow Language project
>> https://github.com/common-workflow-language/common-workflow-language ?
>> Should taverna adopt CWL i
On 04-Dec-15 15:28, Ian Dunlop wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Does anyone have views on how Apache Taverna fits into the goals of
the Common Workflow Language project
https://github.com/common-workflow-language/common-workflow-language ?
Should taverna adopt CWL
-
Hash: SHA256
Hello,
Does anyone have views on how Apache Taverna fits into the goals of
the Common Workflow Language project
https://github.com/common-workflow-language/common-workflow-language ?
Should taverna adopt CWL instead of SCUFL2. Are there things that
SCUFL2 or the current taverna eng
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Does anyone have views on how Apache Taverna fits into the goals of
the Common Workflow Language project
https://github.com/common-workflow-language/common-workflow-language ?
Should taverna adopt CWL instead of SCUFL2. Are there things that
39 matches
Mail list logo
