<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear CPN members,<div><br></div><div>Quite a few changes were suggested on Wednesday, and it may take a while for Kevin and me to work through them by email and generate a new revision of the original set of proposals. I hope to be able to send it to you by the middle of next week but it could be later. </div><div><br></div><div>Regards,</div><div>Phil</div><div><br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span style="font-family:'Helvetica'; font-size:medium;">Michel Laurin <<a href="mailto:michel.laurin@upmc.fr">michel.laurin@upmc.fr</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span style="font-family:'Helvetica'; font-size:medium;">May 1, 2013 8:20:20 PM EDT<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>To: </b></span><span style="font-family:'Helvetica'; font-size:medium;">"<a href="mailto:cpn@listserv.ohio.edu">cpn@listserv.ohio.edu</a>" <<a href="mailto:cpn@listserv.ohio.edu">cpn@listserv.ohio.edu</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><b>Re: [CPN] Proposal to reorganize really just Note 9.3.1 this time</b><br></span></div><br>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi all,<br>
<br>
It is late, but I will be busy with something else tomorrow
(technically, later today because it is 2:20AM), so I just want to
add that after reading Kevin's and David's comments, with which I
agree (at least at first glance), if the changes outlined by both
are done, I think that I will feel comfortable voting for the
amendment.<br>
<br>
Good night,<br>
<br>
Michel<br>
<br>
On 02/05/13 02:10, David Marjanovic wrote:<br>
</div>
<blockquote cite="mid:5181AEE2.7010100@gmx.at" type="cite">
The entire text of the version I propose follows. Because it is so
different from the current wording, I have not marked additions
and deletions, except where I propose to delete entire paragraphs.<br>
<br>
=================================<br>
<br>
<i>Note 9.3.1.</i> The definition of "clade" is "an ancestor (an
organism, population, or species) and all of its descendants"
(Art. 2.1). Building on this definition, clade names can be
defined by pointing at such an ancestor, creating a phylogenetic
definition. This can be done in different ways, such as the
following:<br>
<ul>
<li>The ancestor can be mentioned directly in an ancestor-based
definition: "A and all its descendants", where A is a specific
organism, population, or species.</li>
<li>Usually, however, the intended ancestor is not directly
known. Thus, the ancestor can be indicated by its relation to
two or more specifiers (Art. 11) that are mentioned directly:</li>
<ul>
<li>A minimum-clade definition [note the hyphen which makes
clear that the clade, not the definition, is a minimum] may
take the form [...]</li>
<li>A maximum-clade definition may take the form [...]</li>
<li>An apomorphy-based definition may take the form [...]</li>
</ul>
<li>The ancestor can be indicated by its relation to two or more
specifiers that are not mentioned directly, but described as
members of another clade that fulfill certain criteria. Such
definitions may first describe an unnamed clade and then use
its extant members (or those fulfilling another criterion) as
specifiers for a minimum-clade definition:</li>
<ul>
<li>A maximum-modified crown clade definition [note the
addition of "-modified" to avoid confusion because crown
clades are minimum clades] may take the form [...]</li>
<li>An apomorphy-modified crown clade definition may take the
form [...]</li>
</ul>
<li>A crown clade in its entirety, mentioned by name, can be the
internal specifier in the definition of the name of a total
clade under the conditions specified in Art. 10.5. [This fact
contradicts a claim in Note 11.1.2.]<br>
</li>
</ul>
[deletion of the two paragraphs that follow this list in the
proposal we're currently discussing]<br>
<br>
The above list is not exhaustive. Most importantly, definitions
may contain qualifying clauses that restrict their applications to
specific phylogenetic hypotheses (Art. 11.9).<br>
<br>
The system of abbreviations used here [...]<br>
<br>
For abbreviations involving qualifying clauses, see Note 11.9.1.<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
CPN mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CPN@listserv.ohio.edu">CPN@listserv.ohio.edu</a>
<a class="moz-txt-link-freetext" href="http://listserv.ohio.edu/mailman/listinfo/cpn">http://listserv.ohio.edu/mailman/listinfo/cpn</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Michel Laurin
UMR 7207
Muséum National d’Histoire Naturelle
Batiment de Géologie
Case postale 48
43 rue Buffon
F-75231 Paris cedex 05
FRANCE
<a class="moz-txt-link-freetext" href="http://www2.mnhn.fr/hdt203/info/laurin.php">http://www2.mnhn.fr/hdt203/info/laurin.php</a></pre>
</div>
_______________________________________________<br>CPN mailing list<br><a href="mailto:CPN@listserv.ohio.edu">CPN@listserv.ohio.edu</a><br>http://listserv.ohio.edu/mailman/listinfo/cpn<br></blockquote></div><br></div></body></html>