|
From: | Alan R Williams |
Subject: | [Myexperiment-discuss] Changes to REST API for components |
Date: | Tue, 07 May 2013 12:57:31 +0100 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 |
Hello everybody,At the moment, components (and component profiles, families and versions) are implemented in myExperiment as packs, files, workflows and versions of them. When the REST API is used to talk to myExperiment, the components can only be dealt with as their myExperiment implementation.
This makes it hard for clients to talk to myExperiment about components. At the moment, the Java code in Taverna for talking to myExperiment is "hairy" and complicated. There is a need for Ruby applications to also be able to talk to myExperiment about components.
It would greatly help the BioVeL and SCAPE projects if the REST API dealt in components. There would then by one place for the mapping to the underlying implementation i.e. myExperiment side. This would allow later changes to the myExperiment implementation without the rewriting of the Ruby and Java Gems/packages.
What further information do the myExperiment development team need about the requirements?
Alan
[Prev in Thread] | Current Thread | [Next in Thread] |