head 1.23; access; symbols; locks; strict; comment @# @; 1.23 date 2010.05.05.16.36.29; author RenatoDeGiovanni; state Exp; branches; next 1.22; 1.22 date 2009.09.10.19.37.49; author RenatoDeGiovanni; state Exp; branches; next 1.21; 1.21 date 2009.02.05.17.36.41; author RenatoDeGiovanni; state Exp; branches; next 1.20; 1.20 date 2009.01.07.20.28.57; author RenatoDeGiovanni; state Exp; branches; next 1.19; 1.19 date 2008.07.24.21.28.01; author RenatoDeGiovanni; state Exp; branches; next 1.18; 1.18 date 2008.02.19.17.47.22; author RenatoDeGiovanni; state Exp; branches; next 1.17; 1.17 date 2008.02.19.11.39.42; author RenatoDeGiovanni; state Exp; branches; next 1.16; 1.16 date 2007.12.27.18.23.15; author RenatoDeGiovanni; state Exp; branches; next 1.15; 1.15 date 2007.09.19.14.35.23; author RenatoDeGiovanni; state Exp; branches; next 1.14; 1.14 date 2007.04.13.01.33.21; author RenatoDeGiovanni; state Exp; branches; next 1.13; 1.13 date 2007.02.28.00.37.57; author RenatoDeGiovanni; state Exp; branches; next 1.12; 1.12 date 2007.01.28.23.06.37; author RenatoDeGiovanni; state Exp; branches; next 1.11; 1.11 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.10; 1.10 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.9; 1.9 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.8; 1.8 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.7; 1.7 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.6; 1.6 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.5; 1.5 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.4; 1.4 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.3; 1.3 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.2; 1.2 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.1; 1.1 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next ; desc @Initial revision @ 1.23 log @none @ text @%META:TOPICINFO{author="RenatoDeGiovanni" date="1273077389" format="1.1" version="1.23"}% ---+++ Road map: history and future plans * *April 2004:* Unification of [[DigirProtocol][DiGIR]] and [[BiocaseProtocol][BioCASe]] was considered a priority during the GBIF DADI sub-committee meeting in Oaxaca. * *June 2004:* GBIF commissioned a study that resulted in the [[http://www.cria.org.br/protocols/newprotocol.pdf][original integration proposal]]. * *October 2004:* Original proposal was presented during the TDWG meeting in Christchurch. * *May 2005:* First reference implementation of a TAPIR data provider (PyWrapper). * *November 7th to 11th, 2005:* TAPIR meeting to review the protocol (new version of the XML Schema available). * *January, 2006:* New set of changes incorporated in the protocol schema to address a few open issues that were left after the meeting. First attempt of a protocol feature freeze. See: http://lists.tdwg.org/pipermail/tdwg-tapir_lists.tdwg.org/2005-December/000096.html * *April 2006:* First TDWG TAG meeting requested study about the viability of using ontologies in TAPIR. * *May, 2006:* TDWG contracted TAPIR documentation work, which will include a charter, a formal specification and a user guide. * *May, 2006:* TAPIR charter finished. See: http://www.tdwg.org/subgroups/tapir/charter/ * *May, 2006:* Changes in TAPIR metadata response to make use of DublinCore, VCard and GeoRSS elements. See: http://lists.tdwg.org/pipermail/tdwg-tapir_lists.tdwg.org/2006-May/000208.html * *June, 2006:* IPGRI is now funding the PyWrapper update to support the latest version of the protocol. * *June/July, 2006:* Initial study about the possibility of making TAPIR compliant with ontologies and consequently improve output model mappings (See: SemanticMapping). The other possibility would be to drop dynamic output models (See: DroppingDynamicOutputModels). Although TDWG is already working on a general ontology, it will probably take some time until a stable and accepted ontology is defined. Decision was to postpone related changes in the protocol to a future version. * *July, 2006:* Adjustments made in the protocol during the PyWrapper update. See ImplementationAndDocumentationChanges. * *September, 2006:* PyWrapper adapted to the new version of TAPIR. * *September, 2006:* PyWrapper Config Tool adapted to TAPIR. * *October, 2006:* Formal specification finished. See: http://www.tdwg.org/dav/subgroups/tapir/1.0/docs/ * *October, 2006:* Release of the first official version of the protocol (1.0). * *October, 2006:* TAPIR approved as an official TDWG Task Group (as part of the TDWG Architecture Interest Group). * *January, 2007:* Minor changes suggested during the implementation of TapirLink (see: http://lists.tdwg.org/pipermail/tdwg-tapir/2007-January/000316.html). * *January, 2007:* Second TAPIR provider implementation available: TapirLink. * *February, 2007:* TAPIR developers workshop (see TapirWorkshop2007). * *April, 2007:* TAPIR Executive Summary finished. * *June, 2007:* TAPIR Network Builders' Guide finished. * *18th July, 2007:* First TAPIR service indexed by GBIF: Type collection of mollusca fossils from the Cenozoic of Java, Indonesia, and deposited in the Naturalis National Museum of Natural History, Netherlands (TAPIR service hosted by ETI BioInformatics). * *August, 2007:* Third TAPIR provider implementation available: TapirDotNET. * *September, 2007:* TAPIR promotional video available: http://www.youtube.com/watch?v=x9404is3RJ8 * *December, 2007:* TAPIR provider conformance tests available: TapirTester * *December, 2007:* First client library available: TapirChirp (PHP) * *July, 2008:* Online builders for output models and query templates: TapirBuilder * *December, 2008:* Second client library available: TapirJChirp (Java) * *5th February, 2009:* Specification submitted to the TDWG Standards Track. * *27th July, 2009:* All peer-reviews recommended acceptance. * *10th September, 2009:* Approved by the TDWG executive committee. Started the public review process. * *13th November, 2009:* TAPIR 1.0 approved as an official TDWG standard. @ 1.22 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1252611469" format="1.1" version="1.22"}% a68 1 ----------- d70 1 a70 1 * *?:* TAPIR approved as an official TDWG standard. @ 1.21 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1233855401" format="1.1" version="1.21"}% d65 4 @ 1.20 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1231360137" format="1.1" version="1.20"}% d64 1 @ 1.19 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1216934881" format="1.1" version="1.19"}% d58 1 a58 1 * *December, 2007:* First client library available: TapirChirp d62 2 @ 1.18 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1203443242" format="1.1" reprev="1.18" version="1.18"}% d60 2 a63 2 * *?:* Online builders for output models and query templates. @ 1.17 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1203421182" format="1.1" version="1.17"}% d6 1 a6 1 * *June 2004:* GBIF commissioned a study that resulted in the [[http://ww2.biocase.org/svn/tapir/tags/protocol/proposal_2004/report.pdf][OriginalIntegrationProposal]]. d50 2 a55 2 * *October, 2007:* First TAPIR provider indexed by GBIF: Collections of the New Zealand National Fungal Herbarium (TAPIR service hosted by Landcare Research). @ 1.16 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1198779795" format="1.1" version="1.16"}% d54 2 a63 2 * *?:* GBIF indexed the first TAPIR provider. @ 1.15 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1190212523" format="1.1" reprev="1.15" version="1.15"}% d38 2 d52 5 a56 1 * *September, 2007:* TAPIR promotional video available. d60 2 a63 4 * *?:* TAPIR approved as an official TDWG Task Group. * *?:* Regression tests available. @ 1.14 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1176428001" format="1.1" reprev="1.14" version="1.14"}% a43 2 ----------- d48 6 @ 1.13 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1172623077" format="1.1" reprev="1.13" version="1.13"}% d46 7 a52 1 * *?:* TAPIR Network Builders guide finished. @ 1.12 log @none @ text @d1 11 a11 1 %META:TOPICINFO{author="RenatoDeGiovanni" date="1170025597" format="1.1" version="1.12"}% d42 2 d46 1 a46 1 * *February, 2007:* TAPIR developers workshop. d48 1 a48 1 * *?:* TAPIR Network Builders guide finished. d50 1 a50 1 * *?:* Regression tests available.@ 1.11 log @Revision 11 @ text @d1 38 a38 31 * *November 7th to 11th, 2005:* TAPIR meeting to review the protocol (new version of the XML Schema available). * *January, 2006:* New set of changes incorporated in the protocol schema to address a few open issues that were left after the meeting. First attempt of a protocol feature freeze. See: http://lists.tdwg.org/pipermail/tdwg-tapir_lists.tdwg.org/2005-December/000096.html * *April 2006:* First TDWG TAG meeting requested study about the viability of using ontologies in TAPIR. * *May, 2006:* TDWG contracted TAPIR documentation work, which will include a charter, a formal specification and a user guide. * *May, 2006:* TAPIR charter finished. * *May, 2006:* Changes in TAPIR metadata response to make use of DublinCore, VCard and GeoRSS elements. See: http://lists.tdwg.org/pipermail/tdwg-tapir_lists.tdwg.org/2006-May/000208.html * *June, 2006:* IPGRI is now funding the PyWrapper update to support the latest version of the protocol. * *June/July, 2006:* Initial study about the possibility of making TAPIR compliant with ontologies and consequently improve output model mappings (See: SemanticMapping). The other possibility would be to drop dynamic output models (See: DroppingDynamicOutputModels). Although TDWG is already working on a general ontology, it will probably take some time until a stable and accepted ontology is defined. Decision was to postpone related changes in the protocol to a future version. * *July, 2006:* Adjustments made in the protocol during the PyWrapper update. See ImplementationAndDocumentationChanges. ----------- * *September, 2006:* PyWrapper adapted to the new version of TAPIR. * *September, 2006:* PyWrapper Config Tool adapted to TAPIR. * *October, 2006:* Formal specification and user guide finished. * *October, 2006:* Release of the first official version of the protocol (1.0). * *?:* Regression tests available. * *?:* TAPIR supported by DiGIR2 (without interpreting custom output models). @ 1.10 log @Revision 10 @ text @d21 1 a21 1 * *August, 2006:* Formal specification and user guide finished. d23 1 a23 1 * *August, 2006:* PyWrapper adapted to the new version of TAPIR. d25 1 a25 1 * *August, 2006:* PyWrapper Config Tool adapted to TAPIR. d27 1 a27 1 * *September, 2006:* Release of the first official version of the protocol (1.0). @ 1.9 log @Revision 9 @ text @d15 1 a15 1 ----------- d17 1 a17 1 * *June, 2006:* A new set of changes is being considered to make TAPIR compliant with ontologies and consequently improve output model mappings (See: SemanticMapping). Another possibility is to drop dynamic output models (See: DroppingDynamicOutputModels). A decision is expected by the end of this month. d19 1 a19 1 * *July, 2006:* Probably some adjustments to the protocol will be necessary during the PyWrapper update. d24 1 @ 1.8 log @Revision 8 @ text @a24 1 * *August, 2006:* PyWrapper local query tool adapted to TAPIR. @ 1.7 log @Revision 7 @ text @d1 1 a1 1 * November 7th to 11th, 2005: TAPIR meeting to review the protocol (new version of the XML Schema available). d3 1 a3 1 * January 5th, 2006: Protocol feature freeze - only corrections to eventual issues should be addressed after this date. d5 1 a5 1 * February, 2006: Previous BioCASe configurator adapted to TAPIR. d7 1 a7 1 * April, 2006: PyWrapper adapted to the new version of TAPIR. d9 1 a9 1 * End of first quarter, 2006: TAPIR supported by DiGIR2 (without interpreting custom output models). d11 1 a11 1 * End of first quarter, 2006: Release of the first official version of the protocol (1.0). d13 1 a13 1 * ?: Previous local BioCASe query tool adapted to TAPIR. d15 1 a15 1 * ?: Regression tests available. d17 15 a31 1 * ?: Formal specification available. @ 1.6 log @Revision 6 @ text @a8 2 * End of first quarter, 2006: Previous local BioCASe query tool adapted to TAPIR. d13 2 @ 1.5 log @Revision 5 @ text @d5 1 a5 1 * January, 2006: PyWrapper adapted to the new version of TAPIR. d7 1 a7 1 * January, 2006: Previous BioCASe configurator adapted to TAPIR. d9 1 a9 1 * February, 2006: Previous local BioCASe query tool adapted to TAPIR. @ 1.4 log @Revision 4 @ text @d3 1 a3 1 * December 15th: Protocol feature freeze - only corrections to eventual issues should be addressed after this date. @ 1.3 log @Revision 3 @ text @a0 2 RoadMap @ 1.2 log @Revision 2 @ text @d5 1 a5 1 * November 20th: Protocol feature freeze - only corrections to eventual issues should be addressed after this date. d13 1 a13 1 * December 20th, 2005: Release of the first official version of the protocol (1.0). d15 1 a15 1 * End of first quarter, 2006: TAPIR supported by DiGIR2 (without interpreting custom output models). @ 1.1 log @Initial revision @ text @d7 1 a7 1 * ..., 2005: TAPIR supported by DiGIR2 (without interpreting custom output models). d9 1 a9 1 * ..., 2005: PyWrapper adapted to the new version of TAPIR. d11 1 a11 1 * ..., 2005: Previous BioCASe configurator adapted to TAPIR. d15 2 @