WARNING: This site looks best with a CSS-enabled browser.
The PhyloCode
Appendix A. Registration Procedures and Data Requirements
Most recent revision: June 2, 2006
This appendix may be revised more frequently than the main body of the code and without a formal meeting of the CPN. The most recent information is available on the Internet [URL will be inserted here] or from the database administrator: [address will be inserted here].
I. Registration procedures
After a name is submitted to the database, the registration submission is checked for missing data and the data are entered into a publicly available database under the auspices of the International Society for Phylogenetic Nomenclature. No registration number is issued at this time if the paper or book in which the name will appear has not yet been accepted. Once the paper or book has been accepted for publication, the author must submit the information that it has been accepted in order to receive a registration number. Alternatively, an author may wait until after acceptance for publication before submitting the name, in which case the registration number will be issued immediately.
If the spelling or definition of a submitted name is identical to one that already exists in the registration database, the author will be warned.
Registration should, if possible, make use of the Internet interface to the registration database. Submission of registration forms by mail is also permitted.
II. Data fields (mandatory data indicated with an asterisk)
1. Data common to all clade names
Contact information (for each author): name*, mailing address*, phone number*, fax number, email address, home page URL.
Name to be registered*
Type of name* (new clade name, converted clade name)
Date of registration*
Bibliographic reference to publication
Date of publication
Definition type* (node-based, branch-based, apomorphy-based, other ...)
Phylogenetic definition*
List of specifiers*
  • For a species cited as a specifier: name*, author*, year of publication*, code which governs the name*, URL of taxonomic database holding information
  • For an apomorphy cited as a specifier: description*
  • For a type specimen cited as a specifier: species name typified*, author of species name typified*, year of publication of species name typified*, code governing typified name*
  • For a specimen (other than a type) cited as a specifier: repository institution*, collection data needed to locate the specimen*, description*
Qualifying clause
Status of definition as emended (if appropriate)
Reference phylogeny (bibliographic reference, URL, or accession number in public repository)
Status of name as conserved or suppressed (if appropriate)
Author's comments
Administrator's annotations
2. Data particular to converted clade names
Preexisting name*
Author of preexisting name*
Direct bibliographic reference to original publication of preexisting name (including year)*
Code governing the preexisting name*
URL of taxonomic database holding information about the name
3. Data particular to new clade names
For a replacement name: replaced name*