head 1.36; access; symbols; locks; strict; comment @# @; 1.36 date 2008.12.22.18.14.58; author RenatoDeGiovanni; state Exp; branches; next 1.35; 1.35 date 2007.02.23.16.26.48; author RicardoPereira; state Exp; branches; next 1.34; 1.34 date 2007.01.10.12.50.29; author RicardoPereira; state Exp; branches; next 1.33; 1.33 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.32; 1.32 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.31; 1.31 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.30; 1.30 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.29; 1.29 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.28; 1.28 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.27; 1.27 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.26; 1.26 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.25; 1.25 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.24; 1.24 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.23; 1.23 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.22; 1.22 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.21; 1.21 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.20; 1.20 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.19; 1.19 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.18; 1.18 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.17; 1.17 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.16; 1.16 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.15; 1.15 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.14; 1.14 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.13; 1.13 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.12; 1.12 date 2007.01.09.00.00.00; author MoinMoin; 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.36 log @none @ text @%META:TOPICINFO{author="RenatoDeGiovanni" date="1229969698" format="1.1" reprev="1.36" version="1.36"}% This section provides some examples of common TAPIR messages. The latest version of the examples can always be found in the subversion repository. This page is only updated once in a while, so it might be that the examples below are not valid against the latest schema. But they will only vary in minor details. http://ww2.biocase.org/svn/tapir/trunk/protocol/examples/ Messages in TAPIR should be sent through HTTP. Every TAPIR message can be sent as an XML encoded document as defined by the TAPIR schema or alternatively through a list of URL [[GetInvokedOperations][parameters]] specified by TAPIR as well. This allows to invoke all TAPIR operations through HTTP GET (using the [[GetInvokedOperations][parameters]]) or trough HTTP POST (using [[GetInvokedOperations][parameters]] or sending an XML document). Here we provide a parameterized version of every example and the corresponding XML version. They MUST generate the same result from a TAPIR compliant service. The parameterized version is represented with an*unencoded* URL string. ---- ---+++ TAPIR Operations * [[#p][Ping]] * [[#preq][request]] * [[#presp][response]] * [[#c][Capabilities]] * [[#creq][request]] * [[#cresp][response]] * [[#m][Metadata]] * [[#mreq][request]] * [[#mresp][response]] * [[#i][Inventory]] * [[#it][inventory template]] * [[#ireq][request]] * [[#iresp][response]] * [[#s][Search]] * [[#om][output model]] * [[#st][search template]] * [[#sreq][request]] * [[#sresp][response]] ---- ---++ Ping operation *HTTP Parameters* * http://wrapper_end_point?op=ping *XML message*
http://accesspoint_url
*Response*
---- ---++ Metadata operation *HTTP Parameters* * http://wrapper_end_point?op=metadata *XML message*
*Response* BioCASe training http://purl.org/dc/dcmitype/Service http://localhost:8080/tapir/pywrapper/training This testing database is used in BioCASE workshops and other events. This database was gratefully provide by the Herbarium at the Universidad of Barcelona CeDocBiv, but the data has been greatly modified so DO NOT CONSIDER IT AS REAL DATA en-us BioCASe, Barcelona, CeDocBiv, herbarium, plantae, specimen The BioCASE training database You can distribute this database freely but only for testing purposes and training. 2005-03-17 data supplier data supplier http://ww3.bgbm.org/biocase/datasources/training/metadata.xml Botanic Garden & Botanical Museum Berlin-Dahlem BGBM http://www.biocase.org/images/bdi_logo.gif The Botanic Garden Berlin-Dahlem comprises an area of 126 acres and hence is one of the world´s largest and most important gardens. About 22,000 different species of plants are cultivated here. In the 39 acres of the plant-geography section - one of the biggest of its kind in the world - you can travel all the way around the Northern Hemisphere, and in the 42 acre Arboretum and taxonomy section you can get an insight into the relationship among woody and herbaceous plants. The greenhouse complex consists of 16 houses open to the public and offers the possibility to travel through tropical and subtropical vegetation. These living collections, along with the preserved collections, form the basis for the continued expansion of scientific study within the plant kingdom, with the goal to deepen the knowledge necessary for the utilization and protection of plant diversity on earth.
Königin-Luise-Straße 6-8, D-14191 Berlin, Germany
http://www.bgbm.org/ technical Frank Sinatra senior developer +49 30-5555-55 frank@@worldstars.org administrative Frankenstein head of biodiversity department +49 30-5555-56 fstein@@worldstars.org 52.458356 13.305017
---- ---++ Capabilities operation *HTTP Parameters* * http://wrapper_end_point?op=capabilities *XML message*
*Response*
2 10 20 500 500
---- ---++ Inventory operation *HTTP Parameters* * Without aliases * http://wrapper_end_point?op=inventory&start=10&limit=10&concept=http://digir.net/schema/conceptual/darwin/2003/1.0#/Country&concept=http://digir.net/schema/conceptual/darwin/2003/1.0#/Genus * With global concept aliases * http://wrapper_end_point?op=inventory&start=10&limit=10&concept=Country@@dwc&concept=Genus@@dwc * With template * http://wrapper_end_point?op=inventory&start=10&limit=10&template=http://you.net/inventory3.xml&name=Inula* *Inventory template* An inventory template can be referred to in a request and allows simple parameter bindings to a more complex operation. Example template: Search and list unique scientific names of specimen identifications ordered alphabetically by their name. The filter parameter "name" is used to build the filter *XML message* In the XML messages aliases could also be used, but we only shows here the example with complete concept IDs
*Response*
AUSTRALIA Calicium AUSTRALIA Fellhanera ---- ---++ Search operation Search operations make use of [[#om][output models]]. *HTTP Parameters* * Without aliases * http://wrapper_end_point?op=search&start=0&limit=10&model=http://res.tdwg.org/tapir/models/abcd206.xml&filter=http://www.tdwg.org/schemas/abcd/2.06/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/FullScientificNameString like "Luzu*"&orderby=http://www.tdwg.org/schemas/abcd/2.06/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/FullScientificNameString * With global concept aliases * http://wrapper_end_point?op=search&start=0&limit=10&model=http://res.tdwg.org/tapir/models/abcd206.xml&filter=FullScientificName@@abcd206 like "Luzu*"&orderby=FullScientificName@@abcd206 * With template * http://wrapper_end_point?op=search&start=0&limit=10&template=http://you.net/search3.xml&name=Luzu* *Output Model* *Search template* A search template can be referred to in a request and allows simple parameter bindings to a more complex operation. Example template: Search specimens by their scientific name. Result is returned ordered by name and catalogue number. The filter parameter "name" is used to build the filter. *XML message*
*Response*
Luzula luzuloides Luzula alpestris @ 1.35 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RicardoPereira" date="1172248008" format="1.1" version="1.35"}% @ 1.34 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="RicardoPereira" date="1168433429" format="1.1" version="1.34"}% d370 1 a370 1 Search operations make use of [[#o][output models]]. @ 1.33 log @Revision 33 @ text @d1 534 a534 532 This section provides some examples of common TAPIR messages. The latest version of the examples can always be found in the subversion repository. This page is only updated once in a while, so it might be that the examples below are not valid against the latest schema. But they will only vary in minor details. http://ww2.biocase.org/svn/tapir/trunk/protocol/examples/ Messages in TAPIR should be sent through HTTP. Every TAPIR message can be sent as an XML encoded document as defined by the TAPIR schema or alternatively through a list of URL [[GetInvokedOperations][parameters]] specified by TAPIR as well. This allows to invoke all TAPIR operations through HTTP GET (using the [[GetInvokedOperations][parameters]]) or trough HTTP POST (using [[GetInvokedOperations][parameters]] or sending an XML document). Here we provide a parameterized version of every example and the corresponding XML version. They MUST generate the same result from a TAPIR compliant service. The parameterized version is represented with an*unencoded* URL string. ---- ---+++ TAPIR Operations * [[#p][Ping]] * [[#preq][request]] * [[#presp][response]] * [[#c][Capabilities]] * [[#creq][request]] * [[#cresp][response]] * [[#m][Metadata]] * [[#mreq][request]] * [[#mresp][response]] * [[#i][Inventory]] * [[#it][inventory template]] * [[#ireq][request]] * [[#iresp][response]] * [[#s][Search]] * [[#om][output model]] * [[#st][search template]] * [[#sreq][request]] * [[#sresp][response]] ---- ---++ Ping operation *HTTP Parameters* * http://wrapper_end_point?op=ping *XML message*
http://accesspoint_url
*Response*
---- ---++ Metadata operation *HTTP Parameters* * http://wrapper_end_point?op=metadata *XML message*
*Response* BioCASe training http://purl.org/dc/dcmitype/Service http://localhost:8080/tapir/pywrapper/training This testing database is used in BioCASE workshops and other events. This database was gratefully provide by the Herbarium at the Universidad of Barcelona CeDocBiv, but the data has been greatly modified so DO NOT CONSIDER IT AS REAL DATA en-us BioCASe, Barcelona, CeDocBiv, herbarium, plantae, specimen The BioCASE training database You can distribute this database freely but only for testing purposes and training. 2005-03-17 data supplier data supplier http://ww3.bgbm.org/biocase/datasources/training/metadata.xml Botanic Garden & Botanical Museum Berlin-Dahlem BGBM http://www.biocase.org/images/bdi_logo.gif The Botanic Garden Berlin-Dahlem comprises an area of 126 acres and hence is one of the world´s largest and most important gardens. About 22,000 different species of plants are cultivated here. In the 39 acres of the plant-geography section - one of the biggest of its kind in the world - you can travel all the way around the Northern Hemisphere, and in the 42 acre Arboretum and taxonomy section you can get an insight into the relationship among woody and herbaceous plants. The greenhouse complex consists of 16 houses open to the public and offers the possibility to travel through tropical and subtropical vegetation. These living collections, along with the preserved collections, form the basis for the continued expansion of scientific study within the plant kingdom, with the goal to deepen the knowledge necessary for the utilization and protection of plant diversity on earth.
Königin-Luise-Straße 6-8, D-14191 Berlin, Germany
http://www.bgbm.org/ technical Frank Sinatra senior developer +49 30-5555-55 frank@@worldstars.org administrative Frankenstein head of biodiversity department +49 30-5555-56 fstein@@worldstars.org 52.458356 13.305017
---- ---++ Capabilities operation *HTTP Parameters* * http://wrapper_end_point?op=capabilities *XML message*
*Response*
2 10 20 500 500
---- ---++ Inventory operation *HTTP Parameters* * Without aliases * http://wrapper_end_point?op=inventory&start=10&limit=10&concept=http://digir.net/schema/conceptual/darwin/2003/1.0#/Country&concept=http://digir.net/schema/conceptual/darwin/2003/1.0#/Genus * With global concept aliases * http://wrapper_end_point?op=inventory&start=10&limit=10&concept=Country@@dwc&concept=Genus@@dwc * With template * http://wrapper_end_point?op=inventory&start=10&limit=10&template=http://you.net/inventory3.xml&name=Inula* *Inventory template* An inventory template can be referred to in a request and allows simple parameter bindings to a more complex operation. Example template: Search and list unique scientific names of specimen identifications ordered alphabetically by their name. The filter parameter "name" is used to build the filter *XML message* In the XML messages aliases could also be used, but we only shows here the example with complete concept IDs
*Response*
AUSTRALIA Calicium AUSTRALIA Fellhanera ---- ---++ Search operation Search operations make use of [[#o][output models]]. *HTTP Parameters* * Without aliases * http://wrapper_end_point?op=search&start=0&limit=10&model=http://res.tdwg.org/tapir/models/abcd206.xml&filter=http://www.tdwg.org/schemas/abcd/2.06/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/FullScientificNameString like "Luzu*"&orderby=http://www.tdwg.org/schemas/abcd/2.06/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/FullScientificNameString * With global concept aliases * http://wrapper_end_point?op=search&start=0&limit=10&model=http://res.tdwg.org/tapir/models/abcd206.xml&filter=FullScientificName@@abcd206 like "Luzu*"&orderby=FullScientificName@@abcd206 * With template * http://wrapper_end_point?op=search&start=0&limit=10&template=http://you.net/search3.xml&name=Luzu* *Output Model* *Search template* A search template can be referred to in a request and allows simple parameter bindings to a more complex operation. Example template: Search specimens by their scientific name. Result is returned ordered by name and catalogue number. The filter parameter "name" is used to build the filter. *XML message*
*Response*
Luzula luzuloides Luzula alpestris @ 1.32 log @Revision 32 @ text @d373 1 a373 1 * http://wrapper_end_point?op=search&start=0&limit=10&model=http://res.tdwg.org/tapir/models/abcd206.xml&filter=http://www.tdwg.org/schemas/abcd/2.06/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/FullScientificNameString like "Abies*"&orderby=http://www.tdwg.org/schemas/abcd/2.06/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/FullScientificNameString d375 1 a375 1 * http://wrapper_end_point?op=search&start=0&limit=10&model=http://res.tdwg.org/tapir/models/abcd206.xml&filter=FullScientificName@@abcd206 like "Abies*"&orderby=FullScientificName@@abcd206 @ 1.31 log @Revision 31 @ text @d372 4 @ 1.30 log @Revision 30 @ text @d198 1 a198 1 d201 1 a201 2 d237 2 a238 2 @ 1.29 log @Revision 29 @ text @d97 51 a147 32
http://www.flies.au/pywrapper/flies Australian fruit flies collection of georeferenced records observations fuit flies observation australia diptera Tephritidae Australian Fruit Flies free 2006-01-01T00:00:00 TAPIR working group Frank Sinatra f.sinatra@@tapir.com system administrator Hosting Provider
@ 1.28 log @Revision 28 @ text @d7 1 a7 1 Every TAPIR message can be send as an XML encoded document as defined by the TAPIR schema or alternatively through a list of [[GetInvokedOperations][parameters]] specified by TAPIR as well. d9 1 a9 1 That allows to invoke all TAPIR operations through HTTP GET (using the [[GetInvokedOperations][parameters]]) or trough HTTP POST (using [[GetInvokedOperations][parameters]] or sending an XML document). @ 1.27 log @Revision 27 @ text @d45 1 a45 1 d62 1 a62 1 d83 1 a83 1 d98 1 a98 1 d142 1 a142 1 d157 1 a157 1 d279 1 a279 1 d302 1 a302 1 d322 1 a322 1 d361 1 a361 1 d457 2 a458 2 @ 1.22 log @Revision 22 @ text @d356 67 @ 1.21 log @Revision 21 @ text @d15 2 a16 2 * [[#][preq request]] * [[#][presp response]] d18 2 a19 2 * [[#][creq request]] * [[#][cresp response]] d21 2 a22 2 * [[#][mreq request]] * [[#][mresp response]] d24 3 a26 3 * [[#][it inventory template]] * [[#][ireq request]] * [[#][iresp response]] d28 5 a32 4 * [[#][om output model]] * [[#][st search template]] * [[#][sreq request]] * [[#][sresp response]] @ 1.20 log @Revision 20 @ text @d15 2 d18 2 d21 2 d24 3 d28 4 d40 1 d57 1 a58 1 d78 1 d93 1 a94 1 d130 1 d145 1 a146 1 d251 2 d265 2 d289 1 d310 1 a311 1 d339 1 d343 1 d347 33 a379 1 * http://wrapper_end_point?op=search&start=10&limit=10&model=&template=&filter d381 1 d408 1 @ 1.19 log @Revision 19 @ text @d13 1 a13 1 TAPIR Operations: @ 1.18 log @Revision 18 @ text @a11 1 d13 8 d57 1 d108 1 d236 1 d319 1 @ 1.17 log @Revision 17 @ text @d317 22 a338 1 d344 26 a369 1 @ 1.16 log @Revision 16 @ text @d9 1 a9 1 That allows to invoke all TAPIR operations through HTTP GET (using the parameters) or trough HTTP POST (using parameters or sending an XML document). @ 1.15 log @Revision 15 @ text @d2 3 @ 1.14 log @Revision 14 @ text @d4 1 a4 1 Every TAPIR message can be send as an XML encoded document as defined by the TAPIR schema or alternatively through a list of parameters specified by TAPIR as well. d232 2 a233 2 * With templates * TBD @ 1.13 log @Revision 13 @ text @d106 1 a106 1 d113 1 a113 1 d121 1 a121 1 d134 1 a134 1 d136 3 a138 1 d140 7 a147 11 d150 31 a180 34
d183 2 a184 2 d186 8 a193 3 d195 3 a197 2 d201 19 a219 1 a221 1 d232 23 d260 1 a260 1 d267 1 a267 1 d280 1 a280 1 @ 1.12 log @Revision 12 @ text @d20 1 a20 1 d29 1 a29 1 d37 1 a37 1 d56 1 a56 1 d71 1 a71 1 @ 1.11 log @Revision 11 @ text @d3 4 a6 1 Every message in TAPIR can be sent through HTTP using parameters or using a single parameter with an XML document on it. That makes possible to invoke all TAPIR operations through HTTP GET (using the parameters way) or trough HTTP POST (using parameters or sending an XML document). @ 1.10 log @Revision 10 @ text @d3 1 a3 1 Every message in TAPIR can be sent trough HTTP using parameters or using a single parameter with an XML document on it. That makes possible to invoke all TAPIR operation trough HTTP GET (using the parameters way) or trough HTTP POST (using parameters or sending an XML document). d5 1 a5 1 In this document we provide a parameterize version of every example and the XML version. They MUST generate the same results from a TAPIR compliant service. The parameterize version is represented in a URL string NOT ENCODED!. @ 1.9 log @Revision 9 @ text @d102 10 a111 1 d117 84 d214 1 d267 1 a267 1 * http://wrapper_end_point?op=ping @ 1.8 log @Revision 8 @ text @d7 1 d93 92 @ 1.7 log @Revision 7 @ text @a32 3 d42 50 @ 1.6 log @Revision 6 @ text @d11 1 a11 1 * http://wrapper_end_point?op=ping d28 17 @ 1.5 log @Revision 5 @ text @d10 2 a11 1 http://wrapper_end_point?op=ping a15 4 @ 1.4 log @Revision 4 @ text @d7 1 a7 1 ---+++ Ping operation d10 1 d13 18 @ 1.3 log @Revision 3 @ text @d9 1 a9 1 *Parameters* d11 1 a11 1 *XML* @ 1.2 log @Revision 2 @ text @d5 1 a5 1 In this document we provide a parameterize version of every example and the XML version. They MUST generate the same results from a TAPIR compliant service. The parameterize version is represented in a URL form NOT encoded. d8 4 @ 1.1 log @Initial revision @ text @d1 7 a7 1 Describe ExampleTapirMessages here. @