[Previous by date - Re: Gender of species names?]
[Next by date - Re: Gender of species names?]
[Previous by subject - Fw: First International Phylogenetic Nomenclature Meeting]
[Next by subject - Fw: Minor rewordings of Article 17?]
Date: Thu, 18 Apr 2002 20:15:00 +0200
From: David Marjanovic <david.marjanovic@gmx.at>
To: PhyloCode mailing list <phylocode@ouvaxa.cats.ohiou.edu>
Subject: Fw: Gender of species names?
This is a multi-part message in MIME format. --Boundary_(ID_6/C94/t2hGcnIzWmn+sAyA) Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: quoted-printable Forwarded with permission, slightly edited: ----- Original Message = -------------------------------------------------------------------------= ------------------------------ From: JRW=20 To: David Marjanovic=20 Sent: Thursday, April 18, 2002 7:26 PM Subject: Re: Gender of species names? From my perspective, I see no reason why the full species names, = with either a hyphen or underscore, cannot be used to distinguish these = organisms, such as Oreamnos_americanus. Then we'll have bloodbaths about what to use in front of the hyphen or = whatever. Felis_leo, Panthera_leo or Leo_leo? I was under the impression that the new name was just to preserve what = people are used to. Before the _ was just the old genera name, but in = Phylocode would be rolled into the species name, no indication of the = "genera" implied. I know I've read that, Marc Ereshefhy's book if I = recall. Really all that matters is that the species names are unique = first, preserve some past second. This does not even include different = species names due to different species concepts for the same population. = This is why I'm convinced the only way this change will fly is if the = database is robust and flexible enough to handle all the variations. My = database I'll make sure will work. Numbers will not work, as some will complain about who gets the = first number! The one who registers first. Easy. (for one reason) Plus how will one remember that americanus1 means = Alces americana? This is one reason why I prefer method M instead -- clade addresses, = author & year, registration number etc. allowed. Definitely something that will have to be worked out as the critics will = use that ambiguity as their sword. Richard --Boundary_(ID_6/C94/t2hGcnIzWmn+sAyA) Content-type: text/html; charset="iso-8859-1" Content-transfer-encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 5.50.4912.300" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Forwarded with permission, slightly=20 edited:</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV style=3D"FONT: 10pt arial">----- Original Message=20 -------------------------------------------------------------------------= ------------------------------ <DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20 title=3Djrwakefield@convergeadv.com=20 href=3D"mailto:jrwakefield@convergeadv.com">JRW</A> </DIV> <DIV><B>To:</B> <A title=3Ddavid.marjanovic@gmx.at=20 href=3D"mailto:david.marjanovic@gmx.at">David Marjanovic</A> </DIV> <DIV><B>Sent:</B> Thursday, April 18, 2002 7:26 PM</DIV> <DIV><B>Subject:</B> Re: Gender of species names?</DIV></DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV><FONT face=3DArial size=3D2>From my perspective, I see no = reason why the=20 full species names, with either a hyphen or underscore, cannot be = used to=20 distinguish these organisms, such as=20 Oreamnos_americanus.</FONT></DIV></BLOCKQUOTE> <DIV dir=3Dltr><FONT face=3DArial size=3D2>Then we'll have bloodbaths = about what to=20 use in front of the hyphen or whatever. <EM>Felis_leo</EM>,=20 <EM>Panthera_leo</EM> or <EM>Leo_leo</EM>?</FONT></DIV></BLOCKQUOTE> <DIV dir=3Dltr><FONT face=3DArial size=3D2>I was under the impression = that the new=20 name was just to preserve what people are used to. Before the _ = was just=20 the old genera name, but in Phylocode would be rolled into the species = name, no=20 indication of the "genera" implied. I know I've read that, Marc=20 Ereshefhy's book if I recall. Really all that matters is that the = species=20 names are unique first, preserve some past second. This does not = even=20 include different species names due to different species concepts for = the same=20 population. This is why I'm convinced the only way this change = will fly is=20 if the database is robust and flexible enough to handle all the=20 variations. My database I'll make sure will = work.</FONT></DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV><FONT face=3DArial size=3D2>Numbers will not work, as some will = complain=20 about who gets the first number!</FONT></DIV></BLOCKQUOTE> <DIV dir=3Dltr><FONT face=3DArial size=3D2>The one who registers = first.=20 Easy.</FONT></DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV><FONT face=3DArial size=3D2>(for one reason) Plus how = will one=20 remember that americanus1 means <U>Alces=20 americana</U>?</FONT></DIV></BLOCKQUOTE> <DIV dir=3Dltr><FONT face=3DArial size=3D2>This is one reason why I = prefer method M=20 instead -- clade addresses, author & year, registration number = etc.=20 allowed.</FONT></DIV></BLOCKQUOTE> <DIV dir=3Dltr><FONT face=3DArial size=3D2>Definitely something that = will have to be=20 worked out as the critics will use that ambiguity as their = sword.</FONT></DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV> <DIV dir=3Dltr><FONT face=3DArial = size=3D2>Richard</FONT></DIV></BODY></HTML> --Boundary_(ID_6/C94/t2hGcnIzWmn+sAyA)--