[tdwg-tag] LSID business model?
rhuber at wdc-mare.org
Tue Apr 28 10:09:33 CEST 2009
Good to read something about this issue in this list! I like the idea,
it reminds a bit on how handle and/or doi manage this.
The doi system allows registrants to act as doi resellers, and this is
working. Prices vary, but e.g. for packages of several thousand dois
are sold for an annual fee (http://www.medra.org/en/terms.htm) or for
free (http://www.std-doi.de). Unless someone does it for free (GBIF?),
selling LSIDs could be part of the business model for TDWG?. And in
analogy to the handle system, a fee for registering some
blabla.tdwg.org subdomain (was it authority?) as you mentioned would
surely help to make the whole LSID SYSTEM more persistent.
Well, and I hope LSID registrant(s) would manage the metadata issue
better than the DOI system does. Most people ignore that while doi
registrants do have to register dois+metadata there is no common way
to retrieve this metadata. Crossref, which is mentioned frequently
here, does not hold the metadata on any doi but only on those dois
they registered. Try to get some metadata for example for some dois of
the other registrants such as doi:10.1594/PANGAEA.339110.
On Tue, Apr 28, 2009 at 12:25 AM, Dave Vieglais <vieglais at ku.edu> wrote:
> I'm not sure if anyone has suggested this strategy (I'll be surprised
> if not):
> TDWG seems determined to use LSIDs for GUIDs, yet the technical issues
> for implementation are discouraging enough for some to defer
> deployment. Perhaps TDWG could offer as a bonus for membership (or
> perhaps a small additional charge) the provision of some elements of
> the LSID infrastructure stack, overloading the tdwg.org domain?
> Then, instead of having each institution create DNS entries such as
> "mydepartment.institution.org" and deal with the SRV details, use TDWG
> as a kind of registrar and do something like
> "mycollectionid.tdwg.org". TDWG would then be responsible for the
> appropriate DNS SRV registration, and could even operate a resolver
> and/or redirection service for that domain.
> The income would not be very much (say $10/year per org * 100
> participants = $1k), but it should be a lot less expensive for the
> entire community than the total cost for each organization operating
> their own infrastructure (perhaps $10/year DNS + $1000/year operations
> * 100 participants = $101k).
> So as not to overload the TDWG infrastructure, it would be sensible to
> encourage technically astute groups (e.g. GBIF, EoL, NCEAS) to
> contribute computing cycles and fallback DNS services to ensure
> reliability of the entire system.
> The end result could be a reliable, distributed infrastructure for
> LSID (or whatever GUID scheme is decided upon) resolution that
> conforms to the requirements / specifications derived from the TDWG
> procedures at a small cost for participation. The low cost and
> deferral of technical overhead to a knowledgeable group would
> hopefully encourage participation by a broader audience in this piece
> of fundamental architecture.
> (It may also help reduce the endless cycles of discussion about GUIDs
> and LSIDs)
> Dave V.
> tdwg-tag mailing list
> tdwg-tag at lists.tdwg.org
Dr. Robert Huber,
WDC-MARE / PANGAEA - www.pangaea.de
Stratigraphy.net - www.stratigraphy.net
MARUM - Center for Marine Environmental Sciences
POP 330 440
Phone ++49 421 218-65593, Fax ++49 421 218-65505
e-mail rhuber at wdc-mare.org
More information about the tdwg-tag