<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>RE: [tdwg-tapir] FAQ page</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Thanks, Markus.</FONT>
</P>
<P><FONT SIZE=2>That helps add more to the ontology of data exchange. But, you also added another term - wrapper. So, we have services, wrappers, protocols, providers and portals. Still confusing to most I'm afraid.</FONT></P>
<P><FONT SIZE=2>My general request is for "someone" to produce a single document that organizes it all into a form understandable by the non-programmers.</FONT></P>
<P><FONT SIZE=2>Also, does BioCASE use UDDI for discovery of the provider metadata and the data elements available from the provider/wrapper?</FONT></P>
<P><FONT SIZE=2>Chuck </FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: "Döring, Markus" [<A HREF="mailto:m.doering@BGBM.org">mailto:m.doering@BGBM.org</A>] </FONT>
<BR><FONT SIZE=2>Sent: Friday, January 13, 2006 4:27 AM</FONT>
<BR><FONT SIZE=2>To: Chuck.Miller@mobot.org; tdwg-tapir@lists.tdwg.org</FONT>
<BR><FONT SIZE=2>Cc: Berendsohn, Walter G.</FONT>
<BR><FONT SIZE=2>Subject: AW: [tdwg-tapir] FAQ page</FONT>
</P>
<P><FONT SIZE=2>Chuck,</FONT>
<BR><FONT SIZE=2>from the BioCASE side I can add the following:</FONT>
</P>
<P><FONT SIZE=2>BioCASE</FONT>
<BR><FONT SIZE=2>-------</FONT>
<BR><FONT SIZE=2>BioCASE is a European project and its also the name of the protocol (sometimes written as BioCASe).</FONT>
<BR><FONT SIZE=2>The BioCASE portal (software) is referred to simply as the BioCASE portal.</FONT>
<BR><FONT SIZE=2>The core of the BioCASE provider software (BPS) is called PyWrapper. This wrapper understands the BioCASE protocol, but also the Species2000/SPICE protocol. So you can use it to serve data in ABCD, SPICE/Species2000, DarwinCore, MCPDH, NaturalCollectionMetadata (NCD) or nearly any other XML standard with some limitations (unfortunately used by SDD).</FONT></P>
<P><FONT SIZE=2>TAPIR</FONT>
<BR><FONT SIZE=2>------</FONT>
<BR><FONT SIZE=2>TAPIR refers only to the protocol. The primary goal of TAPIR is the unification of DiGIR and BioCASE, thus replacing them so that data providers and clients can access our data in the same way. </FONT></P>
<P><FONT SIZE=2>There is a full TAPIR provider software available based on the PyWrapper which is called TAPIR PyWrapper. </FONT>
<BR><FONT SIZE=2>There is no TAPIR portal yet or any other client application for TAPIR.</FONT>
</P>
<P><FONT SIZE=2>RDF</FONT>
<BR><FONT SIZE=2>----</FONT>
<BR><FONT SIZE=2>In many discussions currently RDF is considered a better way to share our data. To fully go the RDF way we would have to migrate the TDWG XML schema standards to some sort of RDF schema or ontology. There is still a performance problem with RDF if used with millions of records (equivalent to maybe hundreds of millions of rdf statements). So I dont see RDF being used right now in full production, but its surely a promising way to go.</FONT></P>
<BR>
<P><FONT SIZE=2>Personally I am a bit concerned we are about to split the community again - this time into TAPIR and RDF; but maybe thats how technological progress is made...</FONT></P>
<BR>
<P><FONT SIZE=2>regards,</FONT>
<BR><FONT SIZE=2>Markus</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<P><FONT SIZE=2>-----Ursprüngliche Nachricht-----</FONT>
<BR><FONT SIZE=2>Von: tdwg-tapir-bounces@lists.tdwg.org [<A HREF="mailto:tdwg-tapir-bounces@lists.tdwg.org">mailto:tdwg-tapir-bounces@lists.tdwg.org</A>] Im Auftrag von Dave Vieglais</FONT>
<BR><FONT SIZE=2>Gesendet: Freitag, 13. Januar 2006 16:03</FONT>
<BR><FONT SIZE=2>An: Javier privat</FONT>
<BR><FONT SIZE=2>Cc: tdwg-tapir@lists.tdwg.org</FONT>
<BR><FONT SIZE=2>Betreff: Re: [tdwg-tapir] FAQ page</FONT>
</P>
<P><FONT SIZE=2>Much of the confusion has come about I guess because DiGIR 2 is actually a code name for a project that is building a data service application that supports pluggable protocols. There is no official name for that application, and there is no release (yet).</FONT></P>
<P><FONT SIZE=2>So to try and help things a little:</FONT>
</P>
<P><FONT SIZE=2>DiGIR 2 is a data server application, not a protocol. The application supports multiple protocols for accessing the data it serves including:</FONT></P>
<P><FONT SIZE=2>* DiGIR 1.5 (i.e. the current version of DiGIR)</FONT>
<BR><FONT SIZE=2>* TAPIR (may not be a full implementation)</FONT>
<BR><FONT SIZE=2>* WFS (OGC Web Feature Service)</FONT>
<BR><FONT SIZE=2>* possibly SPARQL (an RDF query language)</FONT>
</P>
<P><FONT SIZE=2>DiGIR 2 data server is being developed because we do not yet feel that there is a single unifying protocol for our community, and that new protocols may emerge and then different versions of the protocols will be developed. Having a single data service application that supports pluggable protocols will, we hope, significantly reduce the maintenance and configuration overhead of those interested in serving their data, since one the application is installed, we expect it to be a relatively trivial matter to add protocols or updates to existing protocols.</FONT></P>
<P><FONT SIZE=2>We will provide more information about the project as updates become available.</FONT>
</P>
<P><FONT SIZE=2>regards,</FONT>
<BR><FONT SIZE=2> Dave Vieglais</FONT>
</P>
<P><FONT SIZE=2>Javier de la Torre said the following on 1/12/2006 8:23 AM:</FONT>
<BR><FONT SIZE=2>> Dear all,</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> We had today the GBIF ICT Expert Group meeting and a lot of people </FONT>
<BR><FONT SIZE=2>> where making questions about TAPIR.</FONT>
<BR><FONT SIZE=2>> Seems that there is confusion regarding names. People were asking why </FONT>
<BR><FONT SIZE=2>> there is Digir 2 if we are all going to TAPIR and things like that.</FONT>
<BR><FONT SIZE=2>> There were also questions regarding when things are gonna be ready, </FONT>
<BR><FONT SIZE=2>> what can we expect from Digir2 and TAPIR pywrapper and what would be </FONT>
<BR><FONT SIZE=2>> the reasons to migrate, how difficult is going to be to migrate, etc.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I was thinking of extending the FAQ page that Renato started in Madrid </FONT>
<BR><FONT SIZE=2>> to answer all these questions, but I need some help specially from the </FONT>
<BR><FONT SIZE=2>> Digir2 people.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> -What is the status of Digir2?</FONT>
<BR><FONT SIZE=2>> -Is it going to be difficult to update from Digir 1 to 2?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I will in any case start writing there and maybe you can then modify </FONT>
<BR><FONT SIZE=2>> extend thins related to you.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Best regards,</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Javi.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> _______________________________________________</FONT>
<BR><FONT SIZE=2>> tdwg-tapir mailing list</FONT>
<BR><FONT SIZE=2>> tdwg-tapir@lists.tdwg.org</FONT>
<BR><FONT SIZE=2>> <A HREF="http://lists.tdwg.org/mailman/listinfo/tdwg-tapir_lists.tdwg.org" TARGET="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-tapir_lists.tdwg.org</A></FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>tdwg-tapir mailing list</FONT>
<BR><FONT SIZE=2>tdwg-tapir@lists.tdwg.org</FONT>
<BR><FONT SIZE=2><A HREF="http://lists.tdwg.org/mailman/listinfo/tdwg-tapir_lists.tdwg.org" TARGET="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-tapir_lists.tdwg.org</A></FONT>
</P>
</BODY>
</HTML>