CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"/> <meta name="robots" content="noindex, nofollow" /> <title>About — The Plant List</title> <link rel="search" type="application/opensearchdescription+xml" href="/opensearch.xml" title="The Plant List" /> <script type="text/javascript" src="/img/jquery-1.4.3.min.js"></script> <script type="text/javascript" src="/img/jquery.tablesorter.min.js"></script>  <script type="text/javascript" src="/img/bsn.AutoSuggest_2.1.3.js"></script> <script type="text/javascript" src="/img/tpl.js"></script> <link rel="stylesheet" href="/img/tpl.css"/>    </head> <body> <header> <h1><a href="/1/">The Plant List — A working list for all plant species</a></h1> <form id="headerSearchForm" action="/tpl/search" method="get"> <input id="q" name="q" placeholder="Enter a genus or genus and species" type="search" value="" size="40"/> <input type="submit" value="Search" /> </form> </header> <nav> <ul> <li><a href="/1/">Home</a></li> <li><a class="current">About</a></li> <li><a href="/browse/">Browse</a></li> <li><a href="/statistics/">Statistics</a></li> <li><a href="/feedback/">Feedback</a></li> <li><a href="/help/">How to use this site</a></li> </ul> </nav> <div id="container"> <div id="logo"> <ul> <li><a href="http://www.cbd.int/2010/"><img src="/img/logo-2010.gif" alt="2010 International Year of Biodiversity"/></a></li> <li><a href="http://www.kew.org/"><img src="/img/logo-kew.gif" alt="Royal Botanic Gardens, Kew"/></a></li> <li><a href="http://www.mobot.org/"><img src="/img/logo-missouri.gif" alt="Missouri Botanical Garden"/></a></li> <li><a href="http://www.compositae.org/checklist/"><img src="/img/logo-tica.gif" alt="International Compositae Alliance"/></a></li> <li><a href="http://www.ildis.org/"><img src="/img/logo-ildis.gif" alt="ILDIS"/></a></li> <li><a href="http://plantnet.rbgsyd.nsw.gov.au/iopi/iopihome.htm"><img src="/img/logo-iopi.png" alt="IOPI"/></a></li> <li><a href="http://www.nybg.org/"><img src="/img/logo-nybg.gif" alt="New York Botanic Garden"/></a></li> <li><a href="http://www.ipni.org/"><img src="/img/logo-ipni.gif" alt="International Plant Names Index"/></a></li> <li><a href="http://www.cbd.int/"><img src="/img/logo-cbd.gif" alt="Convention on Biological Diversity"/></a></li> </ul> </div> <div id="columns"> <section id="warnVersion"> <p><strong>⚠ Version 1 of The Plant List has been superseded.</strong></p> <p>You should refer instead to <a href="/">the current version of The Plant List</a>.</p> </section> <section> <h1>About <cite>The Plant List</cite></h1> <p><cite>The Plant List</cite> is a working list of all known plant species. Version 1, released in December 2010, aims to be comprehensive for species of Vascular plant (flowering plants, conifers, ferns and their allies) and of <i class="majorgroup">Bryophytes</i> (mosses and liverworts). It does not include algae or fungi. Version 1 contains 1,244,871 scientific plant names of which 298,900 are accepted species names. It includes no vernacular or common plant names.</p> <p>Collaboration between the Royal Botanic Gardens, Kew and Missouri Botanical Garden enabled the creation of <cite>The Plant List</cite> by combining multiple checklist datasets held by these institutions and other <a href="#collaborators">collaborators</a>.</p> <p><cite>The Plant List</cite> provides the <a href="#accepted">Accepted</a> Latin name for most species, with links to all <a href="#synonym">Synonyms</a> by which that species has been known. It also includes <a href="#unresolved">Unresolved</a> names for which the contributing data sources did not contain sufficient evidence to decide whether they were Accepted or Synonyms.</p> <p>A description of the content, creation and use of <cite>The Plant List</cite> follows.</p> </section> <section> <h1>Contents</h1> <ul> <li><a href="#overview">Overview</a></li> <li><a href="#audience">Target audience</a></li> <li><a href="#scope">Scope</a></li> <li> <a href="#description">Description of <cite>The Plant List</cite> data set</a> <ul> <li><a href="#taxonomic-coverage">Taxonomic coverage</a></li> <li><a href="#nomenclatural-coverage">Nomenclatural coverage</a></li> <li><a href="#status">The Status of name records</a></li> <li><a href="#annotation">Annotation of names</a></li> <li><a href="#confidence">Confidence Levels</a></li> </ul> </li> <li> <a href="#collaborators">Contributing data sets</a> <ul> <li><a href="#globalspeciesresources">Global species resources</a></li> <li><a href="#regional">Floristic Datasets</a></li> <li><a href="#nomenclatural">Plant nomenclatural resources</a></li> </ul> </li> <li> <a href="#created">How <cite>The Plant List</cite> was Created</a> <ul> <li><a href="#merging">The Sequence for Merging Data Sets</a></li> <li><a href="#derivation">Derivation of Name Status</a></li> <li><a href="#rules">Decision Rules to arbitrate between Conflicts of Opinion</a></li> <li><a href="#analysis">Data analysis of logical inconsistencies and data integrity issues</a></li> <li><a href="#resolution">Resolution of logical inconsistencies and data integrity issues</a></li> <li><a href="#publication">Online Publication of <cite>The Plant List</cite></a></li> <li><a href="#nextsteps">Next Steps</a></li> </ul> </li> <li><a href="#team">The project team</a></li> <li><a href="#enhancing">Enhancing <cite>The Plant List</cite></a></li> <li><a href="#relationships">Relationships to other resources</a></li> </ul> </section> <section> <h1 id="overview">Overview</h1> <p><cite>The Plant List</cite> is a widely accessible working list of known plant species and has been developed and disseminated as a direct response to the <a rel="external" href="http://www.cbd.int/gspc/">Global Strategy for Plant Conservation</a>, adopted in 2002 by the 193 governments who are Parties to the Convention on Biological Diversity. The GSPC was designed as a framework for action to halt the loss of plant diversity. Target 1 of the Strategy called for the completion by 2010 of <q>a widely accessible working list of all known plant species, as a step towards a complete world Flora</q>. Released in December 2010, Version 1 of <cite>The Plant List</cite> aims to be comprehensive for species of Vascular plant (flowering plants, conifers, ferns and their allies) and of Bryophytes (mosses and liverworts). This is consistent with the initial focus of the GSPC.</p> <p><cite>The Plant List</cite> is not perfect and represents work in progress. Our aim was to produce a ‘best effort’ list by 2010 to demonstrate progress and stimulate further work.</p> <p><cite>The Plant List</cite> was produced as a collaborative venture coordinated by the Royal Botanic Gardens, Kew and the Missouri Botanical Garden and involving <a href="#collaborators">collaborators</a> worldwide.</p> <p>Data records from numerous existing global checklist databases (derived from primary taxonomic publications) were brought together and combined with regional and national checklist data and other records from Tropicos. These resources were then complemented by the inclusion of additional names found in <a rel="external" href="http://www.ipni.org/"><abbr title="International Plant Name Index">IPNI</abbr></a> (for Angiosperms, Gymnosperms and Fern & Fern Allies). <cite>The Plant List</cite> may omit some names and may include some duplicate names. Furthermore those names derived from nomenclators may not include any indication of whether they are <a href="#accepted">Accepted</a> names or <a href="#synonym">Synonyms</a>. Our purpose has been to detect inconsistencies between overlapping data sources and resolve them.</p> <p><cite>The Plant List</cite> does not seek to duplicate the efforts of collaborators that have contributed data to the creation of <cite>The Plant List</cite>. This version will not be edited but feedback will be forwarded to our collaborators so that they can extend and improve their original data. (see <a href="#enhancing">Enhancing <cite>The Plant List</cite></a> and <a href="#created">Recreating <cite>The Plant List</cite></a>). Feedback will arise from our own analysis of the data (and its comparison with other resources) and from users of <cite>The Plant List</cite> (see <a href="/feedback/#comment">How to Submit Feedback</a>).</p> <p>In the future we hope to</p> <ol> <li>include improved and extended versions of the data sets included in this version of <cite>The Plant List</cite></li> <li>to include other data sets which we were unable to include in Version 1 and</li> <li>to refine the procedures that were used to create <cite>The Plant List</cite>: e.g. for locating duplicate name records, for resolving inconsistencies and for detecting conflicting opinions expressed within alternative data sets and then for selecting from among those opinions (see <a href="#created">How <cite>The Plant List</cite> was Created</a>).</li> </ol> <p>We welcome <a href="/feedback/#comment">comments</a> on the content of <cite>The Plant List</cite>, and offers of <a href="/feedback/#contribute">contributions</a> for inclusion in the next edition.</p> </section> <section> <h1 id="audience">Target audience</h1> <p>The name of a plant is the key to communicating about it and to finding information about its uses, conservation status, relationships and place within ecosystems. <cite>The Plant List</cite> provides a tool for resolving or verifying the spelling of plant names and a means to find from a global view the botanically accepted name for a plant and all of its alternative synonyms. Since the ability to plan the sustainable use of plants, essential resources for food, medicines, and ecosystem services depends on effective retrieval of information about plants there is a broad constituency of potential users of <cite>The Plant List</cite>.</p> </section> <section> <h1 id="scope">Scope</h1> <p><cite>The Plant List</cite> is a working list of known plant species, which aims to be comprehensive in coverage at species level for all names of mosses and liverworts and their allies (<a href="#bryophytes"><i class="majorgroup">Bryophytes</i></a>) and of <a href="#taxonomic-coverage">Vascular plants</a> which include the flowering plants (<a href="#angiosperms"><i class="majorgroup">Angiosperms</i></a>), conifers, cycads and their allies (<a href="#gymnosperms"><i class="majorgroup">Gymnosperms</i></a>) and the ferns and their allies including horsetails and club mosses (<a href="#pteridophytes"><i class="majorgroup">Pteridophytes</i></a>).</p> <p>For each name at species level we aim to provide the author of the name, the original place of publication and an assessment of whether the name is <a href="#accepted">accepted</a> or is a <a href="#synonym">synonym</a> for another name from data resources held by Kew, by Missouri Botanical Garden and by our <a href="#collaborators">collaborators</a>. Wherever possible for each name included links are also provided to the original online database record, to its corresponding entry in IPNI and to further sources of information about that plant.</p> <p>The names of some subspecies or varieties of plant are also included in <cite>The Plant List</cite> primarily where they are synonyms or accepted names for species names and where they were available from the contributing data sets. <cite>The Plant List</cite> does not aspire to comprehensive coverage of infraspecific taxa (subspecies, varieties, forms etc.).</p> <h2 id="excluded">What does <cite>The Plant List</cite> not contain?</h2> <p>Version 1 of <cite>The Plant List</cite> does not contain:</p> <ul> <li>scientific names for fossil plants, algae or fungi;</li> <li>common (or vernacular) names for the plants included;</li> <li>the geographic distribution or any other data about the plants included (though such data may be obtained from the source databases in many instances).</li> </ul> </section> <section> <h1 id="description">Description of <cite>The Plant List</cite> data set</h1> <h2 id="taxonomic-coverage">Taxonomic coverage</h2> <p><cite>The Plant List</cite> includes all known species of the following major plant groups:</p> <ul> <li>Angiosperms</li> <li>Gymnosperms</li> <li>Pteridophytes</li> <li>Bryophytes</li> </ul> <p>Genera and species are presented in families which follow the source database(s) except in the case of Angiosperms where we have, wherever possible allocated accepted genera to the families recognised by the Angiosperm Phylogeny Group.</p> <h3 id="angiosperms">Angiosperms</h3> <p><i class="majorgroup">Angiosperms</i> (Subclass <i class="subclass">Magnoliidae</i> Novák ex Takht.). Subclass level classification follows Chase, M.W. & Reveal, J.L., 2009. <cite>A phylogenetic classification of the land plants to accompany APG III</cite>. Botanical Journal of the Linnean Society, 161, 122–127.</p> <p>Genera and species of <i class="majorgroup">Angiosperms</i> are presented in families following family circumscriptions in The Angiosperm Phylogeny Group, 2009. <cite>An update of the Angiosperm Phylogeny Group classification for the orders and families of flowering plants: APG III</cite>. Botanical Journal of the Linnean Society, 161, 105–121.</p> <p>Within the <i class="majorgroup">Angiosperms</i>, data quality varies widely reflecting the patchiness of the taxonomic and geographic coverage of the source databases. Coverage is believed to be most comprehensive and consistent for Monocotyledonen, where <cite>The Plant List</cite> benefited from the existence of comprehensive checklists fully reviewed by experts (see <a href="#wcs"><abbr title="World Checklist of Selected Plant Families">WCSP</abbr></a> and <a href="#grassbase">GrassBase</a>). For <i class="majorgroup">Angiosperms</i> other than Monocotyledons, expert-reviewed lists of similar quality provide comprehensive and consistent coverage for certain major families. Otherwise coverage is more patchy and likely to be less consistent as the name records have been assembled from <a href="#regional">regional lists</a> and/or other sources not fully reviewed by specialist systematists. Coverage is probably least reliable for areas for which regional lists were not available for incorporation, especially for South East Asia, and for genera with names ending with the letters H–Z (as genera beginning with the letters A–G benefited from earlier compilation effort as part of development of the World Checklist of Selected Plant Families).</p> <h3 id="gymnosperms">Gymnosperms</h3> <p><i class="majorgroup">Gymnosperms</i> — Conifers, Cycads, Ephedras, Gnetum, Ginkgo and <i class="genus">Welwitschia</i> (including Subclass <i class="subclass">Ginkgooidae</i> Engl; Subclass <i class="subclass">Cycadidae</i> Pax, Subclass <i class="subclass">Pinidae</i> Cronquist, Takht. & Zimmerm.; Subclass <i class="subclass">Gnetidae</i> Pax following Chase and Reveal, 2009)</p> <p><i class="majorgroup">Gymnosperms</i> records derive primarily from <a href="#wcs"><abbr title="World Checklist of Selected Plant Families">WCSP</abbr></a> and incorporate the <cite>2001 World Checklist of Conifers</cite> by A.Farjon. Coverage is thought to be comprehensive.</p> <h3 id="pteridophytes">Pteridophytes</h3> <p><i class="majorgroup">Pteridophytes</i> — ferns, horsetails and club mosses (including Subclass <i class="subclass">Equisetidae</i> Warm; Subclass <i class="subclass">Marattiidae</i> Klinge; Subclass <i class="subclass">Ophioglossidae</i> Klinge; Subclass <i class="subclass">Polypodiidae</i> Cronquist, Takht. & Zimmerm; Subclass <i class="subclass">Psilotidae</i> Reveal; Subclass <i class="subclass">Lycopodiidae</i> Beketov.)</p> <p>No peer-reviewed global lists of any family of ferns or other Pteridophyte has been incorporated. The data presented are compiled from regional and nomenclatural sources not reviewed by experts and are therefore likely to be less comprehensive and consistent than those for <i class="majorgroup">Angiosperms</i> and <i class="majorgroup">Gymnosperms</i>.</p> <h3 id="bryophytes">Bryophytes</h3> <p><i class="majorgroup">Bryophytes</i> — mosses, liverworts and hornworts (including Subclass <i class="subclass">Anthocerotidae</i> Engl.; Subclass <i class="subclass">Bryidae</i> Engl; Subclass <i class="subclass">Marchantiidae</i> Engl.)</p> <h2 id="nomenclatural-coverage">Nomenclatural coverage</h2> <p><cite>The Plant List</cite> aims to provide all the scientific names for species for these plant groups. A breakdown of the numbers of plants and names included in each plant group is provided, see <a href="/statistics/">Statistics</a>. Coverage of infraspecific taxa (subspecies, varieties, forms etc) is not comprehensive; they are included, primarily where they are synonyms or accepted names for species names.</p> <p>Coverage and data quality are primarily influenced by the <a href="#collaboraters">source data sets</a> used to build <cite>The Plant List</cite>. We are aware of additional data sets which, had they been included, would have enriched and improved the final product. We hope to include such data sets in later releases.</p> <h2 id="status">The Status of name records</h2> <p>Each name record included within <cite>The Plant List</cite> is assigned one of the statuses listed below. The Status of each name is derived primarily from the data source from which that name record comes (see <a href="#derivation">Derivation of Name Status</a>). The decision, for example, that one name is the accepted name of a given plant is based upon a taxonomic opinion recorded within the cited data source. Such decisions were automated using a rules-based approach which, where necessary, selected from among alternative taxonomic opinions expressed, within or between different data sources. For an explanation of how these decisions were reached see <a href="#created">How <cite>The Plant List</cite> was Created</a>.</p> <h3 id="accepted">Accepted Name</h3> <p>This is the name which should be used to refer to the species (or to a subspecies, variety or forma).</p> <p>For each name with Status of ‘Accepted’ <cite>The Plant List</cite> aims to provide:</p> <ul> <li>the name currently accepted as the one which should be used in preference to refer to this species (or subspecies, variety or forma);</li> <li>the author(s) credited with publishing that name;</li> <li>the place and date of original publication of the name where this was supplied;</li> <li>a reference to the source database supplying this name record that recorded the opinion that it is an accepted name (with, where possible, a link to that record in the source database);</li> <li> other names (synonyms) considered to refer to that species; </li> <li> the <a rel="external" href="http://www.ipni.org/about_the_index.html">IPNI</a> identifier (linking the name record to the International Plant Names Index, a bibliographic resource which will provide full original publication details for this name); </li> <li> an assessment of the <a href="#confidence">Confidence</a> that <cite>The Plant List</cite> attaches to the name being accepted. (This is an indication of the confidence that the Status of the name is correct). </li> </ul> <h3 id="synonym">Synonym</h3> <p>A Synonym is an alternative name which has been used to refer to a species (or to a subspecies, variety or forma) but which <cite>The Plant List</cite> does not consider to be the currently Accepted name. The decision to assign a Status of Synonym to a name record is based upon a taxonomic opinion recorded in the cited data source (selected using automated rules-based approach; see <a href="#created">How <cite>The Plant List</cite> was Created</a>).</p> <p>Synonymy can be derived directly from the source data (showing identical data as the source data) or can be derived indirectly using the automated <a href="#rules">decision rules</a> (e.g. if <em>source 1</em> says that <em>A</em> is a synonym of <em>B</em> and <em>source 2</em> says that <em>B</em> is a synonym of <em>C</em>, then <cite>The Plant List</cite> will show <em>A</em> to be a synonym of <em>C</em>).</p> <p>For each name with Status of Synonym <cite>The Plant List</cite> aims to provide:</p> <ul> <li>the name;</li> <li>the author(s) credited with publishing that name;</li> <li>the place and date of original publication of the name where this was supplied;</li> <li>a link to its Accepted name;</li> <li> a reference to the source database supplying this name record and expressing the opinion that it is a Synonym (with, where possible, a link to that record in the source database); </li> <li> the <a rel="external" href="http://www.ipni.org/about_the_index.html">IPNI</a> identifier (linking the name record to the International Plant Names Index, a bibliographic resource which will provide full original publication details for this name); </li> <li> an assessment of the <a href="#confidence">Confidence</a> that <cite>The Plant List</cite> attaches to the Status of the name being Synonym. </li> </ul> <h3 id="unresolved">Unresolved Name</h3> <p>Unresolved names are those to which it is not yet possible to assign a status of either ‘Accepted’ or ‘Synonym’. For an explanation of how names were assigned a status please refer to <a href="#created">How <cite>The Plant List</cite> was Created</a>. Unresolved names fall into two sub-classes:</p> <h4 id="unassessed">Unassessed names</h4> <p>for which there is no evidence within any of the contributing data sources that the status of this name had been evaluated by the data owners. None had recorded that it was either ‘accepted’ or a ‘synonym’. None had recorded that they had attempted such an evaluation. Since, by definition, a name is accepted by the publishing author at the time of publication, it could be argued that all names are putatively Accepted until such time as they are demonstrated to be Synonyms.</p> <h4 id="unplaced">Unplaced names</h4> <p>for which the data source supplying that record indicated positively that the data owners had sought to resolve its status and not been able to come to a conclusion so as to place it either in synonymy or as the accepted name of a new species. This is often the case if the name has insufficient description and no herbarium specimens are known.</p> <p>Among Unresolved names, Unassessed names are much more numerous than Unplaced names.</p> <p>It is also important to note that in a small number of cases the status ‘Unresolved’ was assigned to a name record during creation of <cite>The Plant List</cite> despite a taxonomic opinion having been recorded in the contributing data source. This occurs where to have followed this opinion would have conflicted with opinions recorded elsewhere in other data sources. To follow both would have resulted in inconsistencies within the working list of plants. In such cases:</p> <ul> <li>the status of the record on this website is indicated with an ‘<strong>*</strong>’ to indicate that it derives from the procedures used to build <cite>The Plant List</cite> and</li> <li>the original status of the name (as recorded in the source database) is indicated on the details page for that name.</li> </ul> <p>For each name with Status of ‘Unresolved’ <cite>The Plant List</cite> aims to provide:</p> <ul> <li>the name;</li> <li>the author(s) credited with publishing that name</li> <li>the place and date of original publication of the name where this was supplied;</li> <li>a reference crediting the source database providing the name; (with, where possible, a link to that record in the source database)</li> <li>the <a rel="external" href="http://www.ipni.org/about_the_index.html">IPNI</a> identifier (linking the name record to the International Plant Names Index which will provide full original publication details for this name); </li> <li>Unresolved names are generally flagged as ‘Low <a href="#confidence">Confidence</a>’ entries.</li> </ul> <h3 id="misapplied">Misapplied Names</h3> <p>Some data sets which contributed to <cite>The Plant List</cite> record not only how plant names <strong>should</strong> be used but also where in the published literature a given name may previously have been used inappropriately (to refer erroneously to another species). Recording such misapplication of names helps users to avoid pitfalls when interpreting the literature. The decision that a record establishes the misuse of a name is derived from the cited data source (see <a href="#created">How <cite>The Plant List</cite> was Created</a>.)</p> <p>For each reported misapplication of a plant name we aim to provide:</p> <ul> <li>the name;</li> <li> the author(s) that published that name and wherever possible an indication of where or by whom this was misused (e.g. ‘sensu Smith’ may appear after the publishing author);</li> <li> a link to the Accepted name of the species to which this name has been previously and erroneously applied;</li> <li> a reference crediting the source database recording this misuse of the name; (with a link to that record in the source database and hence the publication details of where this name was misapplied);</li> <li> an assessment of the <a href="#confidence">Confidence</a> that <cite>The Plant List</cite> attaches to this name having being erroneously applied to the other species.</li> </ul> <h2 id="annotation">Annotation of names</h2> <p>Sources which contributed name records to <cite>The Plant List</cite> record included, on relatively few occasions, additional information about individual names beyond their status as Accepted or Synonym. Where possible this information is retained within <cite>The Plant List</cite> and made visible to users as annotations attached to the relevant name record.</p> <h3 id="invalid"><span id="illegitimate">Invalid and Illegitimate Names</span></h3> <p>Some of the names in <cite>The Plant List</cite> were recorded by the contributing data sets to be either invalidly or illegitimately published according to the rules of the <a rel="external" href="http://ibot.sav.sk/icbn/main.htm">International Code of Botanical Nomenclature</a>.</p> <h3 id="orthographic">Spelling variants (or Orthographic variants)</h3> <p>Some data sources include names which are recorded as ‘Orthographic variants’ (or spelling variants) of another name. These misspelt names may not have been validly published and yet are nevertheless used in the literature and therefore included in <cite>The Plant List</cite> to guide those that find them.</p> <h2 id="confidence">Confidence Levels</h2> <p>For each name record <cite>The Plant List</cite> offers an indication of the confidence that the <a href="#status">Status</a> of the name record is correct: Our confidence assessments are based primarily on the nature and taxonomic integrity of the source data.</p> <h3 id="high"><img src="/img/H.png" alt=""/> High Confidence level</h3> <p>is applied to the <a href="#status">Status</a> of name records derived from taxonomic datasets which treat the whole of the taxonomic group in question on a global basis and have been peer reviewed (e.g. ILDIS, WCSP, see <a href="#collaborators">collaborators</a>).</p> <h3 id="medium"><img src="/img/M.png" alt=""> Medium Confidence level</h3> <p>is applied to the <a href="#status">Status</a> of name records derived from:</p> <ul> <li><strong>Either</strong> national or regional databases via a rules-based automated process, reflecting the challenges inherent in resolving taxonomic differences between different name data sets for the same species for different geographic areas. Regional datasets used as sources for <cite>The Plant List</cite> are primarily those stored within Tropicos (see <a href="#collaborators">collaborators</a> for details).</li> <li><strong>Or</strong> taxonomic datasets which treat the whole of the taxonomic group in question on a global basis but which have not yet undergone peer review (e.g. GCC and WCSP (in review) see <a href="#collaborators">Collaborators</a>).</li> </ul> <h3 id="low"><img src="/img/L.png" alt=""/> Low Confidence level</h3> <p>is applied to the <a href="#status">Status</a> of name records derived from</p> <ul> <li>any of the contributing data sets which were recorded as unresolved in those data sets.</li> <li>to name records whose status has been inferred from (sometimes conflicting) information from more than one source database.</li> <li>to records derived from nomenclatural resources such as IPNI which do not contain opinions about the status of the name and which were assigned a status of Unresolved in <cite>The Plant List</cite>.</li> </ul> </section> <section> <h1 id="collaborators">Contributing data sets</h1> <p>The data resources used to build Version 1 of <cite>The Plant List</cite> are listed here and we are grateful to the many collaborators listed below that made their data available.</p> <p>We welcome offers of additional data sets for inclusion in the future editions of <cite>The Plant List</cite> (see <a href="/feedback/#contribute">Contributions</a>).</p> <h2 id="globalspeciesresources">Global species resources</h2> <ul> <li> <h4 id="wcsp">World Checklist of Selected Plant Families</h4> <p> This large database of global monographic treatments was supplied to <cite>The Plant List</cite> as two separate data sets which were treated slightly differently:</p> <ol> <li> <h5 id="wcs"><a rel="external" href="http://www.kew.org/wcsp/">WCSP</a></h5> <p>Peer reviewed treatments are available online for 151 Seed Plant families (<a rel="external" href="http://apps.kew.org/wcsp/incfamilies.do">view published families</a>). WCSP gives information on the accepted scientific names and synonyms of selected plant families. It includes more than 320,000 names and allows the user to search for all the scientific names of a particular plant, or the areas of the world in which it grows (distribution). The data set counts upon the collaboration over 16 years of 132 specialists from 25 countries who have contributed data or acted as <a rel="external" href="http://www.kew.org/wcsp/compilersReviewers.do">reviewers</a>. </p> </li> <li> <h5 id="wcsir">WCSP (in review)</h5> <p> In addition to the published family checklists the World Checklist database contains data for many other families which have either been completed and await review by specialists or are still being compiled. <cite>The Plant List</cite> also incorporates these unpublished data which include more than 290,000 additional names. </p> </li> </ol> </li> <li> <h4 id="grassbase"><a rel="external" href="http://www.kew.org/data/grasses-syn/">GrassBase – The Online World Grass Flora</a></h4> <p> The nomenclatural component of this database currently holds over 60,000 names and lists names for any given genus, geographical region or genus within a geographical region; and links to the GrassBase description for any species. The nomenclatural data from GrassBase is made available through the <a href="#wcs">WCSP system</a>. </p> </li> <li> <h4 id="gcc"><a rel="external" href="http://www.compositae.org/checklist/">The Global Compositae Checklist</a></h4> <p> is an integrated database of nomenclatural and taxonomic information for the second largest vascular plant family in the world. This checklist is published by the <a rel="external" href="http://www.compositae.org/">International Compositae Alliance</a> and compiled from many contributed datasets. The <a rel="external" href="http://www.compositae.org/checklist/">database</a> will be continually updated. Additional information such as references, distribution and infraspecific taxa are available on the website. All species are marked as ‘provisionally accepted names’ in the Beta version. The data set has not yet been fully peer-reviewed and may contain some errors. More than 100,000 records derived from The Global Compositae Checklist are included in <cite>The Plant List</cite>. </p> </li> <li> <h4 id="ildis"><a rel="external" href="http://www.ildis.org/">The International Legume Database and Information Service</a></h4> <p> is a long-term programme of co-operation among legume specialists worldwide to create a biodiversity database for the <i class="family">Leguminosae</i> (<i class="family">Fabaceae</i>) family. The database provides a taxonomic checklist plus basic factual data on distribution, common names, life-forms, uses, literature references to descriptions, illustrations and maps. More than 40,000 records derived from ILDIS are included in <cite>The Plant List</cite>. </p> </li> <li> <h4 id="iplants"><a rel="external" href="http://www.iplants.org/">The iPlants project</a></h4> <p> developed and tested the processes and procedures that would be required during production of an authoritative, global online list of plant names. The project was a collaboration between The <a rel="external" href="http://www.kew.org/">Royal Botanic Gardens, Kew</a>, the <a rel="external" href="http://www.mobot.org/">Missouri Botanical Garden</a> and the <a rel="external" href="http://www.nybg.org/">New York Botanical Garden</a> and was funded from April 2004 to May 2006 by the Gordon and Betty Moore Foundation. Checklists for the following families were made available for <cite>The Plant List</cite>: <i class="family">Bignoniaceae</i>, <i class="family">Iridaceae</i>, <i class="family">Lecythidaceae</i>, <i class="family">Melanophyllaceae</i>, <i class="family">Physenaceae</i>, <i class="family">Sarcolaenaceae</i>, <i class="family">Schlegeliaceae</i> and <i class="family">Sphaerosepalaceae</i>. More than 11,000 records derived from iPlants are included in <cite>The Plant List</cite>. </p> </li> <li> <h4 id="iopi"><a rel="external" href="http://www.iopi.org/">The International Organization for Plant Information</a></h4> <p> aims to provide a series of computerised databases summarizing taxonomic, biological, and other information on plants of the world. IOPI’s mission is to develop an efficient and effective means of providing basic plant information to users, and guide them toward sources of authoritative data. Their checklist currently holds over 200,000 names from which <cite>The Plant List</cite> includes records for <i class="family">Juncaceae</i> compiled by J. Kirschner (Institute of Botany, Pruhonice) (Over 1,000 name records). </p> </li> <li> <h4 id="tropicos-bryophyte"><a rel="external" href="http://www.mobot.org/">Missouri Botanical Gardens</a></h4> <p>The Bryophyte information was primarily gathered from <a rel="external" href="http://www.mobot.org/MOBOT/tropicos/most/checklist.shtml"><cite>A Checklist of Mosses</cite></a> and ongoing projects dealing with mosses and liverworts to create World Checklists for these groups. Some liverwort names were not yet available from data sources but are expected to be added in future versions. </p> </li> </ul> <h2 id="regional">Floristic Datasets</h2> <ul> <li> <h4 id="tropicos"><a rel="external" href="http://www.mobot.org/">Missouri Botanical Gardens</a></h4> <p> the botanical information system at the Missouri Botanical Garden, <a rel="external" href="http://www.tropicos.org/">Tropicos</a> contains information on over one million plant names and 3.9 million herbarium specimens. The system was developed through the actions of a wide variety of floristic, nomenclatural, and bibliographic projects both at the Garden and in collaboration with other institutions. All of this information is available on the Internet through the Garden’s web site. </p> <p>Tropicos provides access to the accumulated data on vascular plant and bryophyte as authority files for the development of floras and checklists that provide synthesis of local and regional vegetation. Included within each of these syntheses are indications of acceptance, synonymy and misapplication of names within a floristic region. This information was used to evaluate plant names from these regions for <cite>The Plant List</cite>. </p> <p>The project data held by Tropicos and used in the development of <cite>The Plant List</cite> includes:</p> <ul> <li><a rel="external" href="http://www.tropicos.org/Project/FM">Flora Mesoamericana</a></li> <li><a rel="external" href="http://www.tropicos.org/Project/FC">Flora of China Checklist</a></li> <li><a rel="external" href="http://www.tropicos.org/Project/BC">Checklist of Bolivia</a></li> <li><a rel="external" href="http://www.tropicos.org/Project/CE">Checklist of Ecuador</a></li> <li><a rel="external" href="http://www.tropicos.org/Project/PEC">Checklist of Peru</a></li> <li><a rel="external" href="http://www.tropicos.org/Project/PAC">Checklist of Panama</a></li> </ul> <p> Information was also gleaned from recent published literature when the acceptance or synonyms have been recorded in Tropicos. </p> <p> More than 240,000 records derived from Tropicos were included in <cite>The Plant List</cite>. </p> </li> <li> <h4 id="madagascan">Madagascan endemics</h4> <p>The <a rel="external" href="http://www.iplants.org/">iPlants project</a> also provided a checklist for Madagascan endemics.</p> </li> </ul> <h2 id="nomenclatural">Plant nomenclatural resources</h2> <ul> <li> <h4 id="ipni"><a rel="external" href="http://www.ipni.org/">The International Plant Names Index</a></h4> <p> is a database of the names and associated basic bibliographical details of seed plants, ferns and fern allies. Its goal is to eliminate the need for repeated reference to primary sources for basic bibliographic information about plant names. The data are freely available and are gradually being standardised and checked. IPNI will be a dynamic resource, depending on direct contributions by all members of the botanical community. IPNI is the product of a collaboration between the <a rel="external" href="http://www.kew.org/">Royal Botanic Gardens, Kew</a>, the <a rel="external" href="http://www.huh.harvard.edu/">Harvard University Herbaria,</a> and the <a rel="external" href="http://www.anbg.gov.au/cpbr/herbarium/">Australian National Herbarium</a>. </p> </li> <li> <h4 id="kew-uncompiled">Uncompiled name data records derived from Kew’s checklist databases.</h4> </li> <li> <h4 id="tropicos-uncompiled">Uncompiled name data records from Missouri’s Tropicos database.</h4> </li> </ul> </section> <section> <h1 id="created">How <cite>The Plant List</cite> was Created</h1> <p>Development of <cite>The Plant List</cite> has been a collaborative venture coordinated at the Royal Botanic Gardens, Kew and Missouri Botanical Garden and relying on the generosity of many <a href="#collaborators">collaborators</a> who manage significant taxonomic data resources. The purpose was to merge into a single consistent database the best of the nomenclatural information available in these diverse data resources through a defined and automated process. In summary, development of <cite>The Plant List</cite> involved merging many taxonomic data sources taking the accepted name and synonymy relationships from those that were global checklist datasets, augmenting these and adding additional names and synonymy relationships from regional and national floristic datasets following a set of <a href="#rules">decision rules</a>. Species names not accounted for in any of the previously incorporated data sets are added from nomenclatural resources, ensuring the list is comprehensive for all plant names. Finally a further set of rules are applied to the final data set to resolve inconsistencies, conflicting or overlapping statuses and to correct logical data errors. </p> <h2 id="merging">The Sequence for Merging Data Sets</h2> <p> The starting point was the set of global peer reviewed family checklists published within the <a href="#wcs">World Checklist of Selected Plant Families (WCSP)</a>. Families available through the WCSP from other sources including <a href="#grassbase">GrassBase</a>, <a href="#iplants">iPlants</a> (<i class="family">Bignoniaceae</i>, <i class="family">Iridaceae</i>, <i class="family">Lecythidaceae</i>, <i class="family">Melanophyllaceae</i>, <i class="family">Physenaceae</i>, <i class="family">Sarcolaenaceae</i>, <i class="family">Schlegeliaceae</i> and <i class="family">Sphaerosepalaceae</i>) and <a href="#iopi">IOPI</a> (<i class="family">Juncaceae</i>) were also included. To these were added additional global checklists from collaborating partners: The <a href="#gcc">Global Compositae Checklist</a> from the International Compositae Alliance and <a href="#ildis">The International Legume Database and Information Service</a> Also incorporated were all of the compiled WCSP data records for families other than those which have been published (i.e. are in the process of being compiled or are under peer review): <a href="#wcsir">WCSP (in review)</a>. </p> <p> The second category of information sources was various national and regional checklists. Missouri Botanical Garden’s <a href="#tropicos">Tropicos</a> system, primarily provided data from nearly ten digital flora projects. Each of these national or regional floras or checklists was created at a different time by a different team of botanists and considers only plant specimens found within that area’s borders. Thus these floras/checklists contain different subsets of plants (and plant names) and record conflicting opinions as to which are the accepted names for particular plants or what are their synonyms. In building <cite>The Plant List</cite>, therefore, a significant task was to automate procedures to trawl each of these different data sets to locate new information that they might contain about names and synonymy, then to detect and resolve conflicting opinions among these data sets and to add this additional information to the merged data set. A set of <a href="#rules">decision rules</a> was employed to differentiate between and select from among the diverse opinions expressed within these national and regional data sets. </p> <p> Finally, there were many scientific plant names (recorded in <a href="#ipni">IPNI</a> or included in <a href="#tropicos-uncompiled">Tropicos</a> or <a href="#kew-uncompiled">WCSP</a> as uncompiled records) that had not been included in any of the data sets consulted up to that point. The combined set of global and regional data were therefore compared with the IPNI database to detect missing from our merged data set so that they could be added to our final product. Names derived IPNI (and other nomenclatural data sets consulted) were included as ‘<a href="#unresolved">Unresolved</a>’, since data was not recorded in these data sets asserting whether these were the Accepted name for a new plant (not yet in the merged data set) or whether they were Synonyms of plants already in the merged list. </p> <p> A significant component of this and later phases of the creation of <cite>The Plant List</cite> involved the matching of names between different data sets to identify whether a name was unique to one data set or included in multiple data sets. A variety of algorithms were employed to perform name matching at different stages depending upon the requirements at that stage in the process. </p> <h2 id="derivation">Derivation of Name Status</h2> <p> The procedures used to build <cite>The Plant List</cite> were designed to follow the taxonomic opinions recorded within the contributing data sets. Where necessary these procedures selected from among alternative and conflicting opinions recorded between data sets so as to achieve a coherent taxonomic consensus. </p> <p> Consistent application of the decision rules allowed resolution of most instances of conflicts between data sources so that most species names can be clearly established as either an accepted name or as a synonym with reference to the data source in which that status is recorded. It is important to note that the set of synonyms which point to a given accepted name in <cite>The Plant List</cite> may have originated from more than one data source i.e. some synonyms for a given species may derive from a data set other than that from which the accepted name record derived. </p> <p> Approximately 98% of all <a href="#status">Status</a> values within <cite>The Plant List</cite> derive directly from the data source which supplied that name record. </p> <p> The Status of the remaining 2% of name records in <cite>The Plant List</cite> has been modified from that stored in the source data set as a result of the conflict resolution processes. Such changes were made only where necessary to avoid illogical conflicts detected within the data sets supplied or within the merged data set (i.e. were made to improve the consistency of <cite>The Plant List</cite>). Where such changes were made, these were primarily to downgrade name records recorded as having a status of ‘Accepted’ in the source database to having a status of ‘Unresolved’ in <cite>The Plant List</cite>. </p> <p> Any name records whose status was modified during the creation of <cite>The Plant List</cite> are labelled (using an asterisk) and the original status in the data source also indicated. The Confidence level of any record modified by these procedures was set to ‘Low Confidence’. </p> <h2 id="rules">Decision Rules to arbitrate between Conflicts of Opinion</h2> <p> A set of decision rules were employed to differentiate between and select from among diverse opinions expressed within all of the data sources consulted. These rules were developed by the team at Kew and Missouri in an attempt to mimic the sort of decision-making rationale a botanist might use in a situation where he/she encounters conflict between taxonomic treatments in the literature but is not in a position to resolve the question by examining the original material. For example: </p> <ul> <li> monographic treatments which consider the group in question in its entirety throughout its distribution are given priority over geographically defined treatments which can result in a single species being treated under different names in different parts of its range; </li> <li> synonym relationships reported in more recent treatments are given priority over those published earlier; </li> <li> publication dates are used to assist in detecting likely illegitimate names; </li> <li> author details are used to detect likely orthographic variants (alternative spellings of the same name); </li> <li> the decision rules are informed by the principles embedded in the International Code of Botanical Nomenclature. </li> </ul> <h2 id="analysis">Data analysis of logical inconsistencies and data integrity issues</h2> <p> The data set created by merging records from the various data sources as described above was found initially to be inconsistent and logically incongruous for a variety of reasons. </p> <p> Each of the taxonomic data sets incorporated into <cite>The Plant List</cite> are themselves still being developed and improved upon by their owners and editors. None therefore can be considered to be complete or entirely up to date. Nor would their owners claim that these data sets were free of inconsistencies, gaps or data error. Furthermore these databases use terminology in different ways which necessitated some level of standardisation. Some contained fossil plant names or names of taxonomic ranks that are not intended to be included in <cite>The Plant List</cite> and yet which, nevertheless, might link to names in the merged data set. Careful filtering of the record set was needed. </p> <p> Inevitably, the process of bringing many different data sets together added a layer of further complexity. Thus for example it is not straightforward to automate recognition of a particular Latin binomial reliably within different data sets given that the plant name authors may have been cited or abbreviated differently, subtle differences in spelling and punctuation occur between the data sources and not all of them included the place of publication of a name to help resolve suspected matches. This added a degree of uncertainty even before other complexities such as those surrounding homonyms and misapplied use were dealt with. As a result certain circumstances in the procedures created a merged data set in which a few names were used inconsistently based upon records derived from different sources. </p> <p> The goal of <cite>The Plant List</cite> project is to create a single internally coherent view rather than a set of alternative views. The final stage of development of <cite>The Plant List</cite> therefore involved rigorous logical analysis of the data set. Steps were taken, for example, to identify likely duplicates used in different senses, to detect where a number of Synonyms link one to another but lack any link to an Accepted name, where illegitimate names are assigned Accepted status or where a subspecies included in the dataset occurs within a species which itself does not occur. </p> <h2 id="resolution">Resolution of logical inconsistencies and data integrity issues</h2> <p> For each different data inconsistency detected solutions were derived based upon the concepts and principles as outlined above and used in the previous stages. Additional decision rules were created and new automated steps introduced to perform the following actions on the merged data set:</p> <ol> <li>Standardisation of terminology</li> <li>Standardisation, Selection and Filtering of name records</li> <li>Deduplication of names</li> <li>Resolving referential integrity regarding linkages among synonyms.</li> <li>Resolving referential integrity regarding taxonomic relationships.</li> <li> Standardisation of the names of Families and Major Groups so as to create the taxonomic hierarchy necessary to support browsing of <cite>The Plant List</cite>. </li> </ol> <h2 id="publication">Online Publication of The Plant List</h2> <p> Target 1 of the GSPC was to achieve a "widely accessible" working list of all known plant species. To accomplish that aspect of Target 1, this website was created to enable world-wide access to the working list. The final merged and resolved data set of all plant species is accessible through the search and browse features offered here. </p> <h2 id="nextsteps">Next Steps</h2> <p> As a result of the data analysis and conflict resolution steps described above it is now intended to provide detailed feedback to each of the collaborators that contributed datasets on providing them with enriched data records, information on inconsistencies detected and comparisons with other relevant data sets. Details of the data processing entailed in creating <cite>The Plant List</cite> are to be published for broader discussion. Interest in the process and suggestions for refinements to the decision rules are welcome.</p> </section> <section> <h1 id="team">The project team</h1> <p> <cite>The Plant List</cite> owes its origins to a three-day workshop at Missouri Botanical Garden in May 2008. Bob Allkin, Eimear Nic Lughadha and Alan Paton (Kew) joined Bob Magill and Chuck Miller (MO) to plan how existing resources could best be combined to produce a best efforts working list to meet the 2010 deadline. The principles underlying our approach were agreed at that time, along with many of the decision rules and initial drafts of workflows for the data processing required. Translating that initial plan into action and refining the process to improve the product involved many more people over many months, with datasets, e-mails and occasionally people moving back and forward between Kew and St Louis. </p> <h2 id="kew-team">Contributors working at Kew</h2> <ul> <li>Bob Allkin – Project Manager</li> <li>Abigail Barker – Applications Development Manager</li> <li>Matthew Blissett – Lead Developer Web Application</li> <li>Charlotte Couch – Support Families and Genera Index</li> <li>Paramjit Dhaliwal – IT Operations team</li> <li>Jeff Eden – Graphic Designer</li> <li>Rafaël Govaerts – Editor of the World Checklist of Selected Plant Families</li> <li>Graham Hawkes – Developer responsible for <cite>The Plant List</cite> data and procedures</li> <li>Chris Hopkins – Developer Web Application</li> <li>Eimear Nic Lughadha – Senior Responsible Owner</li> <li>Nicky Nicolson – Developer responsible for IPNI</li> <li>Alan Paton – Assistant Keeper, Herbarium</li> <li>John Stone – Graphic Designer</li> <li>Julius Welby – Data administration</li> <li>Ian Wright – IT Operations team leader</li> </ul> <h2 id="missouri-team">Contributors working at Missouri</h2> <ul> <li>Bob Magill – Senior Vice President of Science & Conservation</li> <li>Chuck Miller – Vice President of Information Technology</li> <li>Chris Freeland – Director of Center for Biodiversity Informatics</li> <li>Jay Paige – Application and Database Developer</li> <li>Heather Stimmel – Application and Database Developer</li> <li>Craig Geil – Application and Database Developer</li> </ul> </section> <section> <h1 id="enhancing">Enhancing <cite>The Plant List</cite></h1> <p> In the future we envisage producing subsequent versions of <cite>The Plant List</cite> at regular intervals. Subsequent versions could: </p> <ol> <li> merge improved and extended versions of the data sets used to create Version 1. As the custodians of the source datasets enhance their data sets through their own planned additions and corrections, their improvements will feed into subsequent versions of <cite>The Plant List</cite>. We are committed to supplying feedback to the owners of each data set as this arises from the use and creation of <cite>The Plant List</cite> </li> <li> include additional data sets which were unavailable in Version 1. If you are interested in making a future <a href="/feedback/#contribute">contribution,</a> please contact <a href="mailto:contributors@theplantlist.org">contributors@theplantlist.org</a>. </li> <li> reflect enhancements in the procedures that were used to create <cite>The Plant List</cite>: e.g for locating duplicate name records, for resolving inconsistencies and for detecting conflicting opinions expressed within alternative data sets and then for selecting from among those opinions (see <a href="#created">How <cite>The Plant List</cite> was created</a>). </li> </ol> <p>Our immediate priorities following the December 2010 launch are to:</p> <ul> <li>provide feedback to the collaborators who contributed datasets</li> <li>complete documentation of the decision rules for publication</li> <li>plan future versions of <cite>The Plant List</cite></li> </ul> <p>Likely priorities for future work include:</p> <ul> <li>increasing the number of data contributors — especially for South East Asia which is poorly represented in Version 1</li> <li>adding links to country level geography</li> <li>providing unique identifiers.</li> </ul> </section> <section> <h1 id="relationships">Relationships to other resources</h1> <p> Of the data resources that were used to create <cite>The Plant List</cite> many of the previously published global monographic datasets are also available through the Catalogue of Life which provides peer reviewed information for many plant families. </p> <p> <cite>The Plant List</cite> goes beyond the scope of Catalogue of Life by also including global treatments which are in peer review or have not yet been published and by seeking to complete the list of all species names by filling the gaps using further digital resources including regional and national floras and nomenclatural databases. <cite>The Plant List</cite> thus aims to be comprehensive in coverage at species level for all names of mosses and liverworts, flowering plants, conifers, cycads and their allies and the ferns and their allies. It is nevertheless a work in progress. The <a href="#confidence">Confidence</a> in the <a href="#status">Status</a> assigned each name records is indicated.</p> </section> </div> </div> <footer> <p> © The Plant List 2010 — <a rel="license" href="/terms/">Terms and Conditions</a> — <a href="/cite/">How to Cite</a> </p> </footer> <script type="text/javascript" src="http://include.reinvigorate.net/re_.js"></script> <script type="text/javascript"> try { reinvigorate.track("qqd10-7tcw301jmk"); } catch(err) {} </script> </body> </html>