<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif;font-size:small">Yes, I agree with David M on his comments and hope that the &quot;node&quot; stuff can be included -- kp</div></div><div class="gmail_extra">
    <br clear="all"><div><div dir="ltr"><div><font face="garamond,serif">Kevin Padian</font></div><div><font face="Garamond">Professor and Curator</font></div><div><font face="Garamond">Department of Integrative Biology and Museum of Paleontology</font></div>
    <div><font face="Garamond">University of California, Berkeley CA 94720</font></div></div></div>
    <br><br><div class="gmail_quote">On Sun, Sep 15, 2013 at 11:14 PM, Michel Laurin <span dir="ltr">&lt;<a href="mailto:michel.laurin@upmc.fr" target="_blank">michel.laurin@upmc.fr</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




      <div text="#000000" bgcolor="#FFFFFF">
        <div>Dear colleagues,<br>
          <br>
          ��� I approve the changes.<br>
          <br>
          ��� Michel<br>
          <br>
          On 16/09/13 01:50, Cantino, Philip wrote:<br>
        </div>
        <blockquote type="cite">

          <div>
            <div>Dear CPN members,</div>
            <div><br>
            </div>
            <div>In the absence of any more comments, I am calling for a
              vote on slightly modified versions of the two sets of proposed
              code changes I sent you on Sept. 6. � The only difference
              between the attached versions and the Sept. 6 ones is that
              David M&#39;s corrections of typos, formatting, etc. have been
              incorporated. �Kevin and I also agree with his recommendation
              that &quot;node&quot; be retained in the glossary, and that Note 9.7.1
              be modified to say that an apomorphy-based definition
              necessarily identifies a clade provided that there is only one
              internal specifier. �Those changes from the Sept. 6 proposals
              are also incorporated in the attached document PhyloCode4c2.</div>
            <div><br>
            </div>
            <div>I interpret David M&#39;s and Brian&#39;s comments as a YES vote on
              the attached versions, unless they tell me otherwise.
              �Everyone else, please vote by this Friday (Sept. 20) by
              responding to all.</div>
            <div><br>
            </div>
            <div>Phil</div>
            <div><br>
            </div>
            <div>
              <div>
                <div>
                </div>
              </div>
            </div>
            <div><br>
            </div>
          </div>
          <div><br>
            <div><br>
              <div>Begin forwarded message:</div>
              <br>
              <blockquote type="cite">
                <div style="margin:0px">
                  <span style="font-family:&quot;Helvetica&quot;;font-size:medium"><b>From:
                    </b></span><span style="font-family:&quot;Helvetica&quot;;font-size:medium">&quot;Cantino, Philip&quot; &lt;<a href="mailto:cantino@ohio.edu" target="_blank">cantino@ohio.edu</a>&gt;<br>
                  </span></div>
                <div style="margin:0px">
                  <span style="font-family:&quot;Helvetica&quot;;font-size:medium"><b>Subject:
                    </b></span><span style="font-family:&quot;Helvetica&quot;;font-size:medium"><b>Re: [CPN] two new sets of changes
                      to consider</b><br>
                  </span></div>
                <div style="margin:0px">
                  <span style="font-family:&quot;Helvetica&quot;;font-size:medium"><b>Date:
                    </b></span><span style="font-family:&quot;Helvetica&quot;;font-size:medium">September 13, 2013 4:08:04 PM EDT<br>
                  </span></div>
                <div style="margin:0px">
                  <span style="font-family:&quot;Helvetica&quot;;font-size:medium"><b>To:
                    </b></span><span style="font-family:&quot;Helvetica&quot;;font-size:medium">Committee on Phylogenetic Nomenclature
                    &lt;<a href="mailto:cpn@listserv.ohio.edu" target="_blank">cpn@listserv.ohio.edu</a>&gt;<br>
                  </span></div>
                <br>
                <div>Thank you, David M, for a very careful reading of the
                  proposals. �I have corrected the various formatting
                  errors, typos, and missing dates that David pointed out.
                  �(Incidentally, I agree with his &quot;pet peeve&quot; about the
                  period belonging inside the parentheses, but I overlooked
                  it in the spot he pointed out.)<br>
                  <br>
                  I will correct the references to various examples of Art.
                  11.13 if the CPN votes to approve the revision of Art.
                  11.12-11.14 that you have been considering this week.
                  �Most of David&#39;s other suggested changes are not directly
                  related to this set of proposals, so we can delay their
                  consideration until after voting on the current proposals.<br>
                  <br>
                  Two points in David&#39;s message are relevant to the current
                  set of proposals: deletion of the definition of &quot;node&quot;
                  from the glossary, and clarification of a point he raised
                  about Note 9.7.1. �I sent my recommendation on these two
                  items to Kevin a few minutes ago and am awaiting his
                  reply. �<br>
                  <br>
                  Today was the tentative deadline for comments. �If you
                  intend to comment on the proposals I sent last Friday,
                  please either do so today or request an extension. �If I
                  do not hear from anyone by the end of the day, I will call
                  for a vote as soon as Kevin and I decide how we want to
                  address the two issues David raised.<br>
                  <br>
                  Phil<br>
                  <br>
                  <br>
                  On Sep 11, 2013, at 5:47 PM, David Marjanovic wrote:<br>
                  <br>
                  <blockquote type="cite">
                    <blockquote type="cite">I am attaching two sets of
                      proposed changes for your consideration (one of them
                      in two forms--one showing the changes using Track
                      Changes and the other with the changes accepted for
                      ease of reading). �The shorter document (Art.
                      11.12-11.14) deals with qualifying clauses and other
                      mechanisms that can be used to restrict the
                      application of a name with respect to particular
                      hypotheses of relationship or clade composition.<br>
                    </blockquote>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite">Art. 11.12, Example 1: In the
                    4th-to-last line there&#39;s &quot;*Multelidae*&quot; instead of
                    *Mustelidae*.<br>
                  </blockquote>
                  <blockquote type="cite">Art. 11.13, Example 3: The year of
                    *Podocarpus macrophyllus* (Thunberg) Sweet is missing.<br>
                  </blockquote>
                  <blockquote type="cite">Pet peeve alert: At the very end,
                    put the period in front of the closing parenthesis. When
                    you put a whole sentence into parentheses, put the whole
                    sentence, including the period at its end, into
                    parentheses.<br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite">Otherwise, I approve.<br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite">
                    <blockquote type="cite">The other attached document
                      consists of nearly the entire code �This draft
                      (version 4c2) consists of the current (posted online
                      in 2010) PhyloCode version 4c (excluding the Preface
                      and Index) with the addition of modifications approved
                      by the CPN in a series of votes between September 2012
                      and August 5, 2013.<br>
                    </blockquote>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite">I approve of all changes except
                    the deletion of &quot;node&quot; from the glossary; I have not
                    systematically looked for uncorrected cross-references.<br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite">There&#39;s an extra period between
                    Principles 5 and 6.<br>
                  </blockquote>
                  <blockquote type="cite">In Principle 6, I&#39;d like to
                    propose replacing &quot;a given&quot; by &quot;any particular&quot;.<br>
                  </blockquote>
                  <blockquote type="cite">Note 6.1A1 states that italicizing
                    all taxon names is not consistent with the ICZN. The
                    passage of the ICZN that says only genus and species
                    names should be italicized, however, is &quot;only&quot; General
                    Recommendation 6: &quot;6. The scientific names of genus- or
                    species-group taxa should be printed in a type-face
                    (font) different from that used in the text; such names
                    are usually printed in italics, which should not be used
                    for names of higher taxa. Species�group names always
                    begin with a lower-case letter, and when cited should
                    always be preceded by a generic name (or an abbreviation
                    of one); names of all supraspecific taxa begin with an
                    upper-case (capital) letter.&quot;
                    <a href="http://www.nhm.ac.uk/hosted-sites/iczn/code/includes/page.jsp?nfv=&amp;booksection=appendixB" target="_blank">http://www.nhm.ac.uk/hosted-sites/iczn/code/includes/page.jsp?nfv=&amp;booksection=appendixB</a><br>

                  </blockquote>
                  <blockquote type="cite">Note 9.5.2: &quot;Art. 11.12, example
                    5&quot;, which does not currently exist, will become Art.
                    11.13, Example 1 under the other proposal.<br>
                  </blockquote>
                  <blockquote type="cite">Note 9.6.1: &quot;Art. 11.12, Example
                    4&quot;, which does not currently exist, will become Art.
                    11.13, Example 2 under the other proposal.<br>
                  </blockquote>
                  <blockquote type="cite">Note 9.7.1: &quot;An apomorphy-based
                    definition as described in Art. 9.7 necessarily
                    identifies a clade&quot; only if it has only one internal
                    specifier.<br>
                  </blockquote>
                  <blockquote type="cite">Art. 9.8: Note 9.8.1 should be
                    indented twice to make clear that the bulleted examples
                    below it belong directly to the Article, not to the
                    Note, and that the Note refers specifically to the
                    example above it. In the first example after the Note,
                    &quot;Art. 11.12, Example 3&quot; will become Art. 11.13, Example
                    2 under the other proposal. I&#39;m confused now, because
                    &quot;Art. 11.12, Example 4&quot; must correspond to the same
                    Example...<br>
                  </blockquote>
                  <blockquote type="cite">Art. 9.9: In the second example,
                    &quot;Art. 11.12, Example 3&quot; will become Art. 11.13, Example
                    2 under the other proposal.<br>
                  </blockquote>
                  <blockquote type="cite">Art. 9.10: Replace &quot;Art. 9.10,&quot; by
                    &quot;Art. 9.10.&quot;.<br>
                  </blockquote>
                  <blockquote type="cite">Art. 17.1: I propose deleting
                    &quot;foreign to classical Latin&quot;. Not only is it
                    unnecessary, but � I think we had that discussion a few
                    years ago � there is a diacritical sign that was used in
                    Classical Latin, even in stone inscriptions:
                    <a href="https://en.wikipedia.org/wiki/Apex_%28diacritic%29" target="_blank">https://en.wikipedia.org/wiki/Apex_%28diacritic%29</a><br>
                  </blockquote>
                  <blockquote type="cite">Art. 17.5, taken literally,
                    appears to contradict Art. 17.1 and 17.2.<br>
                  </blockquote>
                  <blockquote type="cite">Art. 20: Two Examples use &quot;2010&quot;;
                    that&#39;s over...<br>
                  </blockquote>
                  <blockquote type="cite">Glossary: The term &quot;node&quot; is still
                    used in the glossary entries for &quot;branch&quot; and
                    &quot;phylogenetic tree&quot;, and in the footnote to Art. 9.5
                    (and 9.6).<br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite"><br>
                  </blockquote>
                  <blockquote type="cite">_______________________________________________<br>
                  </blockquote>
                  <blockquote type="cite">CPN mailing list<br>
                  </blockquote>
                  <blockquote type="cite"><a href="mailto:CPN@listserv.ohio.edu" target="_blank">CPN@listserv.ohio.edu</a><br>
                  </blockquote>
                  <blockquote type="cite"><a href="http://listserv.ohio.edu/mailman/listinfo/cpn" target="_blank">http://listserv.ohio.edu/mailman/listinfo/cpn</a><br>
                  </blockquote>
                  <br>
                </div>
              </blockquote>
            </div>
            <br>
          </div>
          <br>
          <fieldset></fieldset>
          <br>
          <pre>_______________________________________________
    CPN mailing list
    <a href="mailto:CPN@listserv.ohio.edu" target="_blank">CPN@listserv.ohio.edu</a>
    <a href="http://listserv.ohio.edu/mailman/listinfo/cpn" target="_blank">http://listserv.ohio.edu/mailman/listinfo/cpn</a><span class="HOEnZb"><font color="#888888">
    </font></span></pre><span class="HOEnZb"><font color="#888888">
        </font></span></blockquote><span class="HOEnZb"><font color="#888888">
        <br>
        <br>
        <pre 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 href="http://www2.mnhn.fr/hdt203/info/laurin.php" target="_blank">http://www2.mnhn.fr/hdt203/info/laurin.php</a></pre>
      </font></span></div>

    <br>_______________________________________________<br>
    CPN mailing list<br>
    <a href="mailto:CPN@listserv.ohio.edu">CPN@listserv.ohio.edu</a><br>
    <a href="http://listserv.ohio.edu/mailman/listinfo/cpn" target="_blank">http://listserv.ohio.edu/mailman/listinfo/cpn</a><br>
    <br></blockquote></div><br></div>
    View Site in Mobile | Classic
    Share by: