<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="">In the absence of any further discussion, I think it is time for the CPN to vote on the proposed rules changes, as shown in the draft I sent on April 2. Please reply to the listserv.</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 Apr 2, 2018, at 1:06 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="" style="word-wrap:break-word; line-break:after-white-space">
<div class="">Dear CPN members,</div>
<div class=""><br class="">
</div>
<div class="">It is time to return to the proposed revision of the PhyloCode articles on publication, which the CPN considered in February and early March. The subcommittee that developed the proposal (Nico, Dick, Kevin and myself) held a Skype conference
on Friday to discuss your comments. We appreciate the time and thought that all of you devoted to this, and we carefully considered your suggestions, some of which are reflected in the attached revision. The new Note 4.2.1 addresses issues about electronic
publication that were raised by many of you. </div>
<div class=""><br class="">
</div>
<div class="">In the attached draft, the only changes tracked are the new ones resulting from your comments on the version I sent the CPN on Feb. 6. </div>
<div class="">
<div class=""><br class="webkit-block-placeholder">
</div>
<p class="x_MsoNormal">A few comments on the suggestions we did not adopt:</p>
<div class=""><br class="webkit-block-placeholder">
</div>
<p class="x_MsoNormal">Peer review: Even though it was a departure from the rank-based codes, the CPN decided years ago that peer review should be a requirement of the PhyloCode. The issue is one of quality control. Although it is not always possible to
determine easily if a publication was peer-reviewed, having the requirement reduces the likelihood of “taxonomic vandalism” (exploiting the lack of a peer-review requirement to publish names indiscriminately, to “scoop” rivals, or to sabotage the phylogenetic
nomenclature system). We don’t envision checking every name to be sure it was peer-reviewed; however, the requirement gives the CPN a basis to suppress works that are shown to be flagrant violations.</p>
<div class=""><br class="webkit-block-placeholder">
</div>
<p class="x_MsoNormal">Regarding Rec. 4.4B, it was suggested that we mention CLOCKSS. CLOCKSS is a dark archive designed to be a failsafe in case of a disaster and, as such, is largely inaccessible to individuals. By contrast, our goal is to encourage publication
in outlets that are not only archived but also provide broad accessibility. In addition, we deliberately avoided listing specific repositories, which may change over time. On the other hand, there is nothing in the recommendation to discourage the use of
CLOCKSS.</p>
<div class=""><br class="webkit-block-placeholder">
</div>
<p class="x_MsoNormal">Regarding Note 7.2.2, we retained the rule that material contained only in electronic supplements is not considered published as defined in this code. Our major concerns about electronic supplements are that they are not as carefully
reviewed as the main body of publications and that they may have less permanence.</p>
<div class="">I think we could vote soon on whether to adopt these revised rules, but let’s wait a few days to give everyone a chance for a final reading. There is no need to respond to this email unless there is a point you want to bring up for further consideration.
I will get back in touch with you early next week and ask for a vote.</div>
<div class=""><br class="">
</div>
<div class="">I am copying this message separately to Max because the listserv emails are not reaching him for some reason, even though he is listed on my administrative page as a subscriber. Please remember to copy your messages to his addresses <<a href="mailto:mclanger@ffclrp.usp.br" class="">mclanger@ffclrp.usp.br</a>,
<a href="mailto:langer.mc@gmail.com" class="">langer.mc@gmail.com</a>> when you send messages to the CPN listserv. </div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class="">Phil</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
<div class=""></div>
</div>
<div class="" style="word-wrap:break-word; line-break:after-white-space">
<div class=""></div>
<div class=""><br class="">
</div>
<br class="">
<br class="">
<div class="">
<div class=""><span class="" style="orphans:2; widows:2">Philip D. Cantino</span><br class="" style="orphans:2; widows:2">
<span class="" style="orphans:2; widows:2">Emeritus Professor</span><br class="" style="orphans:2; widows:2">
<span class="" style="orphans:2; widows:2">Department of Environmental and Plant Biology</span><br class="" style="orphans:2; widows:2">
<span class="" style="orphans:2; widows:2">Ohio University</span><br class="" style="orphans:2; widows:2">
<span class="" style="orphans:2; widows:2">Athens, OH 45701-2979</span><br class="" style="orphans:2; widows:2">
<br class="" style="orphans:2; widows:2">
<span class="" style="orphans:2; widows:2">Phone: (740) 593-1128</span><br class="" style="orphans:2; widows:2">
<span class="" style="orphans:2; widows:2">Fax: (740) 593-1130</span><br class="" style="orphans:2; widows:2">
<span class="" style="orphans:2; widows:2"><a href="mailto:cantino@ohio.edu" class="">email: cantino@ohio.edu</a></span><br class="" style="orphans:2; widows:2">
</div>
</div>
<br class="">
</div>
</div>
<span id="cid:9E64EBC0C1CCEE4390663F74C68FD83C@prod.exchangelabs.com"><revised publication requirements.docx></span></div>
</blockquote>
</div>
<br class="">
<br class="">
</body>
</html>