<div>Hi all,</div><div><br></div><div>The reason why I proposed a canonicalScientificName was to make it easier for data users.</div><div><br></div><div>As Tim Robertson points out [1], adding this term will probably make it more complicated, without much benefit. Gregor Hagedorn [2] explains that canonicalScientificName is not a solution for some edge cases (like hybrids) and infraspecific names without a rank marker don't mean much in botany. Rich Pyle [3] points out that more requests will probably be proposed (canonicalScientificNameWithoutRanks, canonicalScientificNameWithoutInfrageneric), demonstrated by Gregor's remark [2].</div>
<div><br></div><div>I now agree with all of these. The only thing I'd like to refine is the definition for genus [4], for which I issued a request: <a href="http://code.google.com/p/darwincore/issues/detail?id=151">http://code.google.com/p/darwincore/issues/detail?id=151</a></div>
<div><br></div><div>See my argumentation in the link above. Basically: As I explained before (and Markus Döring before me), under the current definition the genus gets populated with the genus name of the accepted taxon for a synonym, while the specificEpithet and infraspecificEpithet are not. I think this is counter intuitive and confusing. I would populate it with the "genus name of the scientificName", which I think is how much people interpret it anyway. Advantages:</div>
<div><br></div><div>1. Agreeing with the refined definition for genus won't affect most of our applications and data (only for those who cared about putting the accepted genus for synonyms).<br></div><div>2. No new term canonicalScientificName.<br>
</div><div>3. Not need to update the useful definition for scientificName (verbose all the way if you can).</div><div>4. Publishers and aggregators *have the option* to provide an easier to use name via genus, specificEpithet and infraspecificEpithet. None of these have an authorship, so creating a canonicalScientificName under the proposed definition is as easy as TRIM(genus+" "+specificEpithet+" "+infraspecificEpithet).</div>
<div>5. The above statement only applies to genera, species and infraspecific taxa, but this is the bulk of our data. This method cannot be applied to infrageneric taxa and higher taxa, but as Rich pointed out [3], there are alternative methods for this.</div>
<div>6. Aggregators can ignore genus, specificEpithet and infraspecificEpithet for heterogenous networks and use parsers to deal with scientificNames. Stripping out the scientificNameAuthorship or using a simple regular expression won't sometimes be enough of course, e.g. "<i>Calamagrostis</i> <i>stricta</i> (Timm) Koeler subsp. <i>stricta</i> (Timm) Koeler var. <i>borealis</i> (Laestadius) Hartman" and those pesky hybrids. The good this is that once they have done the work, they can actually express that data in Darwin Core (see point 4).</div>
<div>7. Timon lepidus won't complain [5]. :-)</div><div><br></div><div>Regards,</div><div><br></div><div>Peter</div><div><br></div><div>[1] <a href="http://code.google.com/p/darwincore/issues/detail?id=150#c1">http://code.google.com/p/darwincore/issues/detail?id=150#c1</a></div>
<div>[2] <a href="http://code.google.com/p/darwincore/issues/detail?id=150#c3">http://code.google.com/p/darwincore/issues/detail?id=150#c3</a></div><div>[3] <a href="http://lists.tdwg.org/pipermail/tdwg-tag/2012-March/002487.html">http://lists.tdwg.org/pipermail/tdwg-tag/2012-March/002487.html</a><br>
</div><div>[4] <a href="http://rs.tdwg.org/dwc/terms/index.htm#genus">http://rs.tdwg.org/dwc/terms/index.htm#genus</a></div><div>[5] <a href="https://plus.google.com/114672072317054763788/posts/Nph2ksggNZW">https://plus.google.com/114672072317054763788/posts/Nph2ksggNZW</a></div>
<br><br><div class="gmail_quote">On Thu, Mar 15, 2012 at 17:28, Peter Desmet <span dir="ltr"><<a href="mailto:peter.desmet@umontreal.ca" target="_blank">peter.desmet@umontreal.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<div><br></div><div>Since most of the discussion happened on this tdwg-content and tdwg-tag mailing lists already, can't we continue here? I created a link to both from the issue page: <a href="http://code.google.com/p/darwincore/issues/detail?id=150#c2" target="_blank">http://code.google.com/p/darwincore/issues/detail?id=150#c2</a></div>
<div><br></div><div>I have been stuck in a meeting all day, while Tim Roberston wrote some convincing arguments against creating a canonicalScientificName term (<a href="http://code.google.com/p/darwincore/issues/detail?id=150#c1" target="_blank">http://code.google.com/p/darwincore/issues/detail?id=150#c1</a>), as did Rich Pyle (email March 14 <span style="color:rgb(34,34,34);font-size:13px;white-space:nowrap;font-family:arial,sans-serif">17:20 GMT-10:00). I will need some time to think about these. :-) I will try to write a coherent response tomorrow.</span></div>
<span><font color="#888888">
<div><span style="color:rgb(34,34,34);font-size:13px;white-space:nowrap;font-family:arial,sans-serif"><br></span></div><div><span style="color:rgb(34,34,34);font-size:13px;white-space:nowrap;font-family:arial,sans-serif">Peter</span></div>
</font></span></blockquote><div><br></div><div> </div></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>