Context Navigation

Changes between Version 39 and Version 40 of PhyloWS_workgroup

v39	v40
40	40	The 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.
41	41	* '''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
42		* '''Pair of Trees''' - exactly two trees, which function as inputs for tree-to-tree distance calculations
	42	* '''Pair of Trees''' - exactly two trees, which function as inputs for tree reconciliation (e.g. duplication inference) or for tree-to-tree distance calculations
43	43	* '''Set of Trees''' - input for consensus calculations, or as query topologies
44	44	* '''One OTU''' - exactly one OTU for which associated data (trees or matrices that contain it) and metadata might be retrieved