On Mon, Apr 18, 2016 at 2:11 PM, Stian Soiland-Reyes <[email protected]> wrote:
> Thank you for explaining your project! > > (BTW: Edi has already talked to me and Alan in person in Manchester > about this work) > > > I think it makes sense to start with 2.5 plugin as you say, and then > adapt it for Taverna 3. This means you can try it out in a full > workbench right away - as we have not yet release Apache Taverna 3 > workbench. Then you can update the code for 3.0 - the changes are > mainly different package names and that it will run under OSGi rather > than our own plugin system. > > > Feel free to ask this list any questions during development of your > plugin - I'm sure the other folk will also be able to help you. > Thank you > > You might also find it useful to follow this list as there are three > potential Google Summer of Code students this year who would be > developing Taverna and Taverna plugins as well (but for Common > Workflow Language, Docker and Taverna Mobile) > > I'm aware of that and I have been following your discussions. > > You'll probably find this tutorial useful for the Taverna 2.5 plugin: > > > http://dev.mygrid.org.uk/wiki/display/developer/Creating+plugins+for+Taverna+2 I have already completed the plugin invocation and discovery tutorials. In addition, I read the Development, releases and testing procedures tutorial. Please feel free to suggest any other tutorials that might help. > There is unfortunately not an updated plugin tutorial for 3.0 - which > changes slightly how you do Activity configuration. If you keep your > plugin using a Jackson JSONObject as a configuration bean - then it > should be straight forwards to later update it for Taverna 3. > > Ok. I will use JSONObject. > > Are you considering contributing your plugin to Apache Taverna? We > would be very happy if you consider this - in which case I hope you > would be OK to sign and send in a Contributor License Agreement to > ASF: > > https://www.apache.org/licenses/icla.txt > > (You would need to send it to [email protected] ) > I am very happy to contribute to Apache Taverna. Do they need a hard copy of the Contributor License Agreement? > > If you do this earlier, it makes it easier for us to accept your code > early rather than requiring an additional Intellectual Property > clearance process at the end of your project. (BTW - this is the > pattern we have used for Google Summer of Code students) > > > If contributed, your plugin would need to use dependencies that are > compatible with the Apache license - > http://www.apache.org/legal/resolved.html - in short GPL and LGPL are > not allowed, but pretty much anything open source is OK as a pom.xml > dependency. Inclusion of third-party work in the source code is much > trickier area - avoid this if possible. > > > > > On 18 April 2016 at 13:09, Edi KARADUMI <[email protected]> wrote: > > Greetings, > > > > My name is Edi Karadumi. I am pursuing a Master Degree in Software > > Engineering at the University of Manchester. > > > > The aim of my dissertation project is to add geospatial services based on > > The Open Geospatial Consortium (OGC) standards to Taverna. Firstly, a > > plugin that invokes and discovers OGC Web Processing Services (WPS) will > be > > implemented. Therefore, Taverna users will be able to discover WPS > services > > from a user specified wps server, configure it, and then execute it. The > > project will be extended further to support OGC Web Map Servies and OGC > > Sensor Observation Services. > > > > A generic approach will be developed in order to support most of OGC > > service standards. The plugin will be developed for Taverna 2.5, and > after > > that it will be migrated to the most recent development of Taverna 3. > > > > If you are interested in this functionality, I welcome any > > suggestions and, especially, offers to test my work > > > > Kind Regards, > > Edi Karadumi > > > > -- > Stian Soiland-Reyes > Apache Taverna (incubating), Apache Commons RDF (incubating) > http://orcid.org/0000-0001-9842-9718 >
