-
Notifications
You must be signed in to change notification settings - Fork 7
Release notes for web API v3
Jonathan A Rees edited this page Feb 14, 2016
·
37 revisions
this is work in progress
This page gives information for users of the Open Tree of Life v2 web API regarding the transition to v3.
Full documentation for the v3 web API is here: Open Tree of Life Web APIs
- All
graph/methods are discontinued, not available even under their v2/ URLs, with no replacement (with the exception ofgraph/node_infowhich is nowtree_of_life/node_info)
- Synthetic tree node ids are written as strings instead of integers
-
include_childrenboolean parameter to thetaxonomy/taxonmethod, andchildrenin result (list of taxon descriptions similar toinclude_lineage; compare arguson)
- Rename
taxonomy/taxonmethod totaxonomy/taxon_infofor consistency withtree_of_life/node_info - Parameter and output field names normalization:
-
ott_idrather thanottID(intaxonomy/taxon_info) andot:ottId(intnrs/methods) -
nameortax_namerather thanot:ottTaxonName(ArguSON currently usesname) -
tax_sourcesinstead oftax_source -
tax_rankrather thanrankintaxonomy/taxon, or else changetax_ranktorankArguSON. Should be consistent
-
- In
node_info, the sources are returned astax_sourceswhose value is a list of strings - Rename
taxonomy/licamethod totaxonomy/mrca - It's proposed to split
dateintree_of_life/aboutintodate_createdanddate_deployed- are both pieces of information available now? - It's been suggested to write
taxon_idinstead ofott_id - It's been noted that
tree_idis used in two different ways: for synthetic tree labels (arbitrary strings) and for source tree ids (must be XML ids). Might be better to have distinct names for the two.
- Considering:
/studies/all_studies(list of ids for all studies) - we have the method, just a matter of exposing and documenting it - Method for getting a subtree of the synthetic tree (exists, but with odd name and calling convention)
- Optional argument to
tree_of_life/methods specifying which synthetic tree to use (currently there's only one, but in future there could be several) (this might already be implemented in tm-lite) - what else? see google doc
- advertised conflict report generator
- new study/tree index (OTI replacement) using GET instead of POST etc.
ArguSON is not necessarily ready for outside users. Changes to ArguSON are given here: "Arguson" format
The phylesystem methods use camelCase. Probably not going to be able to make this consistent, this time around at least.