| 34 | |

| 35 | == Tuesday session == |

| 36 | |

| 37 | In a 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) |

| 38 | |

| 39 | === Inputs === |

| 40 | * '''One Tree''' - exactly one tree, which might function as a query topology, as an input for topology metric calculations, or as something for which associated data (matrices) and metadata might be retrieved |

| 41 | * '''Pair of Trees''' - exactly two trees, which function as inputs for tree-to-tree distance calculations |

| 42 | * '''Set of Trees''' - input for consensus calculations, or as query topologies |

| 43 | * '''One OTU''' - exactly one OTU for which associated data (trees or matrices that contain it) and metadata might be retrieved |

| 44 | * '''Pair of OTUs''' - exactly two OTUs, as input for topological queries (MRCA) and calculations (patristic distance) |

| 45 | * '''Set of OTUs''' - input for topological queries (MRCA) and for which data (trees or matrices that contain them) and metadata might be retrieved |

| 46 | * '''One Node''' - input for tree traversal operations (parent, children) and for which metadata might be retrieved |

| 47 | * '''Pair of Nodes''' - input for topological queries (MRCA) and calculations (patristic distance) |

| 48 | * '''Set of Nodes''' - input for topological queries (MRCA) |

| 49 | * '''One character''' - exactly one character (matrix column) for which calculations are performed (variability) and metadata is retrieved |