Hi Donald,<div><br></div><div>I just don't understand why an additional field canonicalScientificName (much like minimumElevationInMeters or countryCode) would create or shift the problem. It has a clear and easy to understand definition [1]. As a data provider I can assess if its too much of a bother to populate the field in addition to the more lenient scientificName (just like countryCode, etc.) and as a data user I can complain or ignore the data if I see the provider didn't follow the definition.</div>
<div><br></div><div>This discussion resurfaces every time: clearly users would like to have this. So why do we make it difficult for those users and the data providers who can provide it?<br></div><div><br></div><div>Peter</div>
<div><br></div><div>[1] <a href="http://code.google.com/p/darwincore/issues/detail?id=150" target="_blank">http://code.google.com/p/darwincore/issues/detail?id=150</a> I could even add "<span>[...] it will contain one, two or three words"</span> (see email Jessie Kennedy)<br>
</div><div><br></div><div>PS: Yes, some people probably interpret scientificName as "Give us the cleanest representation of the scientific name you have", but that is definitely not the Darwin Core definition. It's more "give us the most verbose representation of the scientific name you have", which is what I use and what I advise all data publishers in my network to use. The difference doesn't matter though, the important thing is that a data user cannot expect this term to be a canonical representation of the name.</div>
<div><br></div><div><div class="gmail_quote">On Wed, Mar 14, 2012 at 13:36, Donald Hobern (GBIF) <span dir="ltr"><<a href="mailto:dhobern@gbif.org" target="_blank">dhobern@gbif.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-GB" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Rod.<u></u><u></u></span></p><p class="MsoNormal">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Given the two alternatives you offer, I fully agree. However (and I may be very wrong on this), I don’t actually believe that what you describe is what is happening in most cases. I believe that the scientificName field should always be the “give us the cleanest representation of the scientific name you have” and we could certainly provide a more useful set of priorities for how that is defined. Regardless of what the DwC guidelines say, I think many data providers simply map their most closely aligned database column into the DwC view and we get whatever that happens to be, with whatever authorship it may contain.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I’d agree that the clean name is much closer to what a web-enabled linked-data world needs and would happily endorse a move to make that the recommended form. I just honestly believe that many providers will always give us something different. Adding a new field will just shift the problem.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">At least that’s my perspective…<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">All the best,<u></u><u></u></span></p>
<div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Donald<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><div><p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">----------------------------------------------------------------------<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Donald Hobern - GBIF Director - <a href="mailto:dhobern@gbif.org" target="_blank"><span style="color:blue">dhobern@gbif.org</span></a> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Global Biodiversity Information Facility <a href="http://www.gbif.org/" target="_blank"><span style="color:blue">http://www.gbif.org/</span></a> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="DA" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">GBIF Secretariat, Universitetsparken 15, DK-2100 Copenhagen Ø, Denmark<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">Tel: <a href="tel:%2B45%203532%201471" value="+4535321471" target="_blank">+45 3532 1471</a> Mob: <a href="tel:%2B45%202875%201471" value="+4528751471" target="_blank">+45 2875 1471</a> Fax: <a href="tel:%2B45%202875%201480" value="+4528751480" target="_blank">+45 2875 1480</a><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas;color:#1f497d">----------------------------------------------------------------------<u></u><u></u></span></p></div><p class="MsoNormal">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p></div><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal">
<b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a> [mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>] <b>On Behalf Of </b>Roderic Page<br>
<b>Sent:</b> Wednesday, March 14, 2012 5:50 PM<br><b>To:</b> TDWG Content Mailing List<br><b>Subject:</b> Re: [tdwg-content] canonicalScientificName<u></u><u></u></span></p></div></div><div><div><p class="MsoNormal">
<u></u> <u></u></p><div><p class="MsoNormal">Dear Donald,<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I couldn't disagree more!<u></u><u></u></p></div><div><p class="MsoNormal">
<u></u> <u></u></p></div><div><p class="MsoNormal">It seems to me that this is one case where needs of consumers and providers align pretty well.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div>
<div>
<p class="MsoNormal">If I'm publishing data I want to avoid hassle, and one hassle is finding the taxonomic authorities for names. Then there is the issue of how to write the authority. There are so many variables: do I include diacritic characters? is the person's name abbreviated? what is the correct date? should I use parentheses? should I use commas? If I can just publish the canonical name life is simpler.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">As a consumer I can't trust people to get the authority right. Publishers get the taxonomic names wrong, and they will certainly make a mess of the authority.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">So, if we mandate clean names we are saying to providers "give me this"<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p>
</div><div><p class="MsoNormal"><taxonomic name><u></u><u></u></p></div><div><p class="MsoNormal">[some scope for crap]<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">
Instead, we've mandated "give me this"<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><div><p class="MsoNormal"><taxonomic name> + <authority><u></u><u></u></p>
</div><div><p class="MsoNormal">[some scope for crap] + [huge scope for crap]<u></u><u></u></p></div></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Why? Why would we do this to ourselves? Why do we think it's OK to have databases full of duplicates such as these (from the ION database)?:<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><div><p class="MsoNormal">Pseudopaludicola Miranda Ribeiro 1926<u></u><u></u></p></div><div><p class="MsoNormal">Pseudopaludicola Mir. Ribeiro 1926<u></u><u></u></p>
</div><div><p class="MsoNormal">Pseudopaludicola Miranda-Ribeiro 1926<u></u><u></u></p></div></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">One consequence of this is that we have projects like <a href="http://globalnames.org" target="_blank">http://globalnames.org</a> project, which is essentially collecting endless variations on authority strings. In other words, trying to clean up a mess essentially of our own making. <u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">By all means have a field for taxonomic authority, but keep that separate from the canonical taxonomic name. In the real world, the canonical name is what people use. If we want people to make data available, make it simple. If we want people to use data make it simple.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Regards<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Rod<u></u><u></u></p></div><div>
<p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">On 14 Mar 2012, at 11:16, Donald Hobern wrote:<u></u><u></u></p>
</div><p class="MsoNormal"><br><br><u></u><u></u></p><p class="MsoNormal">Hi Peter.<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I certainly sympathise with the desire for a readily-consumed naked scientific name field. However, unless the canonicalScientificName element is enforced as a mandatory field (which would in itself impact some data publishers and may prevent them validly sharing their data without extra work to provide clean scientific names), it will be yet another element which data consumers must check. If canonicalScientificName is supplied, consumers will still need to handle cases where it is malformed. If is not supplied, they will need to ignore the record or else do precisely what they do today with the scientificName field. <u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I therefore worry that adding this field could in fact make the task more complex, rather than simpler, for data consumers.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Thanks,<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Donald<u></u><u></u></p></div>
<div><div><p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas"> </span><u></u><u></u></p></div><p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas">----------------------------------------------------------------------</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas">Donald Hobern - GBIF Director - <a href="mailto:dhobern@gbif.org" target="_blank"><span style="color:#1155cc">dhobern@gbif.org</span></a></span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas">Global Biodiversity Information Facility <a href="http://www.gbif.org/" target="_blank"><span style="color:#1155cc">http://www.gbif.org/</span></a></span><u></u><u></u></p>
<p class="MsoNormal"><span lang="DA" style="font-size:10.5pt;font-family:Consolas">GBIF Secretariat, Universitetsparken 15, DK-2100 Copenhagen Ø, Denmark</span><u></u><u></u></p><p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas">Tel: <a href="tel:%2B45%203532%201471" target="_blank"><span style="color:#1155cc">+45 3532 1471</span></a> Mob: <a href="tel:%2B45%202875%201471" target="_blank"><span style="color:#1155cc">+45 2875 1471</span></a> Fax: <a href="tel:%2B45%202875%201480" target="_blank"><span style="color:#1155cc">+45 2875 1480</span></a></span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Consolas">----------------------------------------------------------------------</span><u></u><u></u></p></div><p class="MsoNormal">_______________________________________________<br>
tdwg-content mailing list<br><a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br><a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><u></u><u></u></p>
</div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">---------------------------------------------------------<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: <a href="mailto:r.page@bio.gla.ac.uk" target="_blank">r.page@bio.gla.ac.uk</a><br>Tel: <a href="tel:%2B44%20141%20330%204778" value="+441413304778" target="_blank">+44 141 330 4778</a><br>
Fax: <a href="tel:%2B44%20141%20330%202792" value="+441413302792" target="_blank">+44 141 330 2792</a><u></u><u></u></p></div><div><p class="MsoNormal">Skype: rdmpage<br>AIM: <a href="mailto:rodpage1962@aim.com" target="_blank">rodpage1962@aim.com</a><br>
Facebook: <a href="http://www.facebook.com/profile.php?id=1112517192" target="_blank">http://www.facebook.com/profile.php?id=1112517192</a><br>Twitter: <a href="http://twitter.com/rdmpage" target="_blank">http://twitter.com/rdmpage</a><br>
Blog: <a href="http://iphylo.blogspot.com" target="_blank">http://iphylo.blogspot.com</a><br>Home page: <a href="http://taxonomy.zoology.gla.ac.uk/rod/rod.html" target="_blank">http://taxonomy.zoology.gla.ac.uk/rod/rod.html</a><u></u><u></u></p>
</div></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></div><br>_______________________________________________<br>
tdwg-content mailing list<br>
<a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
<a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Peter Desmet<br>Biodiversity Informatics Manager<br>Canadensys - <a href="http://www.canadensys.net" target="_blank">www.canadensys.net</a><br><br>Université de Montréal Biodiversity Centre<br>
4101 rue Sherbrooke est<br>Montreal, QC, H1X2B2<br>Canada<br><br>Phone: <a href="tel:514-343-6111%20%2382354" value="+15143436111" target="_blank">514-343-6111 #82354</a><br>Fax: <a href="tel:514-343-2288" value="+15143432288" target="_blank">514-343-2288</a><br>
Email: <a href="mailto:peter.desmet@umontreal.ca" target="_blank">peter.desmet@umontreal.ca</a> / <a href="mailto:peter.desmet.cubc@gmail.com" target="_blank">peter.desmet.cubc@gmail.com</a><br>
Skype: anderhalv<br>Public profile: <a href="http://www.linkedin.com/in/peterdesmet" target="_blank">http://www.linkedin.com/in/peterdesmet</a><br>
</div>