Welcome! This Wiki was created for discussing and documenting a unified 2nd generation query protocol to supersede the CurrentProtocols in use within the biodiversity informatics community.
Take a look at the RSS Feed or WebNotify if you want to subscribe to news from this wiki.
Introduction
During the 2004 TDWG meeting in Christchurch, NZ, the presented unified protocol was named TAPIR, TDWG Access Protocol for Information Retrieval. It was agreed to start testing the protocol by reimplementing two data provider software, each one carried out by one of the existing network communities, BioCASe and DiGIR.
The previous BioCASePyWrapper (http://www.pywrapper.org) and PHP DiGIR provider (a new version known as TapirLink) are already fully functional TAPIR providers.
(output models used to be called views, thats why you will still find the term view being mentioned in some places)
Are models determinate or do they depend upon the providers datasource structure? Is the current model definition sufficient? In particular some potential problems have surfaced during the PyWrapper implementation:
ObjectOrientedApproach: Make TAPIR truly object oriented and serve interlinked, compound objects instead of XML documents. A very different approach which causes a lot of reorganisation of the protocol. Promosing for the future in a time where GUIDs are omnipresent.