[tdwg-guid] Permanent LSID Proxy
Matthew Jones
jones at nceas.ucsb.edu
Tue Dec 4 00:07:52 CET 2007
I think this is a great idea, and we'd be willing to host one of the
replicas at NCEAS if so desired. This is the same approach we've been
pursuing for replicating our data between several nodes on the KNB
(e.g., between NCEAS and LTER). I think insitutional diversity and
redundancy are key to long-term persistence.
Matt
Dave Vieglais wrote:
> Why not use something like round robin DNS as a load balancing
> mechanism? Then we can just use the same DNS entry for many identically
> implemented resolvers around the world. If one organization goes kaput,
> the others take on the load automatically, providing the domain remains
> registered.
>
> Dave V.
>
> On Dec 3, 2007 1:47 AM, Donat Agosti <agosti at amnh.org
> <mailto:agosti at amnh.org>> wrote:
>
> How much does it cost to run an LSID resolver, including anything
> from human resources to hardware? If this is high, and TDWG can't
> generate on an annually base this amount, then this needs be
> considered, not just the idealistic aspects.
>
>
>
> Donat
>
>
>
>
>
> ------------------------------------------------------------------------
>
> *From:* tdwg-guid-bounces at lists.tdwg.org
> <mailto:tdwg-guid-bounces at lists.tdwg.org>
> [mailto:tdwg-guid-bounces at lists.tdwg.org
> <mailto:tdwg-guid-bounces at lists.tdwg.org>] *On Behalf Of *Donald Hobern
> *Sent:* Sunday, December 02, 2007 10:26 PM
> *To:* Kevin Richards
> *Cc:* Chuck Miller; tdwg-guid at lists.tdwg.org
> <mailto:tdwg-guid at lists.tdwg.org>
>
> *Subject:* Re: [tdwg-guid] Permanent LSID Proxy
>
>
>
> For what it's worth, I agree with Kevin on this. The TDWG domain
> has been hosted by different organisations at different times and it
> seems a natural place for such a resolver.
>
> Donald
>
> Kevin Richards wrote:
>
> I think this is the idea of "communities". I.e. nothing is
> guaranteed to be forever. It relies on us as a community to keep it
> going indefinitely. So yes on the safe side, we could say "in the
> forseeable future", but on the idealistic side we would say
> "indefinitely".
>
>
>
> So I would reccommend staying with tdwg.org <http://tdwg.org>, as
> this ties the "domain" to a global community / an ideal / an
> aspiration, rather than to a commercial / funding based organisation
> (which could, even more readily, be terminated).
>
>
>
> Any "infrastrutcture" will need to be housed somewhere and, I guess,
> this will be up to the members of our community to chip in and
> provide the services required at the time (as GBIF have done recently).
>
>
>
> This probably all sounds a bit "idealistic", but I think ideals last
> longer than organisations, and longer than any specific technology
> for that matter (LSIDs, DNS, Internet, etc).
>
>
>
> Kevin
>
> > >> "Chuck Miller" <Chuck.Miller at mobot.org>
> <mailto:Chuck.Miller at mobot.org> 1/12/2007 6:18 a.m. >>>
>
> How to turn LSIDs into a clickable link guaranteed to work forever?
>
> Rich's vision:
> http://<some <http://%3Csome> proxy
> server>.org/?urn:lsid:zoobank.org:act:1234
>
> This sounds to me like a question more about networking infrastructure,
> than TDWG's charter about data exchange protocols and content standards.
> I have always presumed that TDWG's standards would work using whatever
> networking infrastructure was available to them - e.g. DNS, HTTP, local
> provider servers, etc.
>
> But, then lsid.tdwg.org <http://lsid.tdwg.org> was created--a
> server. Servers are operational
> infrastructure. I don't think TDWG has (yet) a "forever" funding stream
> to enable operational infrastructure - ongoing operation of server room,
> system administrator, network connections. But, something like
> lsid.tdwg.org <http://lsid.tdwg.org> would serve a valuable purpose
> as Rich notes of enabling
> LSIDs as a clickable link in publications or other online sources.
>
> Is there an existing international body that could operate a forever
> functioning LSID proxy (say like, proxy.lsid.org--which unfortunately is
> already lost to Lindsay-Strathmore Irrigation District)?
>
> Maybe we will be forced to accept that there is no "forever" on the
> Internet and accept instead the "forseeable future". I would think for
> the forseeable future that GBIF would be a good place to put a new LSID
> infrastructure like this since they are in the "operations center"
> business already and TDWG is by charter not. So, maybe the proxy should
> be lsid.gbif.org <http://lsid.gbif.org>?
>
> Chuck
>
>
> -----Original Message-----
> From: tdwg-guid-bounces at lists.tdwg.org
> <mailto:tdwg-guid-bounces at lists.tdwg.org>
> [mailto:tdwg-guid-bounces at lists.tdwg.org]
> <mailto:tdwg-guid-bounces at lists.tdwg.org%5D> On Behalf Of Richard Pyle
> Sent: Friday, November 30, 2007 6:39 AM
> To: 'Roger Hyam'; 'Roderic Page'
> Cc: tdwg-guid at lists.tdwg.org <mailto:tdwg-guid at lists.tdwg.org>
> Subject: [tdwg-guid] Embedding LSID links within Publications
>
>
> Thank you, Roger, for launching the next conversation I wanted to start
> on
> this list (not to interrupt the previous conversation....but this one is
> actually more pressing for me right now):
>
> > Would it be better to take the approach we have with LSIDs
> > where we always cite a proxied version?
> >
> > What do other people do?
>
> As many of you already know, I'm planning to publish the description of
> five
> new species of Chromis in Zootaxa on Jan 1 to:
>
> - launch ZooBank
> - Commemorate the 250th Anniversary of the start of Zoological
> Nomenclature
> - Create an "exemplar" cybertaxonomy publication
>
> I was talking this up at Bratislava, and things are still on track.
> Anyone
> who wants to know more about the project, let me know and I'll send a
> document describing it in more detail.
>
> For now, I'll just provide a basic synopsis: This publication will
> include
> the first 5 zoological names proactively registered in ZooBank. As such,
> there will be five ZooBank LSIDs, which I will want to include within
> the
> publication itself (published in both paper version to comply with ICZN
> Code
> rules; and as an online PDF version, which 99.9% of people will actually
> read). The plan is to have the PDF version marked up as much as
> possible,
> with taXMLit & TaxonX markup files, SDD files for the character data,
> ZooBank LSIDs, Images deposited in MorphBank, links to GenBank records
> for
> Barcode sequences, links to Museum specimen databases, links to BHL for
> literature cited, etc., etc.
>
> So....this will be a document intended to show what could be possible
> with
> all this TDWG stuff we've all be working on for all these years -- i.e.,
> how
> cybertaxonomy could/should be done in the age of the internet.
>
> Now, the PDF file itself will be rather simple -- a standard PDF file as
> per
> normal Zootaxa practice -- except in this document, there will be MANY
> embedded links that allow point-and-click access to all sorts of online
> resources -- each of which will in some way showcase TDWG and TDWG-like
> standards.
>
> A bunch of these links will be LSIDs (e.g., ZooBank LSIDs, plus maybe
> others). However, some of them may be other links (DOIs, URLs, etc.).
> All
> HTTP and other self-resolving links will be pretty straightforward, but
> I'm
> not sure yet how to embed links associated with the LSIDs.
>
> Obviously, LSIDs are not, by themselves, completely self-resolving via
> most
> web browsers, so simply embedding the LSID as a link will not do the
> average
> user much good. Thus, I'm now thinking of how I can make the LSIDs
> "clickable" from the PDF, to allow the cicker/user to be directed to
> something meangiful. And that has caused me to think a lot about HTTP
> proxies for LSIDs.
>
> Thus, assuming I have a ZooBank LSID that is
> urn:lsid:zoobank.org:act:1234,
> how do I represent that as a "clickable" link? One way to do this would
> be
> to embed the LSID within the TDWG HTTP proxy:
>
> http://lsid.tdwg.org/?urn:lsid:zoobank.org:act:1234
>
> However, what I'm shooting for is to have a document that can, as best
> as
> possible, withstand the test of time, such that 250 years from now, some
> or
> all of those embedded links will still work (I know, I know -- they
> won't --
> but humor me....) I'm a little neverous about simply assuming that the
> TDWG
> LSID resolver will still be around in 250 years. Besides, 99.9% of
> users
> will look at the returned RDF and scratch their heads.
>
> My gut feeling is that LSIDs have a better chance of surviving the
> long-term
> than URLs do. And following this premise, the LSID
> "urn:lsid:zoobank.org:act:1234" will only survive as long as the
> authority
> "zoobank.org <http://zoobank.org>" survives (in theory), so it seems
> to me a slightly more
> appropriate solution would be to build a custom LSID resolver at
> zoobank.org <http://zoobank.org>, and thereby format the clickable
> link as:
>
> http://zoobank.org/?lsid=urn:lsid:zoobank.org:act:1234
>
> Does this make sense to anyone? Am I missing something fundamental
> here?
> Is there a better way to embed clickable links to LSIDs in a PDF
> document?
>
> I have a bunch of other questions to follow up with, but let's tackle
> this
> one first.
>
> Many thanks!!
>
> Aloha,
> Rich
>
> Richard L. Pyle, PhD
> Database Coordinator for Natural Sciences
> and Associate Zoologist in Ichthyology
> Department of Natural Sciences, Bishop Museum
> 1525 Bernice St., Honolulu, HI 96817
> Ph: (808)848-4115, Fax: (808)847-8252
> email: deepreef at bishopmuseum.org <mailto:deepreef at bishopmuseum.org>
> http://hbs.bishopmuseum.org/staff/pylerichard.html
>
>
>
> _______________________________________________
> tdwg-guid mailing list
> tdwg-guid at lists.tdwg.org <mailto:tdwg-guid at lists.tdwg.org>
> http://lists.tdwg.org/mailman/listinfo/tdwg-guid
> _______________________________________________
> tdwg-guid mailing list
> tdwg-guid at lists.tdwg.org <mailto:tdwg-guid at lists.tdwg.org>
> http://lists.tdwg.org/mailman/listinfo/tdwg-guid
>
>
>
>
>
> ------------------------------------------------------------------------
>
>
>
>
> _______________________________________________
>
> tdwg-guid mailing list
>
>
> tdwg-guid at lists.tdwg.org <mailto:tdwg-guid at lists.tdwg.org>
>
>
> http://lists.tdwg.org/mailman/listinfo/tdwg-guid
>
>
>
>
> _______________________________________________
> tdwg-guid mailing list
> tdwg-guid at lists.tdwg.org <mailto:tdwg-guid at lists.tdwg.org>
> http://lists.tdwg.org/mailman/listinfo/tdwg-guid
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> tdwg-guid mailing list
> tdwg-guid at lists.tdwg.org
> http://lists.tdwg.org/mailman/listinfo/tdwg-guid
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matthew B. Jones
Director of Informatics Research and Development
National Center for Ecological Analysis and Synthesis (NCEAS)
UC Santa Barbara
jones at nceas.ucsb.edu Ph: 1-907-523-1960
http://www.nceas.ucsb.edu/ecoinfo
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
More information about the tdwg-tag
mailing list