Changes between Version 48 and Version 49 of PhyloWS_workgroup

Show
Ignore:
Timestamp:
2008/02/15 16:09:52 (16 years ago)
Author:
rvos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PhyloWS_workgroup

    v48 v49  
    88 * Have another round of OTU discussions 
    99=== Formalizing scope, use cases, requirements (Tuesday) === 
    10  * Identify inputs and outputs (white board) 
     10 * In a [http://hackathon.dbcls.jp/attachment/wiki/PhyloWS_workgroup/P1070128.JPG white board] exercise, we identified plausible input and output data types for phyloinformatic webservices. Plausibility is defined by our being able to imagine [https://www.nescent.org/wg_evoinfo/PhyloWS#Use_Cases use cases] (no time line for implementation implied, the goal here is to come up with interfaces) 
    1111 * For all I/O combinations, imagine a [https://www.nescent.org/wg/evoinfo/index.php?title=PhyloWS#Use_Cases use case], move to NESCent wiki 
    1212 * For each use case, classify [https://www.nescent.org/wg/evoinfo/index.php?title=PhyloWS#PhyloWS_Requirements scope and requirements] 
    … …  
    8484  * But we usually also have (possibly multiple) support values associated with tree branches 
    8585 
    86 == Services versus their Inputs and Outputs   == 
    87  
    88 In a [http://hackathon.dbcls.jp/attachment/wiki/PhyloWS_workgroup/P1070128.JPG white board] exercise, we identified plausible input and output data types for phyloinformatic webservices. Plausibility is defined by our being able to imagine [https://www.nescent.org/wg_evoinfo/PhyloWS#Use_Cases use cases] (no time line for implementation implied, the goal here is to come up with interfaces) 
    89  
    9086=== Inputs === 
    9187The input data types defined here do not imply pass-by-value, i.e. "One Tree" could be some kind of identifier. In addition, it looks like several services need multiple data types (e.g. a matrix + a tree, in order to return a tree score). Given that accumulate-and-fire (i.e. stateful operations, where you first post a matrix, then a tree) is a Bad Thing, and that tunneling multiple data types in a single attachment or body (e.g. a chunk of nexus/nexml) is also a Bad Thing, it seems that these combinations of data would be submitted as multiple post parameters.