Changes between Version 44 and Version 45 of PhyloWS_workgroup

Show
Ignore:
Timestamp:
2008/02/15 15:51:47 (11 years ago)
Author:
rvos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PhyloWS_workgroup

    v44 v45  
    11== PhyloWS BioHackathon Report == 
    22=== Brainstorm sessions (Monday) === 
    3 * What's our scope for now? 
    4 * Accumulate use cases 
    5 * Accumulate requirements 
    6 * Propose a simple API 
    7 * Start reference implementations 
    8 * Have another round of OTU discussions 
     3 * What's our scope for now? 
     4 * Accumulate use cases 
     5 * Accumulate requirements 
     6 * Propose a simple API 
     7 * Start reference implementations 
     8 * Have another round of OTU discussions 
    99=== Formalizing scope, use cases, requirements (Tuesday) === 
    10 * Identify inputs and outputs (white board) 
    11 * 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 
    12 * For each use case, classify [https://www.nescent.org/wg/evoinfo/index.php?title=PhyloWS#PhyloWS_Requirements scope] and requirements 
     10 * Identify inputs and outputs (white board) 
     11 * 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 
     12 * For each use case, classify [https://www.nescent.org/wg/evoinfo/index.php?title=PhyloWS#PhyloWS_Requirements scope] and requirements 
    1313=== Scopes === 
    14 * '''Phylogenetic tree database''', i.e. a persistence service based on BioSQL 
    15 * '''Phylogenetic data conversion''', i.e. make sure that inputs and outputs of data work syntactically 
    16 * '''Phylogenetic data analysis''', i.e. actual computations 
     14 * '''Phylogenetic tree database''', i.e. a persistence service based on BioSQL 
     15 * '''Phylogenetic data conversion''', i.e. make sure that inputs and outputs of data work syntactically 
     16 * '''Phylogenetic data analysis''', i.e. actual computations 
    1717=== API design === 
    1818''Assuming that syntax and semantics of the data can be solved, what would be the syntax and semantics of making the connections?'' 
    1919=== API design principles === 
    20 # Stateless REST, no accumulate-and-fire 
    21 # Architecture modeled as resources on which CRUD operations are performed 
    22 # Use common HTTP methods (GET, PUT, POST, DELETE) 
    23 # Describe RESTful API in WSDL 2.0 
    24 # Reuse prior art 
     20 # Stateless REST, no accumulate-and-fire 
     21 # Architecture modeled as resources on which CRUD operations are performed 
     22 # Use common HTTP methods (GET, PUT, POST, DELETE) 
     23 # Describe RESTful API in WSDL 2.0 
     24 # Reuse prior art 
    2525=== URL API === 
    26 We started to design a URL API (pathinfo + query strings) on the NESCent Wiki 
     26We started to design a URL API (pathinfo + query strings) on the [https://www.nescent.org/wg_evoinfo/PhyloWS/REST NESCent Wiki] 
    2727=== Actual implementation === 
    2828All displacement activities aside, we did some coding: 
    29 * Started conversion and persistence services 
    30 * Improve plumbing (format support, database support) 
     29 * Started conversion and persistence services 
     30 * Improve plumbing (format support, database support) 
    3131=== Moving forward === 
    32 * Expand/formalize API, following manifesto? Recommendations? 
    33 * Implement services. 
     32 * Expand/formalize API, following manifesto? Recommendations? 
     33 * Implement services. 
    3434 
    3535