<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Dear Michel and other CPN members,</div>
<div class=""><br class="">
</div>
<div class="">We have received comments from all but one CPN member. The subcommittee will consider all the comments received and respond to the CPN, but I’m not sure when that will occur. In the meanwhile, if you or other CPN members want to send additional
comments in response to the ones recently received, feel free.</div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class="">Phil</div>
<div class=""><br class="">
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Mar 5, 2018, at 9:39 AM, Michel LAURIN <<a href="mailto:michel.laurin@mnhn.fr" class="">michel.laurin@mnhn.fr</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">
<div id="zimbraEditorContainer" style="font-family: arial, helvetica, sans-serif; font-size: 12pt;" class="1">
<div class="">Dear CPN members,<br class="">
</div>
<div class=""><br data-mce-bogus="1" class="">
</div>
<div class="">I agree with George; we should consider these problems carefully.<br data-mce-bogus="1" class="">
</div>
<div class=""><br class="">
</div>
<div class="">Phil, did you intend us to discuss these further, or will you (the subcommittee working on this) simply rework the relevant articles and come back with a revision later? I know from your comment from March 2 that we are still awaiting on one or
two Council members for their feedback, but do you need anything else from the rest of us?<br class="">
</div>
<div class=""><br data-mce-bogus="1" class="">
</div>
<div class="">Best wishes,<br data-mce-bogus="1" class="">
</div>
<div class=""><br data-mce-bogus="1" class="">
</div>
<div class="">Michel<br data-mce-bogus="1" class="">
</div>
<hr id="zwchr" data-marker="__DIVIDER__" class="">
<div data-marker="__HEADERS__" class=""><b class="">De: </b>"George Sangster" <<a href="mailto:g.sangster@planet.nl" class="">g.sangster@planet.nl</a>><br class="">
<b class="">À: </b>"Committee on Phylogenetic Nomenclature" <<a href="mailto:cpn@listserv.ohio.edu" class="">cpn@listserv.ohio.edu</a>><br class="">
<b class="">Envoyé: </b>Vendredi 2 Mars 2018 16:06:17<br class="">
<b class="">Objet: </b>Re: [CPN] Proposed changes to PhyloCode rules on publication<br class="">
</div>
<div class=""><br class="">
</div>
<div data-marker="__QUOTED_TEXT__" class=""><span class="st"></span>Dear CPN members,<br class="">
<br class="">
I have made a few comments on the proposed PhyloCode articles on what constitutes publication (see attached).<br class="">
<br class="">
I see two problems:<br class="">
<br class="">
Note 4.2.1. How do we deal with potential violations of the rule that papers must be peer reviewed? Must there be *evidence* that a journal (or paper) is peer-reviewed? In other words, is *lack of evidence* for peer-review sufficient reason to consider a name
unavailable? How can we tell if a paper was not peer-reviewed? (no journal will state this in print)<br class="">
<br class="">
Art. 4.5 and 5.1. "An electronic publication must not be altered after it is published" and the publication date is when it "first becomes available either in print or online".<br class="">
These rules seem to accept online pre-publications (pdfs), which may be (i) an accepted (but unedited) manuscript, (ii) uncorrected proofs, or (iii) corrected proofs (version of record). Any of these could be regarded as 'the 'first published version' of the
manuscript, depending on which versions are published. Some journals publish all these before the final paginated version appears online. Art. 4.5 in its present form would suggest that a published manuscript version could be the ‘correct’ one (because it’s
published first), and that the version of record and final version are just ‘corrections’ or ‘revisions’. Clearly, this is not desirable.<br class="">
<br class="">
I am attaching three papers on this subject, which I hope helps us make up our minds on this matter.<br class="">
<br class="">
All the best,<br class="">
George<br class="">
<br class="">
Dr George Sangster<br class="">
Department of Bioinformatics and Genetics,<br class="">
Swedish Museum of Natural History,<br class="">
P.O. Box 50007,<br class="">
SE–104 05 Stockholm,<br class="">
Sweden<br class="">
<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Op 6-2-2018 om 21:09 schreef Cantino, Philip:<br class="">
</div>
<blockquote cite="mid:EBE5BF01-9B2D-490E-B1E4-BCD601676A6B@ohio.edu" class="">
<pre class="">Dear CPN members,
Having now updated the CPN listserv membership, I am sending material for your consideration. As many of you are aware, the PhyloCode articles on what constitutes publication need to be revised to address electronic publication. I think the CPN was in general agreement on this point several years ago, but the details remained to be worked out. Over the past several months, Nico Cellinese and Dick Olmstead drafted a set of revisions to the current rules. Kevin and I then reviewed them, leading to further discussion among the four of us. The result is attached (“proposed publication requirements”).
Three other documents are also attached: “current publication requirements” (as they exist in PhyloCode version 5); “publication requirements with changes tracked”; and the full PhyloCode 5, in case some of you don’t have a copy on your computer. As you will see from the document with the tracked changes, most are in Article 4, but a few related changes are proposed in Articles 5 and 7.
I want to be sure that this message was received by the four new members (Jim Doyle, Micah Dunthorn, Sean Graham, and Max Cardoso Langer) and the two continuing members whose email addresses I just updated on the listserv (Michel Laurin and Dick Olmstead). Therefore, I’d appreciate it if the six of you would email me to confirm that you received this.
Let’s give everyone the rest of the week to read the proposed changes before we start discussing them. Although the revised text is not long, everyone is busy and I realize some of you may not have time to focus on this right away. I will be back in touch on Monday to ask for comments.
The address when emailing this listserv is <a class="moz-txt-link-abbreviated" href="mailto:cpn@listserv.ohio.edu" target="_blank">cpn@listserv.ohio.edu</a>.
Best regards,
Phil
</pre>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset> <br class="">
<pre class="">_______________________________________________
CPN mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CPN@listserv.ohio.edu" target="_blank">CPN@listserv.ohio.edu</a>
<a class="moz-txt-link-freetext" href="http://listserv.ohio.edu/mailman/listinfo/cpn" target="_blank">http://listserv.ohio.edu/mailman/listinfo/cpn</a>
</pre>
</blockquote>
<br class="">
<br class="">
_______________________________________________<br class="">
CPN mailing list<br class="">
<a href="mailto:CPN@listserv.ohio.edu" class="">CPN@listserv.ohio.edu</a><br class="">
http://listserv.ohio.edu/mailman/listinfo/cpn<br class="">
</div>
<div class=""><br class="">
</div>
<div data-marker="__SIG_POST__" class="">-- <br class="">
</div>
<div class="">Michel Laurin<br class="">
CR2P, UMR 7207<br class="">
Muséum National d'Histoire Naturelle<br class="">
Bâtiment de Géologie<br class="">
Case postale 48<br class="">
43 rue Buffon<br class="">
F-75231 Paris cedex 05<br class="">
FRANCE <br class="">
<a href="http://www2.mnhn.fr/hdt203/info/laurin.php" class="">http://www2.mnhn.fr/hdt203/info/laurin.php</a><br class="">
E-mail: michel.laurin@mnhn.fr<br class="">
</div>
</div>
</div>
_______________________________________________<br class="">
CPN mailing list<br class="">
<a href="mailto:CPN@listserv.ohio.edu" class="">CPN@listserv.ohio.edu</a><br class="">
http://listserv.ohio.edu/mailman/listinfo/cpn<br class="">
</div>
</blockquote>
</div>
<br class="">
<br class="">
</body>
</html>