Tony,<div><br></div><div>A mix up in the method generating APNI name strings reusing the HISPID hybrid indicator code for named hybrid - 'X' . Now fixed. Perhaps more interesting is that this method has been in place since 1992 and while, since then, the APNI web interface has addressed c. 12 million download requests not one of them has resulted in a complaint about the style of the hybrid indicator. I wonder if anybody cares.</div>
<div><br></div><div>One complaint that we do have though is that hybrid indicator upsets searching and sorting at least for named generic hybrids. It seems that users of the data would like to see it separated from the name string completely. </div>
<div><br></div><div>greg</div><div><br><div class="gmail_quote">On 12 December 2010 08:10, <span dir="ltr"><Tony.Rees@csiro.au></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Paul, all,<br>
<br>
Well, if the existing ANBG software code is displaying the hybrid symbol as an uppercase rather than a lowercase "x", then I would say there was something wrong with it, since this usage is not supported by the ICBN.<br>
<br>
In any case, to summarise, a recipient / parser of incoming taxonomic names and associated data must therefore be able to cope successfully with hybrid indicators for genera in any of the following formats:<br>
<br>
×Foo (ICBN preferred usage as per examples)<br>
× Foo (apparently tolerated, since white space appears to be optional??)<br>
x Foo (ICBN preferred alternative)<br>
X Foo (apparently incorrect, but found in some quite reputable systems)<br>
xFoo (again, probably tolerated, but not sure...)<br>
<br>
have I missed anything? (e.g. "Goo × Hoo" or variants thereof?)<br>
<br>
I am also presuming that in all these cases, the equivalent canonical version would be Foo. Does this mean that an extra DwC field would also be needed now, for hybrid indicator?<br>
<br>
Regards - Tony<br>
________________________________________<br>
From: Paul Murray [<a href="mailto:pmurray@anbg.gov.au">pmurray@anbg.gov.au</a>]<br>
Sent: Saturday, 11 December 2010 4:05 PM<br>
To: Rees, Tony (CMAR, Hobart)<br>
Cc: <a href="mailto:morris.bob@gmail.com">morris.bob@gmail.com</a>; <a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
<div class="im">Subject: Re: [tdwg-content] canonical name for named hybrid & infragenericnames [SEC=UNCLASSIFIED]<br>
<br>
</div><div><div></div><div class="h5">On 10/12/2010, at 5:47 PM, <Tony.Rees@csiro.au> <Tony.Rees@csiro.au> wrote:<br>
<br>
> Dear all,<br>
><br>
> Paul Murray wrote:<br>
><br>
>> A generic name may be marked as a hybrid. It is rendered<br>
>> × Foo<br>
><br>
><br>
> Actually my understanding is that ×Foo is the Code-endorsed version:<br>
<br>
<br>
Hmm ... . Well, perhaps there's an issue with our existing (software) code.<br>
<br>
<a href="http://www.anbg.gov.au/cgi-bin/apni?taxon_id=272817" target="_blank">http://www.anbg.gov.au/cgi-bin/apni?taxon_id=272817</a><br>
<a href="http://www.anbg.gov.au/cgi-bin/apni?taxon_id=40429" target="_blank">http://www.anbg.gov.au/cgi-bin/apni?taxon_id=40429</a><br>
<br>
There are only 9 genera in APNI that look like this.<br>
X Cynochloris Clifford & Everist<br>
X Calassodia M.A.Clem.<br>
X Agropogon P.Fourn.<br>
X Chilosimpliglottis Jeanes<br>
X Vappaculum M.A.Clem. & D.L.Jones<br>
X Taurodium D.L.Jones & M.A.Clem.<br>
X Glossadenia Kavulak<br>
X Cyanthera Hopper & <a href="http://A.P.Br" target="_blank">A.P.Br</a>.<br>
X Festulolium Asch. & Graebn.<br>
<br>
Perhaps the issue is that it's a shade tricky to get it right if you have to use the letter, and so we err on the side of caution and put spaces around the genus name. Although a multiplication sign is preferred to an 'x', I believe our powerbuilder interface was written back in the day before all this new-fangled unicode. Or perhaps it's simply that getting Windows to do proper multiplication signs involves explaining codepages to the windows oracle client: a byzantine process at best, and one which involves getting Admin access to the box. Hence the 'x'.<br>
<br>
(Once, ages ago, I got oracle sql-plus to work correctly on one Windows machine on the departmental network, but we never did succeed in getting the machine sitting right next to it to do umlauts properly. Our users addressed this issue by inserting html escape codes into the data.)<br>
<br>
In any case - anyone looking to parse names into their components may encounter something like this.<br>
<br>
Oh - here's some more:<br>
<br>
<a href="http://www.anbg.gov.au/cgi-bin/apni?taxon_id=257927" target="_blank">http://www.anbg.gov.au/cgi-bin/apni?taxon_id=257927</a><br>
xAstackea<br>
xAstackea 'Winter Pink'<br>
xChamecordia<br>
xChamecordia 'Eric John'<br>
xChamecordia 'Jasper'<br>
xChamecordia 'Southern Stars'<br>
xChamecordia 'Susie'<br>
xRhinochilus<br>
xRhinochilus 'Dorothy'<br>
<br>
I think that the issue is that these genera were only inserted into the data in order to make it possible to construct the cultivar name. The genera are not published scientific names at all - 'Chamecordia' doesn't appear anywhere as a genus name except in these records (heck: even google has never heard of it), but Wrigley, J. & Fagg, M. (2003) named the cultivars thusly, so we have to jam them into the data somehow.<br>
<br>
_______________________________________________<br>
<br>
<br>
<br>
If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments.<br>
<br>
Please consider the environment before printing this email.<br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a href="mailto:tdwg-content@lists.tdwg.org">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>
<br>
If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments.<br>
<br>
Please consider the environment before printing this email.<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Greg Whitbread<br>Australian National Botanic Gardens <br>Australian National Herbarium<br>+61 2 62509482<br><a href="mailto:ghw@anbg.gov.au">ghw@anbg.gov.au</a> <br>
</div>