FW: [SEEK-Taxon] looking into global unique identifier systems

[Kukla, Robert]

The original doesn't seem to have made it to the list....

I wrote:

> Hi Dave,
> 
> I was just about to answer your (internal) email, but figured
> I might as well write here.
> 
> First of all, great work. Although I couldn't get the actual
> implementations to work (error: Cannot query database & stack
> trace), your descriptions are good enough to understand what
> is going on.
> 
> Another pro for lsid that could be added is the support for
> versions (depending on whether SEEK wants to go down this route).
> 
> Reading through your pros and cons, I am inclined to favour
> the handle system for its simplicity (e.g. hdl:1883/582 with
> plug-in) - the two numbers are easily stored/used and could
> even form part of another implementation (even lsids) if this
> approach doesn't pan out. 
> 
> As far as the CONs are concerned:
> - speed should be solvable
> - although they are not part of an internet standard, they
> make use of other i. standards
> - biggest problem, but as long as there is an interested body
> it should be possible to recreate/replace it
> - this really depends on what data needs to be referenced
> through the handle. If it is just the taxonomic concept
> information there shouldn't be a problem, as it is the
> metadata is identical for all concepts.
> - not so sure why you think it would be restricted to one
> authority (your number 1883) although I would personally
> prefer it this way
> 
> I think from the users (people using GUIDs to resolve a
> taxonomic concept) point of view the methods are equivalent.
> It seems a pity though that only plug-ins for windows browser
> exist in both cases, but this can change easily and for the
> purpose of SEEK the lookups are probably hidden in specific
> client software anyway.
> 
> It is probably more important to investigate what mechanisms
> there are to register and maintain the records associated
> with the GUIDs. Especially in a distributed environment. Who
> owns the records and how can database migrations etc be
> facilitated (e.g. all records pointing to a particular
> location need to be changed). Also how do the systems deal
> with missing destinations? Can they be redirected to
> something useful and generate a notice that something needs fixing?
> 
> These are my thoughts so far.
> 
> Cheers
>   Robert