1. Interoperability among phylogenetic data resources Rutger Vos University of British Columbia Recent additions to the TreeBASE2 architecture
2.
3.
4.
5.
6. PhyloWS URL API http://purl.org phylo treebase phylows study/TB2:S1787 / / / / Permanent URL resolver domain Subdomain for any phylogenetic resource Subdomain for TreeBASE Subdomain for PhyloWS API Object ID
Phylogenetic web resources are often closed data silos, i.e.applications that do not interact with other applications or information systems. Until recently this has also been the case forTreeBASE2's development: it has been constructed such that data can only be accessed through the browser interface, and only be downloaded in NEXUS format. To make TreeBASE2 a resource that is visited more often in the research cycle then just when research results need to be deposited prior to publication, this situation has had to change. To this end, the development team has started to incorporate the tools and practices created by the EvoInfo working group( http: //evoinfo . nescent .org ) in TreeBASE2's architecture. Among these are: "cool URIs" to identify and de-reference phylogenetic data objects; a PhyloWS-compliant web service interface allowing programmatic access to TreeBASE2 data; database searching using Common Query Language constructs; data export in NeXML and RDF. I will describe what the implications of each of these are, and what additional functionality we expect to add in the near future.
![Introducing TreeBASE3.0 ,[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)