<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><style><!--
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></div><div>Dear Kevin et al,<br></div><div><br data-mce-bogus="1"></div><div>My point is that it is not really clear, in your second example (below), that the definition would not apply here; it is clear only in the first case. But I made my point, no need to insist. If everybody else thinks that it is clear, I don't mind if this stays as it is.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Best wishes,<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Michel<br data-mce-bogus="1"></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>De: </b>"Kevin de Queiroz" <deQueirozK@si.edu><br><b>À: </b>"michel laurin" <michel.laurin@mnhn.fr><br><b>Cc: </b>"Committee on Phylogenetic Nomenclature" <cpn@listserv.ohio.edu>, "Max Langer" <mclanger@ffclrp.usp.br><br><b>Envoyé: </b>Lundi 25 Juin 2018 20:08:54<br><b>Objet: </b>Re: [CPN] Proposed additions to the PhyloCode (Art. 9)<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">Dear Michel et al.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">I’m not in favor of the change suggested by Michel because I don’t think it is appropriate to say “especially” here. The situation is that external specifiers can be used (with the “or” operator) either with
or without qualifying clauses to make names inapplicable in the context of particular phylogenies. To continue with my previous example, both of the following definitions would function similarly, making the name Pinnipedia inapplicable in the context of
phylogenies in which either bears, procyonids, or mustelids (or some combination of those taxa) are descended from the MRCA of seals, sea lions, and walruses:</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">1) With qualifying clause: Pinnipedia := the smallest clade containing Otaria byronia de Blainville 1820, Odobenus rosmarus Linnaeus 1758, and Phoca vitulina Linnaeus 1758, provided that it does not include
Ursus arctos Linnaeus 1758 or Procyon lotor (Linnaeus 1758) or Mustela erminea Linnaeus 1758.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">2) Without qualifying clause: Pinnipedia := the smallest clade containing Otaria byronia de Blainville 1820, Odobenus rosmarus Linnaeus 1758, and Phoca vitulina Linnaeus 1758 but not Ursus arctos Linnaeus
1758 or Procyon lotor (Linnaeus 1758) or Mustela erminea Linnaeus 1758.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Kevin</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Michel LAURIN <michel.laurin@mnhn.fr><br>
<b>Date: </b>Saturday, June 23, 2018 at 6:23 PM<br>
<b>To: </b>Kevin de Queiroz <deQueirozK@si.edu><br>
<b>Cc: </b>Committee on Phylogenetic Nomenclature <cpn@listserv.ohio.edu>, Max Langer <mclanger@ffclrp.usp.br><br>
<b>Subject: </b>Re: [CPN] Proposed additions to the PhyloCode (Art. 9)</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Dear Kevin,<br>
<br>
With this added information, I find the text much clearer. I would only suggest a one-word change in this part:</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Original wording:</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><br>
"For example, it would be<br>
appropriate to use “or” when using a minimum-clade definition with multiple<br>
external specifiers, <strong><span style="font-family:"Arial",sans-serif">including</span></strong> those used in qualifying clauses, to render the defined<br>
name inapplicable in the context of phylogenetic hypotheses in which any one (or<br>
more) of the external specifiers is more closely related to some of the internal<br>
specifiers than those internal specifiers are to other internal specifiers (see Art.<br>
11.12, Example 1)."</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Suggested modification:</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">"For example, it would be<br>
appropriate to use “or” when using a minimum-clade definition with multiple<br>
external specifiers, <strong><span style="font-family:"Arial",sans-serif">especially</span></strong> those used in qualifying clauses, to render the defined<br>
name inapplicable in the context of phylogenetic hypotheses in which any one (or<br>
more) of the external specifiers is more closely related to some of the internal<br>
specifiers than those internal specifiers are to other internal specifiers (see Art.<br>
11.12, Example 1)."</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">This is because it seems that this applies mostly in the context of qualifying clauses. Or would this also work in other portion of definitions?</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Best wishes,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Michel</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">
<hr width="100%" size="0" align="center">
</span></div>
<div>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">De:
</span></b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">"Kevin de Queiroz" <deQueirozK@si.edu><br>
<b>À: </b>"michel laurin" <michel.laurin@mnhn.fr>, "Committee on Phylogenetic Nomenclature" <cpn@listserv.ohio.edu><br>
<b>Cc: </b>"Max Langer" <mclanger@ffclrp.usp.br><br>
<b>Envoyé: </b>Vendredi 22 Juin 2018 21:04:15<br>
<b>Objet: </b>Re: [CPN] Proposed additions to the PhyloCode (Art. 9)</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Dear Michel,<br>
<br>
Right; the most recent version of the PhyloCode (version 5) is not up on the website, though it is available from Phil on request. I'm pasting Art. 11.12, Example 1 below.<br>
<br>
11.12. In order to prevent use of a name under certain hypotheses of relationships, clade composition, or both, phylogenetic definitions may include qualifying clauses specifying conditions under which the name cannot be applied to any clade (see Examples 1
and 2). <br>
<br>
Note 11.12.1. The following conventions are adopted for abbreviated qualifying clauses such as those in Examples 1 and 2: | = on the condition that; ~ = it does not; () = contain;
</span><span style="font-size:12.0pt;font-family:"Cambria Math",serif;color:black">∨</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> = or; anc = the ancestor in which the clade originated. See Note 9.4.1 for the other abbreviations
used in these examples.<br>
<br>
Example 1. The name Pinnipedia is traditionally applied to a group composed of sea lions (Otariidae), walruses (Odobenidae), and seals (Phocidae). However, under some phylogenetic hypotheses, the sister group of one or more of these taxa is a group of terrestrial
carnivorans (e.g., Ursidae, Procyonidae, Mustelidae). If the name Pinnipedia were to be defined as “the clade originating with the most recent common ancestor of Otaria byronia de Blainville 1820, Odobenus rosmarus Linnaeus 1758, and Phoca vitulina Linnaeus
1758, provided that it does not include Ursus arctos Linnaeus 1758 or Procyon lotor (Linnaeus 1758) or Mustela erminea Linnaeus 1758”, then the name would not be applicable to any clade in the context of phylogenetic hypotheses in which the most recent common
ancestor of Otaria byronia, Odobenus rosmarus, and Phoca vitulina was also inferred to be an ancestor of Ursus arctos or Procyon lotor or Mustela erminea. The phrase “provided that it does not include Ursus arctos Linnaeus 1758 (Ursidae) or Procyon lotor
(Linnaeus 1758) (Procyonidae) or Mustela erminea Linnaeus 1758 (Mustelidae)” is a qualifying clause. This definition may be abbreviated min
</span><span style="font-size:12.0pt;font-family:Symbol;color:black">Ñ</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> (Otaria byronia de Blainville 1820 & Odobenus rosmarus Linnaeus 1758 & Phoca vitulina Linnaeus 1758) | ~
(Ursus arctos Linnaeus 1758 </span><span style="font-size:12.0pt;font-family:"Cambria Math",serif;color:black">∨</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> Procyon lotor (Linnaeus 1758)
</span><span style="font-size:12.0pt;font-family:"Cambria Math",serif;color:black">∨</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> Mustela erminea Linnaeus 1758) (see Note 11.12.1).<br>
<br>
Kevin<br>
<br>
P.S. I'm not sure if the "or" symbols will come through. I had to reinsert them after pasting.<br>
<br>
On 6/21/18, 6:05 PM, "Michel LAURIN" <michel.laurin@mnhn.fr> wrote:<br>
<br>
Dear Kevin,<br>
<br>
That is much clearer, but some of this info needs to go into the text, unless it already is. A problem is that the current version ends with "see Art. 11.12, Example 1)", but I found no such article in the latest posted version of the PhyloCode, and so,
I did not find the example either.<br>
<br>
Best wishes,<br>
<br>
Michel<br>
<br>
----- Mail original -----<br>
De: "Kevin de Queiroz" <deQueirozK@si.edu><br>
À: "michel laurin" <michel.laurin@mnhn.fr>, "Committee on Phylogenetic Nomenclature" <cpn@listserv.ohio.edu><br>
Cc: "Max Langer" <mclanger@ffclrp.usp.br><br>
Envoyé: Jeudi 21 Juin 2018 23:12:13<br>
Objet: Re: [CPN] Proposed additions to the PhyloCode (Art. 9)<br>
<br>
Dear Michel,<br>
<br>
The problem is that if "and" is used in this context (qualifying clause), the definition will not function as intended. For example, if one wants the name Pinnipedia to be inapplicable in the context of phylogenies in which either ursids or mustelids or
both taxa are descended from the MRCA of seals, sea lions, and walruses, one must use "or" rather than "and" (Pinnipedia := the smallest crown clade containing seals, sea lions, and walruses, provided that it does not include ursids or mustelids). If "or"
is used, then the name Pinnipedia will not be applicable if either ursids, or mustelids, or both taxa are descended from the MRCA of seals, sea lions, and walruses. If "and" is used instead, then the name will only be inapplicable if BOTH ursids AND mustelids
are descended from the MRCA of seals, sea lions, and walruses. That is, the definition could result in ursids being included in Pinnipedia, or mustelids being included in Pinnipedia, contrary to the intent of the author. See the distinction between logical
disjunction ("or" operator) and logical conjunction ("and" operator). <br>
<br>
Best,<br>
Kevin<br>
<br>
On 6/21/18, 3:20 PM, "CPN on behalf of Michel LAURIN" <cpn-bounces@listserv.ohio.edu on behalf of michel.laurin@mnhn.fr> wrote:<br>
<br>
Dear all,<br>
<br>
I generally agree with the changes, but I find this part problematic:<br>
<br>
"For example, it would be<br>
appropriate to use “or” when using a minimum-clade definition with multiple<br>
external specifiers, including those used in qualifying clauses, to render the defined<br>
name inapplicable in the context of phylogenetic hypotheses in which any one (or<br>
more) of the external specifiers is more closely related to some of the internal<br>
specifiers than those internal specifiers are to other internal specifiers (see Art.<br>
11.12, Example 1)."<br>
<br>
I do not find obvious that using "or" in this context should be interpreted in this way. I think that if we keep this text, more explanation, not in a note, is in order. I interpret the "or" as leading to ambiguity in interpretation and I would simply
discourage (perhaps forbid) it.<br>
<br>
Best wishes,<br>
<br>
Michel<br>
<br>
----- Mail original -----<br>
De: "Philip Cantino" <cantino@ohio.edu><br>
À: "Committee on Phylogenetic Nomenclature" <cpn@listserv.ohio.edu><br>
Cc: "Max Langer" <mclanger@ffclrp.usp.br><br>
Envoyé: Lundi 18 Juin 2018 17:58:27<br>
Objet: [CPN] Proposed additions to the PhyloCode (Art. 9)<br>
<br>
Dear CPN members,<br>
<br>
Kevin and I are proposing the attached additions to Article 9 to clarify points of confusion that we became aware of in the process of editing Phylonyms contributions. These are probably the last changes in the code that we will propose before the
manuscript is finalized. <br>
<br>
If you have comments or questions, please send them to the listserv by June 30. If there is no ongoing discussion at that point, I will call for a vote. Please do not vote yet, in case there is discussion before June 30.<br>
<br>
Best regards,<br>
Phil<br>
<br>
<br>
_______________________________________________<br>
CPN mailing list<br>
CPN@listserv.ohio.edu<br>
http://listserv.ohio.edu/mailman/listinfo/cpn<br>
-- <br>
Michel Laurin<br>
CR2P, UMR 7207<br>
Muséum National d'Histoire Naturelle<br>
Bâtiment de Géologie<br>
Case postale 48<br>
43 rue Buffon<br>
F-75231 Paris cedex 05<br>
FRANCE <br>
http://www2.mnhn.fr/hdt203/info/laurin.php<br>
E-mail: michel.laurin@mnhn.fr<br>
-- <br>
Michel Laurin<br>
CR2P, UMR 7207<br>
Muséum National d'Histoire Naturelle<br>
Bâtiment de Géologie<br>
Case postale 48<br>
43 rue Buffon<br>
F-75231 Paris cedex 05<br>
FRANCE <br>
http://www2.mnhn.fr/hdt203/info/laurin.php<br>
E-mail: michel.laurin@mnhn.fr</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">--
</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Michel Laurin<br>
CR2P, UMR 7207<br>
Muséum National d'Histoire Naturelle<br>
Bâtiment de Géologie<br>
Case postale 48<br>
43 rue Buffon<br>
F-75231 Paris cedex 05<br>
FRANCE <br>
http://www2.mnhn.fr/hdt203/info/laurin.php<br>
E-mail: michel.laurin@mnhn.fr</span></p>
</div>
</div>
</div><br></div><div><br></div><div data-marker="__SIG_POST__">-- <br></div><div>Michel Laurin<br>CR2P, UMR 7207<br>Muséum National d'Histoire Naturelle<br>Bâtiment de Géologie<br>Case postale 48<br>43 rue Buffon<br>F-75231 Paris cedex 05<br>FRANCE <br>http://www2.mnhn.fr/hdt203/info/laurin.php<br>E-mail: michel.laurin@mnhn.fr<br></div></div></body></html>
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></div><div>Dear Kevin et al,<br></div><div><br data-mce-bogus="1"></div><div>My point is that it is not really clear, in your second example (below), that the definition would not apply here; it is clear only in the first case. But I made my point, no need to insist. If everybody else thinks that it is clear, I don't mind if this stays as it is.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Best wishes,<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Michel<br data-mce-bogus="1"></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>De: </b>"Kevin de Queiroz" <deQueirozK@si.edu><br><b>À: </b>"michel laurin" <michel.laurin@mnhn.fr><br><b>Cc: </b>"Committee on Phylogenetic Nomenclature" <cpn@listserv.ohio.edu>, "Max Langer" <mclanger@ffclrp.usp.br><br><b>Envoyé: </b>Lundi 25 Juin 2018 20:08:54<br><b>Objet: </b>Re: [CPN] Proposed additions to the PhyloCode (Art. 9)<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">Dear Michel et al.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">I’m not in favor of the change suggested by Michel because I don’t think it is appropriate to say “especially” here. The situation is that external specifiers can be used (with the “or” operator) either with
or without qualifying clauses to make names inapplicable in the context of particular phylogenies. To continue with my previous example, both of the following definitions would function similarly, making the name Pinnipedia inapplicable in the context of
phylogenies in which either bears, procyonids, or mustelids (or some combination of those taxa) are descended from the MRCA of seals, sea lions, and walruses:</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">1) With qualifying clause: Pinnipedia := the smallest clade containing Otaria byronia de Blainville 1820, Odobenus rosmarus Linnaeus 1758, and Phoca vitulina Linnaeus 1758, provided that it does not include
Ursus arctos Linnaeus 1758 or Procyon lotor (Linnaeus 1758) or Mustela erminea Linnaeus 1758.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">2) Without qualifying clause: Pinnipedia := the smallest clade containing Otaria byronia de Blainville 1820, Odobenus rosmarus Linnaeus 1758, and Phoca vitulina Linnaeus 1758 but not Ursus arctos Linnaeus
1758 or Procyon lotor (Linnaeus 1758) or Mustela erminea Linnaeus 1758.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Kevin</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Michel LAURIN <michel.laurin@mnhn.fr><br>
<b>Date: </b>Saturday, June 23, 2018 at 6:23 PM<br>
<b>To: </b>Kevin de Queiroz <deQueirozK@si.edu><br>
<b>Cc: </b>Committee on Phylogenetic Nomenclature <cpn@listserv.ohio.edu>, Max Langer <mclanger@ffclrp.usp.br><br>
<b>Subject: </b>Re: [CPN] Proposed additions to the PhyloCode (Art. 9)</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Dear Kevin,<br>
<br>
With this added information, I find the text much clearer. I would only suggest a one-word change in this part:</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Original wording:</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><br>
"For example, it would be<br>
appropriate to use “or” when using a minimum-clade definition with multiple<br>
external specifiers, <strong><span style="font-family:"Arial",sans-serif">including</span></strong> those used in qualifying clauses, to render the defined<br>
name inapplicable in the context of phylogenetic hypotheses in which any one (or<br>
more) of the external specifiers is more closely related to some of the internal<br>
specifiers than those internal specifiers are to other internal specifiers (see Art.<br>
11.12, Example 1)."</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Suggested modification:</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">"For example, it would be<br>
appropriate to use “or” when using a minimum-clade definition with multiple<br>
external specifiers, <strong><span style="font-family:"Arial",sans-serif">especially</span></strong> those used in qualifying clauses, to render the defined<br>
name inapplicable in the context of phylogenetic hypotheses in which any one (or<br>
more) of the external specifiers is more closely related to some of the internal<br>
specifiers than those internal specifiers are to other internal specifiers (see Art.<br>
11.12, Example 1)."</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">This is because it seems that this applies mostly in the context of qualifying clauses. Or would this also work in other portion of definitions?</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Best wishes,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Michel</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">
<hr width="100%" size="0" align="center">
</span></div>
<div>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">De:
</span></b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">"Kevin de Queiroz" <deQueirozK@si.edu><br>
<b>À: </b>"michel laurin" <michel.laurin@mnhn.fr>, "Committee on Phylogenetic Nomenclature" <cpn@listserv.ohio.edu><br>
<b>Cc: </b>"Max Langer" <mclanger@ffclrp.usp.br><br>
<b>Envoyé: </b>Vendredi 22 Juin 2018 21:04:15<br>
<b>Objet: </b>Re: [CPN] Proposed additions to the PhyloCode (Art. 9)</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Dear Michel,<br>
<br>
Right; the most recent version of the PhyloCode (version 5) is not up on the website, though it is available from Phil on request. I'm pasting Art. 11.12, Example 1 below.<br>
<br>
11.12. In order to prevent use of a name under certain hypotheses of relationships, clade composition, or both, phylogenetic definitions may include qualifying clauses specifying conditions under which the name cannot be applied to any clade (see Examples 1
and 2). <br>
<br>
Note 11.12.1. The following conventions are adopted for abbreviated qualifying clauses such as those in Examples 1 and 2: | = on the condition that; ~ = it does not; () = contain;
</span><span style="font-size:12.0pt;font-family:"Cambria Math",serif;color:black">∨</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> = or; anc = the ancestor in which the clade originated. See Note 9.4.1 for the other abbreviations
used in these examples.<br>
<br>
Example 1. The name Pinnipedia is traditionally applied to a group composed of sea lions (Otariidae), walruses (Odobenidae), and seals (Phocidae). However, under some phylogenetic hypotheses, the sister group of one or more of these taxa is a group of terrestrial
carnivorans (e.g., Ursidae, Procyonidae, Mustelidae). If the name Pinnipedia were to be defined as “the clade originating with the most recent common ancestor of Otaria byronia de Blainville 1820, Odobenus rosmarus Linnaeus 1758, and Phoca vitulina Linnaeus
1758, provided that it does not include Ursus arctos Linnaeus 1758 or Procyon lotor (Linnaeus 1758) or Mustela erminea Linnaeus 1758”, then the name would not be applicable to any clade in the context of phylogenetic hypotheses in which the most recent common
ancestor of Otaria byronia, Odobenus rosmarus, and Phoca vitulina was also inferred to be an ancestor of Ursus arctos or Procyon lotor or Mustela erminea. The phrase “provided that it does not include Ursus arctos Linnaeus 1758 (Ursidae) or Procyon lotor
(Linnaeus 1758) (Procyonidae) or Mustela erminea Linnaeus 1758 (Mustelidae)” is a qualifying clause. This definition may be abbreviated min
</span><span style="font-size:12.0pt;font-family:Symbol;color:black">Ñ</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> (Otaria byronia de Blainville 1820 & Odobenus rosmarus Linnaeus 1758 & Phoca vitulina Linnaeus 1758) | ~
(Ursus arctos Linnaeus 1758 </span><span style="font-size:12.0pt;font-family:"Cambria Math",serif;color:black">∨</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> Procyon lotor (Linnaeus 1758)
</span><span style="font-size:12.0pt;font-family:"Cambria Math",serif;color:black">∨</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> Mustela erminea Linnaeus 1758) (see Note 11.12.1).<br>
<br>
Kevin<br>
<br>
P.S. I'm not sure if the "or" symbols will come through. I had to reinsert them after pasting.<br>
<br>
On 6/21/18, 6:05 PM, "Michel LAURIN" <michel.laurin@mnhn.fr> wrote:<br>
<br>
Dear Kevin,<br>
<br>
That is much clearer, but some of this info needs to go into the text, unless it already is. A problem is that the current version ends with "see Art. 11.12, Example 1)", but I found no such article in the latest posted version of the PhyloCode, and so,
I did not find the example either.<br>
<br>
Best wishes,<br>
<br>
Michel<br>
<br>
----- Mail original -----<br>
De: "Kevin de Queiroz" <deQueirozK@si.edu><br>
À: "michel laurin" <michel.laurin@mnhn.fr>, "Committee on Phylogenetic Nomenclature" <cpn@listserv.ohio.edu><br>
Cc: "Max Langer" <mclanger@ffclrp.usp.br><br>
Envoyé: Jeudi 21 Juin 2018 23:12:13<br>
Objet: Re: [CPN] Proposed additions to the PhyloCode (Art. 9)<br>
<br>
Dear Michel,<br>
<br>
The problem is that if "and" is used in this context (qualifying clause), the definition will not function as intended. For example, if one wants the name Pinnipedia to be inapplicable in the context of phylogenies in which either ursids or mustelids or
both taxa are descended from the MRCA of seals, sea lions, and walruses, one must use "or" rather than "and" (Pinnipedia := the smallest crown clade containing seals, sea lions, and walruses, provided that it does not include ursids or mustelids). If "or"
is used, then the name Pinnipedia will not be applicable if either ursids, or mustelids, or both taxa are descended from the MRCA of seals, sea lions, and walruses. If "and" is used instead, then the name will only be inapplicable if BOTH ursids AND mustelids
are descended from the MRCA of seals, sea lions, and walruses. That is, the definition could result in ursids being included in Pinnipedia, or mustelids being included in Pinnipedia, contrary to the intent of the author. See the distinction between logical
disjunction ("or" operator) and logical conjunction ("and" operator). <br>
<br>
Best,<br>
Kevin<br>
<br>
On 6/21/18, 3:20 PM, "CPN on behalf of Michel LAURIN" <cpn-bounces@listserv.ohio.edu on behalf of michel.laurin@mnhn.fr> wrote:<br>
<br>
Dear all,<br>
<br>
I generally agree with the changes, but I find this part problematic:<br>
<br>
"For example, it would be<br>
appropriate to use “or” when using a minimum-clade definition with multiple<br>
external specifiers, including those used in qualifying clauses, to render the defined<br>
name inapplicable in the context of phylogenetic hypotheses in which any one (or<br>
more) of the external specifiers is more closely related to some of the internal<br>
specifiers than those internal specifiers are to other internal specifiers (see Art.<br>
11.12, Example 1)."<br>
<br>
I do not find obvious that using "or" in this context should be interpreted in this way. I think that if we keep this text, more explanation, not in a note, is in order. I interpret the "or" as leading to ambiguity in interpretation and I would simply
discourage (perhaps forbid) it.<br>
<br>
Best wishes,<br>
<br>
Michel<br>
<br>
----- Mail original -----<br>
De: "Philip Cantino" <cantino@ohio.edu><br>
À: "Committee on Phylogenetic Nomenclature" <cpn@listserv.ohio.edu><br>
Cc: "Max Langer" <mclanger@ffclrp.usp.br><br>
Envoyé: Lundi 18 Juin 2018 17:58:27<br>
Objet: [CPN] Proposed additions to the PhyloCode (Art. 9)<br>
<br>
Dear CPN members,<br>
<br>
Kevin and I are proposing the attached additions to Article 9 to clarify points of confusion that we became aware of in the process of editing Phylonyms contributions. These are probably the last changes in the code that we will propose before the
manuscript is finalized. <br>
<br>
If you have comments or questions, please send them to the listserv by June 30. If there is no ongoing discussion at that point, I will call for a vote. Please do not vote yet, in case there is discussion before June 30.<br>
<br>
Best regards,<br>
Phil<br>
<br>
<br>
_______________________________________________<br>
CPN mailing list<br>
CPN@listserv.ohio.edu<br>
http://listserv.ohio.edu/mailman/listinfo/cpn<br>
-- <br>
Michel Laurin<br>
CR2P, UMR 7207<br>
Muséum National d'Histoire Naturelle<br>
Bâtiment de Géologie<br>
Case postale 48<br>
43 rue Buffon<br>
F-75231 Paris cedex 05<br>
FRANCE <br>
http://www2.mnhn.fr/hdt203/info/laurin.php<br>
E-mail: michel.laurin@mnhn.fr<br>
-- <br>
Michel Laurin<br>
CR2P, UMR 7207<br>
Muséum National d'Histoire Naturelle<br>
Bâtiment de Géologie<br>
Case postale 48<br>
43 rue Buffon<br>
F-75231 Paris cedex 05<br>
FRANCE <br>
http://www2.mnhn.fr/hdt203/info/laurin.php<br>
E-mail: michel.laurin@mnhn.fr</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">--
</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Michel Laurin<br>
CR2P, UMR 7207<br>
Muséum National d'Histoire Naturelle<br>
Bâtiment de Géologie<br>
Case postale 48<br>
43 rue Buffon<br>
F-75231 Paris cedex 05<br>
FRANCE <br>
http://www2.mnhn.fr/hdt203/info/laurin.php<br>
E-mail: michel.laurin@mnhn.fr</span></p>
</div>
</div>
</div><br></div><div><br></div><div data-marker="__SIG_POST__">-- <br></div><div>Michel Laurin<br>CR2P, UMR 7207<br>Muséum National d'Histoire Naturelle<br>Bâtiment de Géologie<br>Case postale 48<br>43 rue Buffon<br>F-75231 Paris cedex 05<br>FRANCE <br>http://www2.mnhn.fr/hdt203/info/laurin.php<br>E-mail: michel.laurin@mnhn.fr<br></div></div></body></html>