<div id="RTEContent">Dear Rich<br><br><b><i>Richard Pyle <deepreef@BISHOPMUSEUM.ORG></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Hi Patricia,<br><br>Many thanks for the feedback (and thanks also to Bob -- who I neglected to<br>thank in my previous post).<br><br>What do you reckon would be the limiting social and financial factors for<br>full mirrors? In social terms, if I'm going to expose my data to the world<br>anyway (e.g., via DiGIR), then I don't see why I would be socially reluctant<br>to allow others to mirror the data (provided robust syncronization protocols<br>are in place -- see my previous response to Bob; and provided data<br>"ownership" credentials are embedded within the core metadata).<br> <br> I agree with you about the logic in this. However accoding to my daily experience with potential dataproviders there is a lot of teaching and conviencing
needed to make this logic accepted that this does not result in the loss of control over own data. I agree that to be conviencing a robust syncronization is needed. <br><br>As for financial, I prefaced my original post with the observation of ever<br>decreasing $/GB for storage space. I suspect that, before TDWG nails down<br>the GUID protocols, entry-level web servers (of the sort that even the most<br>modest DiGIR provider would need to establish) will come with nearly a TB of<br>disk storage space by default. Perhaps the cost of bandwidth will be a<br>limiting factor? Or maybe DB software capable of managing such large<br>datasets?<br> <br> I agree that for machines and storage it is not that expensive. I was more referring to the human ressources needed to manage the mirror. Smaller institutions do not have necessary the funds or cannot justify to their hierachy that staff is devoting time to maintain a
full miror containing mainly "references" to information coming from other institutions, but it is easier to justify the time spent to contribute to the whole with the part concerning directly the institution ... <br><br>As for IPR -- well, ultimately that applies mostly to specimens. And again,<br>assuming that "ownership" metadata remains intact, I see no basis for<br>increased apprehension about allowing mirrored copies of data records (as<br>GBIF already does, for example) over and above exposing them in the first<br>place.<br> <br> Yes I agree with you here too, but as said before this need teaching and convincing ... <br><br>Personally, I don't think the social, legal, or financial barriers are<br>significantly greater for a mass-mirror paradigm than they are for<br>distributed complementary data sets. I suspect the major barriers will be<br>more technical (i.e., those aforementioned "robust syncronization<br>protocols").<br><br> Yes I agree with you that robust
syncronization will be needed but as my IT colleague always remind me, I guess we must not forget that setting up an IT infrastructure is most of the time 10 % technical issues to be solved and 90% of the time solving "human problems and barriers" to make it work and accepted ... <br> <br> Pat<br> <br> <br>Aloha,<br>Rich<br><br>-----Original Message-----<br>From: Taxonomic Databases Working Group GUID Project<br>[mailto:TDWG-GUID@LISTSERV.NHM.KU.EDU]On Behalf Of Patricia Mergen<br>Sent: Tuesday, January 03, 2006 10:31 PM<br>To: TDWG-GUID@LISTSERV.NHM.KU.EDU<br>Subject: Re: RDF query and inference in a distributed environment<br><br><br>Dear Richard<br><br>I agree with you that several mirror copies will and are needed, preferably<br>well spread geographically as back-ups. This is exactely the approach of<br>GBIF, as they are now in the process to mirror their services.<br><br>However as highlighted by Bob Morris their is are social, but also financial<br>barriers to have
all contributing institutions run a "full" mirror. In order<br>to insure the participation of all those who are willing to, I believe that<br>a distributed system where each provider can participate with his part<br>should be kept. Those who have the ressources could of course set up full<br>mirrors if this match their needs and if this is allowed by the providers<br>(there are also IPRs issues which may be raise here by some institutions).<br><br>Patricia<br><br><br>Richard Pyle <deepreef @bishopmuseum.org=""> wrote:<br>> Long term what I think might happen is that users have their own triple<br>> stores, and as they do queries the results get added to their own<br>> triple store and they can make inferences locally that they are<br>> interested in. MIT's Piggy bank project<br>> (http://simile.mit.edu/piggy-bank/) is an example of this sort of<br>> approach.<br><br>With hard drive sizes spiraling skyward, and $/GB ($/TB) spiraling<br>downward.... I'm wondering
whether or not the "distributed" system that<br>serves us best might be "distributeded mirror copies", rather than<br>distributed complementary data. I've been pushing this approach for<br>taxonomic data for a while, but perhaps it would be useful for other shared<br>data as well (geographic localities, people/agents, publications/references,<br>etc.) Even for specimen data -- where "ownership" is unambiguous -- it<br>seems that as long as the ownership is clearly embedded in the core<br>metadata, there are more fundamental advantages in storing and serving data<br>from multiple data resources, rather than serving it from only one single<br>data resource.<br><br>One way to look at it would be "robust caching", with automated update<br>capabilities. The main benefits would be:<br><br>1) Large-scale distributed backup of the world's biodata (ensuring<br>perpetuity across a changing technological landscape);<br>2) Performance and reliability enhancement for local data authority
needs;<br>4) Essentially 100% data availability (like DNS), regardless of which<br>servers are up or down at any given moment;<br>3) Maximization of distributed work/effort for data "maintenance and<br>repair".<br><br>The point is, the technology discussions would focus less on issues of<br>distributed queries, and more on issues of replication/synchronization and<br>data edit authorization protocols.<br><br>Perhaps this would be reaching too far, too soon. But on the other han d, I<br>don't see why implementing a "distributed mirror" system would be any more<br>technically, financially, or socially challenging than implementing a<br>distributed query system for distributed data.<br><br>Aloha,<br>Rich<br><br>Richard L. Pyle, PhD<br>Database Coordinator for Natural Sciences<br>and Associate Zoologist in Ichthyology<br>Department of Natural Sciences, Bishop Museum<br>1525 Bernice St., Honolulu, HI 96817<br>Ph: (808)848-4115, Fax: (808)847-8252<br>email:
deepreef@bishopmuseum.org<br>http://hbs.bishopmuseum.org/staff/pylerichard.html<br><br><br><br><br><br>Yahoo! Photos<br>Ring in the New Year with Photo Calendars. Add photos, events, holidays,<br>whatever.<br></deepreef></blockquote><br></div><p>
<hr size=1>Yahoo! Photos<br>
Ring in the New Year with <a href="http://us.rd.yahoo.com/mail_us/taglines/photos/*http://pg.photos.yahoo.com/ph//page?.file=calendar_splash.html&.dir=">Photo Calendars</a>. Add photos, events, holidays, whatever.