<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class="">Dear CPN members,</div>
<div class=""><br class="">
</div>
<div class="">I realize that the December 10 target date for review of the code has passed. I am dealing with a family medical emergency and can’t involve myself with much of anything else until at least next week. Also, I will be sending you one other small
change in the code for consideration soon (a modification of Art. 11.9 that I think will not be controversial), plus a revision of Appendix A that Nico, Kevin and I have been working on. Therefore, we will have to postpone the ratification vote until after
the holidays. In the meanwhile, please review the code if you have not already so that we can vote on it in January and get on with submission to the publisher.</div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class="">Phil</div>
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Nov 19, 2018, at 3:51 PM, Cantino, Philip <<a href="mailto:cantino@ohio.edu" class="">cantino@ohio.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">
<div class="BodyFragment"><font size="2" class=""><span style="font-size:11pt;" class="">
<div class="PlainText">Dear CPN members,<br class="">
<br class="">
Although three members have not yet voted, all nine members who did (including Kevin and myself as “yes” votes) agree that the CPN can ratify the code without the preface and index. Kevin or I will send the preface to the CPN when it is done, but in the meanwhile,
the code as it now stands is attached for your review. <br class="">
<br class="">
Appendix A was last revised 12 years ago and needs updating. Because this appendix deals solely with registration procedures, the best person to revise it is clearly Nico. This is currently in progress; Nico sent comments yesterday and it is now up to me
and Kevin to reply, but it is likely to take a few back-and-forth drafts before the three of us settle on wording, and this may take some time (especially since this is a holiday week in the U.S.). I don’t want to delay sending the rest of the code to the
CPN while we finish that one appendix---which doesn’t even require CPN approval, as stated in its first paragraph, because of the nature of what it covers.<br class="">
<br class="">
I’m not sure how much time you will need to review the code. Is three weeks reasonable? I would ideally like to be done with this before people start heading off on winter-break travel. How about a target date of Monday, December 10? Please let me know
if this is too short a window to complete the job. <br class="">
<br class="">
Those of you who are relatively new on the CPN, please keep in mind that everything in the code has been approved by the CPN at one time or another, so calls for major change at this point would probably not be appropriate. However, corrections of minor problems
should be possible, and we will certainly want to fix any typos, incorrect citations of rules and recommendations, and other such errors that you might notice.<br class="">
<br class="">
Thank you!<br class="">
<br class="">
Phil<br class="">
<br class="">
<br class="">
<br class="">
</div>
</span></font></div>
<div class="BodyFragment"><font size="2" class=""><span style="font-size:11pt;" class="">
<div class="PlainText"><br class="">
<br class="">
> On Nov 15, 2018, at 4:17 PM, Cantino, Philip <<a href="mailto:cantino@ohio.edu" class="">cantino@ohio.edu</a>> wrote:<br class="">
> <br class="">
> Dear CPN members,<br class="">
> <br class="">
> Kevin and I are approaching completion of the PhyloCode and are hoping to submit the manuscript to CRC Press before the end of 2018. According to Article 22.3 of the code, "the CPN has the responsibility and power to ratify the first edition of the code
prior to its implementation.” Through the many drafts and versions of the code, all parts of it have been approved at least once by the CPN, but the code as a whole should be ratified by the CPN before the manuscript is sent to CRC.
<br class="">
> <br class="">
> At this point, the main body of the code (including preamble, principles, rules, recommendations, notes, appendices, and glossary) is finished and could be submitted to the CPN for ratification. The only parts that are not done are the preface and index,
neither one of which affects how the code functions. In order to expedite submission of the manuscript, Kevin and I suggest that the CPN review the completed body of the code while we continue to work on the preface (the index will be prepared by CRC Press,
after which we will check it). My question to you is this: Are you willing to vote on ratification of the code without seeing the preface, or do you want to wait until we have the entire manuscript (including the preface but not the index) assembled before
reviewing and voting on it? <br class="">
> <br class="">
> Phil<br class="">
<br class="">
Philip D. Cantino<br class="">
Department of Environmental and Plant Biology<br class="">
Ohio University<br class="">
Athens, OH 45701-2979<br class="">
<br class="">
Phone: (740) 593-1128<br class="">
Fax: (740) 593-1130<br class="">
<a href="mailto:cantino@ohio.edu" class="">email: cantino@ohio.edu</a><br class="">
<br class="">
<br class="">
<br class="">
<br class="">
</div>
</span></font></div>
</div>
<span id="cid:feb633aa-68d2-4e2b-a115-337440784f48@prod.exchangelabs.com"><PhyloCode version 6 for CPN.pdf></span></div>
</blockquote>
</div>
<br class="">
</body>
</html>