Changes between Version 26 and Version 27 of PhyloWS_workgroup

Show
Ignore:
Timestamp:
2008/02/12 16:58:11 (10 years ago)
Author:
rvos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PhyloWS_workgroup

    v26 v27  
    66 * Accumulating [https://www.nescent.org/wg_evoinfo/PhyloWS#Use_Cases use-cases] 
    77 * Formulating a task-oriented API [https://www.nescent.org/wg_evoinfo/PhyloWS#PhyloWS_Requirements requirements] description 
    8  * Identify "method signatures" for API (e.g. input: a tree, output: a number for methods that return tree scores) 
     8 * Identify "method signatures" for API (e.g. input: a tree, output: a number for methods that return tree scores). A whiteboard sketch exercise indicated that the following might be plausible inputs: 1 tree, pair of trees, set of trees; 1 OTU, pair of OTUs, set of OTUs; 1 node, pair of nodes, set of nodes; 1 character, set of characters; 1 seq (character state sequence of various types), pair of seqs, set of seqs; a data matrix and some combinations of these types: OTU(s) and a data matrix, tree and data matrix. Plausible outputs are the same as the mentioned inputs + numbers (floats and ints) + strings and sets of strings. 
    99 * Proposing a concrete REST~~ or SOAP-~~based API 
    1010 * Propose input/output formats (e.g. http://$resource?view=$format where $resource is an opaque url to some data resource (matrix, tree, etc) and $format something like nexus, phylip, nexml, phyloxml, json, etc.)