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.
General Protocol Requirements
Integrate the CurrentProtocols being used by different networks from the biodiversity informatics community.
(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.
Dynamic processing of output models is considered experimental. Data providers are encouraged to declare the specific output models that are supported by them.