Changes between Version 11 and Version 12 of PhyloWS_workgroup

Show
Ignore:
Timestamp:
2008/02/12 12:25:30 (17 years ago)
Author:
rvos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PhyloWS_workgroup

    v11 v12  
    1 At present there is no standard web-service API for phylogenetic data that would allow integration of phylogenetic data and service providers into the programmable web. Hence, current approaches to integrate data and services into workflows are highly specific to the integration platform (CIPRES, Bioperl, Bio::Phylo, Kepler), and nearly unusable in other environments. 
     1At present there is no standard web-service API for phylogenetic data that would allow integration of phylogenetic data and service providers into the programmable web. Hence, current approaches to integrate data and services into workflows are highly specific to the integration platform (CIPRES, Bioperl, Bio::Phylo, Kepler), and nearly unusable in other environments. This work group is formed to remedy this (to the extent that that's possible in a week). 
    22 
    33Here are several ideas for tasks we can work on at the hackathon: 
    44 * Defining scope  
    55  * Issue of identifiers and OTUs 
    6  * Accumulating use-cases  
    7   * OTU-oriented queries: 
    8    * Need ability to obtain sequence(s) and taxon (taxa) for a leaf (or generally, a node) 
    9    * Finding trees by sequence (rather than the OTU name)  
    10  * Formulating a task-oriented API requirements description 
     6 * Accumulating [https://www.nescent.org/wg_evoinfo/PhyloWS#Use_Cases use-cases] 
     7 * Formulating a task-oriented API [https://www.nescent.org/wg_evoinfo/PhyloWS#PhyloWS_Requirements requirements] description 
    118 * Identify "method signatures" for API (e.g. input: a tree, output: a number for methods that return tree scores) 
    129 * Proposing a concrete REST~~ or SOAP-~~based API