<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Hi Rob,
<div><br>
</div>
<div>At the risk of opening the whole taxon/name/concept can of worms, I’d see this a little differently.</div>
<div><br>
</div>
<div>For me a taxon name is a name + the original publication, rather than simply a text string. A taxon is different again, being essentially a statement about a collection of things that belong to the same taxon, and a statement of what to call them.</div>
<div><br>
</div>
<div>Taxon databases (e.g., GBIF) tend use strings for names, when it would be more elegant to use identifiers for names + publications. We could go some way towards cleaning the mess we’ve accumulated if we adopted (and reused) identifiers for these things.
For a start, name strings that don’t map to identifiers in nomenclators would immediately be under suspicion as being potentially erroneous. it also links names to evidence, which is something we’re spectacularly bad at doing at the moment. </div>
<div><br>
</div>
<div>For example, "Pristimantis vilcabambae” is a text string which isn’t terribly useful. But if we combine that with details on where and when it was published we get something a bit more useful:</div>
<div><br>
</div>
<div> "<span style="background-color: rgb(250, 250, 250);"><font color="#2a2b2e" face="Montserrat, sans-serif"><span style="line-height: 20px;">Pristimantis vilcabambae Lehr 2007 published in DOI
<a href="http://dx.doi.org/">http://dx.doi.org/</a></span></font></span><font color="#2a2b2e" face="Montserrat, sans-serif"><span style="line-height: 20px;">10.3099/0027-4100(2007)159[145:NEFLPP]2.0.CO;2 “ This is the information I’m accumulating in BioNames,
by combining metadata from ION LSIDs with data from CrossRef and BioStor , see </span></font><a href="http://bionames.org/names/cluster/1949681">http://bionames.org/names/cluster/1949681</a></div>
<div><br>
</div>
<div>Should this "name string + publication” get a DOI? Sure. Then I’d want GBIF (and other taxon databases) to link to this name on their taxon pages. In other words, <a href="http://www.gbif.org/species/2425396">http://www.gbif.org/species/2425396</a> should
have an identifier for the taxon name, instead of simply using a text string. </div>
<div><br>
</div>
<div>I’m beginning to sound like Rich Pyle, and he and I would a lost certainly model these things differently, but name strings <> taxon names <> taxa</div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Rod</div>
<div><br>
</div>
<div><br>
<div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
---------------------------------------------------------<br>
Roderic Page<br>
Professor of Taxonomy<br>
Institute of Biodiversity, Animal Health and Comparative Medicine<br>
College of Medical, Veterinary and Life Sciences<br>
Graham Kerr Building<br>
University of Glasgow<br>
Glasgow G12 8QQ, UK<br>
<br>
Email: <span class="Apple-tab-span" style="white-space: pre;"> </span><a href="mailto:Roderic.Page@glasgow.ac.uk">Roderic.Page@glasgow.ac.uk</a><br>
Tel: <span class="Apple-tab-span" style="white-space: pre;"> </span>+44 141 330 4778<br>
Skype: <span class="Apple-tab-span" style="white-space: pre;"> </span>rdmpage<br>
Facebook: <span class="Apple-tab-span" style="white-space: pre;"> </span>http://www.facebook.com/rdmpage<br>
LinkedIn: <span class="Apple-tab-span" style="white-space: pre;"> </span>http://uk.linkedin.com/in/rdmpage<br>
Twitter: <span class="Apple-tab-span" style="white-space: pre;"> </span>http://twitter.com/rdmpage<br>
Blog: <span class="Apple-tab-span" style="white-space: pre;"> </span>http://iphylo.blogspot.com<br>
ORCID: <span class="Apple-tab-span" style="white-space: pre;"> </span>http://orcid.org/0000-0002-7101-9767</div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Citations: <span class="Apple-tab-span" style="white-space: pre;"> </span><a href="http://scholar.google.co.uk/citations?hl=en&user=4Z5WABAAAAAJ">http://scholar.google.co.uk/citations?hl=en&user=4Z5WABAAAAAJ</a><br>
<br>
</div>
</div>
</div>
<br>
<div>
<div>On 18 Aug 2014, at 14:29, Robert Guralnick <<a href="mailto:Robert.Guralnick@colorado.edu">Robert.Guralnick@colorado.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr"><br>
<div> Markus --- I think the answer to the question: "<span style="font-family:arial,sans-serif;font-size:12.800000190734863px">Would a taxon DOI be a valuable feature for you?" really depends on some of the details. With a taxon name, you are putting a DOI
on a string and one that has been dissociated from its source(s). I would think more valuable would be a DOI linked to the checklist that contained the name, and maybe a passthrough (a la suffix passthroughs in the EZID system) to the individual name. That
way I can resolve that taxon name to the source from whence it came. </span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px">Best, Rob</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br>
</span></div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Aug 18, 2014 at 3:44 AM, Markus Döring <span dir="ltr">
<<a href="mailto:mdoering@gbif.org" target="_blank">mdoering@gbif.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello Geoff,<br>
<br>
GBIF uses simples integers as taxon identifiers, for example 2396049 for Ecsenius bicolor.<br>
These ids are stable, but obviously not globally unique. If you need a URI right now I would recommend for now to use our restful portal URL:<br>
<a href="http://www.gbif.org/species/2396049" target="_blank">http://www.gbif.org/species/2396049</a><br>
<br>
For the future I could imagine us assigning DOIs to taxa reusing the current integer ids, but that has to be carefully evaluated first.<br>
Would a taxon DOI be a valuable feature for you?<br>
<br>
Cheers,<br>
Markus<br>
<br>
<br>
--<br>
Markus Döring<br>
Software Developer<br>
Global Biodiversity Information Facility (GBIF)<br>
<a href="mailto:mdoering@gbif.org">mdoering@gbif.org</a><br>
<a href="http://www.gbif.org/" target="_blank">http://www.gbif.org</a><br>
<br>
<br>
<br>
<br>
<br>
On 05 Aug 2014, at 05:17, Geoff Shuetrim <<a href="mailto:geoff@galexy.net">geoff@galexy.net</a>> wrote:<br>
<br>
> Working with a range of web services, I have found myself making extensive use of the LSIDs that are specific to each data source. For example, for ITIS, I use the Ecsenius bicolor LSID: urn:lsid:itis.gov:itis_tsn:636326<br>
><br>
> For WoRMS, the LSID for Ecsenius bicolor is: urn:lsid:marinespecies.org:taxname:277652<br>
><br>
> For Atlas of living Australia the LSID for Ecsenius bicolor is:<br>
> urn:lsid:biodiversity.org.au:afd.taxon:99c29e7c-5b04-4e57-8e6b-82aa442a801a<br>
><br>
> Is there a GBIF LSID that can similarly be used as a unique identifier for a taxon? I have come across the various GBIF unique keys but these are not unique outside of the GBIF environment and within the Gaia Guide systems I am deciding how best to work with
these, ensuring their uniqueness, alongside identifiers from other data sources.<br>
><br>
> Thanks again for your assistance.<br>
><br>
> Geoff Shuetrim<br>
> Gaia Guide Association<br>
> <a href="http://www.gaiaguide.info/" target="_blank">http://www.gaiaguide.info/</a><br>
> _______________________________________________<br>
> API-users mailing list<br>
> <a href="mailto:API-users@lists.gbif.org">API-users@lists.gbif.org</a><br>
> <a href="http://lists.gbif.org/mailman/listinfo/api-users" target="_blank">http://lists.gbif.org/mailman/listinfo/api-users</a><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
API-users mailing list<br>
<a href="mailto:API-users@lists.gbif.org">API-users@lists.gbif.org</a><br>
<a href="http://lists.gbif.org/mailman/listinfo/api-users" target="_blank">http://lists.gbif.org/mailman/listinfo/api-users</a><br>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
API-users mailing list<br>
<a href="mailto:API-users@lists.gbif.org">API-users@lists.gbif.org</a><br>
http://lists.gbif.org/mailman/listinfo/api-users<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>