Showing posts with label PhyloCode. Show all posts
Showing posts with label PhyloCode. Show all posts

18 October 2013

The PhyloCode Has a Deadline

As most of you probably know, the PhyloCode (more verbosely, the International Code of Phylogenetic Nomenclature)  is a proposed nomenclatural code, intended as an alternative to the rank-based codes. It was first drafted in April 2000, and at that time the starting date was given as "1 January 200n". On this date the code would be enacted and published along with a companion volume, which would provide the first definitions under the code, establishing best practices and defining the most commonly-used clade names across all fields of biology.


Well, the '00s (the zeroes? the aughts?) came and went without the code being enacted. The hold-up was not the code itself, which has been at least close to its final form since 2007. (The last revision, in January 2010, was minor.) And it hasn't been the software for the registration database, which has been completed. The hold-up was the companion volume, which turned out to be a much more daunting project than expected. (And considering that the zoological code took 66 years to go from being proposed to being published, perhaps the initial estimate should have been hedged, anyway.)

At the 2008 meeting of the International Society for Phylogenetic Nomenclature (ISPN), this problem was discussed. It was decided that the companion volume should be narrowed in scope. Instead of waiting to get definitions for commonly-used clade names across all fields of biology (many of which did not even have willing authors), entries would be limited to those already in progress. Later on, a revision was also made to the editorial process to help speed things up.

Now for some news: at the website for the ISPN (recently revamped by yrs trly), there is a new progress report for Phylonyms, the companion volume to the PhyloCode. There will be at most 268 entries. Currently 186 of those (over two thirds) have already been accepted. The rest are at various stages of review. But perhaps most excitingly, there is a deadline:
The contract with University of California Press calls for the manuscript to be submitted by September 1, 2014.
 Yes, folks, we will see the PhyloCode enacted in our lifetime! (Pending nuclear holocaust or alien invasion.)

02 May 2012

The PhyloCode Will Not Be Amended

At least for now.


In a 10-1 decision, the Committee on Phylogenetic Nomenclature voted to reject the wholesale adoption of a proposal to amend the PhyloCode that would have greatly changed how it handles species and species names. However, the CPN has decided to discuss the possibility of using some ideas in the proposal.

27 February 2012

What Is Phylogenetic Nomenclature?

Sometimes when discussing the PhyloCode, I get the feeling a lot of potentially interested parties don't understand what phylogenetic nomenclature actually is. I have gone into excruciating detail on this topic elsewhere, but who wants to be excruciated? So here's a brief summary of the process of creating a phylogenetic taxonomy.

1. Declare Operational Taxonomic Units
Result: Alpha Taxonomy

The very first step is to decide what your units are. Are you dealing with individual organisms? Populations? Species? Which ones? Whatever you select, there should be an unambiguous way of referring to these taxonomic units (specimen numbers, species names, etc.).

Phylogenetic nomenclature is flexible as to how you determine and name taxonomic units. (Although the names must be relateable to those used in definitions [see Step 3].)

Example: My operational taxonomic units are the whale species Aetiocetus cotylalveusBalaena mysticetus, Balaenoptera physalus, Delphinus delphis, and Monodon monoceros.

Operational Taxonomic Units
Silhouettes by Chris huh and T. Michael Keesey, taken from PhyloPic.
Image license: CC-BY-SA 3.0

15 February 2012

Amending the PhyloCode: The Species Problem

Earlier I mentioned a proposal by Cellinese, Baum, and Mishler to make a major revision to the PhyloCode, removing pretty much all mention of "species". In this post I'm going to take a high-level look at some of the proposed changes.

16 January 2012

A Proposal to Amend the PhyloCode


The draft PhyloCode has been in a pretty stable form for a while. But recently, there has been a proposal to drastically change how it handles species. You can read the proposal here: 



The first paragraph:

The overarching goal of this proposal is to remove all mention of "species" from the  PhyloCode. Detailed justifications for this goal are given in a supporting paper (Cellinese, Baum, and Mishler, in review); here we present a summary of the main arguments, along with specific proposals for change.

Before I weigh in on this, I'm curious as to what other people think. Please comment below, or send comments to David Marjanović, the Secretary of the Committee on Phylogenetic Nomenclature.

UPDATE:
If anyone would like a Microsoft Word version of this document, just ask.

ANOTHER UPDATE:
I have weighed in.

17 August 2010

An Example of Why We Need the PhyloCode

I just ran Radish on Zea mays (maize, a.k.a. corn). Look what the combined taxonomies from uBio look like:


What a mess! Keep in mind that the multiplicity of paths is not due to differing phylogenies (they all seem to agree on that), but to differing nomenclature. Even if uBio were to add some of the more obvious synonymies (e.g., Embryophyta and "Embryophytes"), it'd still be pretty wild.

Eventually I plan to have Radish work with automatically-generated taxonomies, made by placing PhyloCode names (from RegNum) onto TreeBase phylogenies using Names on Nodes algorithms, but until then I guess this is the best option.

And Zea mays is just a particularly egregious example. In contrast, here's a nice, neat "radish" for Scarabaeus sacer:


Apart from the one errant use of Animalia, pretty nice!

01 March 2010

The Great PhyloCode Land Run

Sometime in the near future, the PhyloCode will be enacted. For this to happen, two things need to happen concurrently:

1. The registration database (called "RegNum") must be completed and opened to the public. This is necessary because the PhyloCode requires all names to be registered electronically.

2. Phylonyms: a Companion to the PhyloCode must be published. This is a multi-authored volume that will include the earliest definitions under the PhyloCode.

Which names will be defined in Phylonyms? The original goal was to cover the most historically important names (what Alain Dubois calls "sozonyms"). However, proponents of phylogenetic nomenclature tend to be clustered in several fields (most notably vascular plant botany and vertebrate zoology—note that the code's authorship reflects this). This means certain parts of the Tree of Life (e.g., entomology) will unfortunately be underrepresented, due to lack of interest in those fields. (The alternative, having non-specialists define such names in Phylonyms, does not bear consideration.) So Phylonyms will be less about providing coverage and more about providing sturdy, well-reasoned definitions that can serve as examples.

What about all the names that it omits? What will happen to those once the PhyloCode is enacted? That will be interesting to see.


One thing I could envision is a sort of "land run". I picture it working this way. Let's consider a field, say, anthropology, where phylogenetic nomenclature has not taken much of a hold. Currently there is debate about how to use some taxonomic names related to the field. Some workers like to use the familial name "Hominidae" to refer to a large taxon, including humans and great apes. Others prefer to restrict it to the human total clade (i.e., humans and everything closer to them than to other extant taxa). Similarly, some workers use the generic name "Homo" in a broad sense to include short, small-brained species like Homo habilis, while others prefer to restrict it to the tall, large-brained clade (relegating H. habilis to another genus, e.g., Australopithecus).

Let's say there's a researcher out there named Dr. Statler, who prefers a strict usage for "Hominidae" and a broad use for "Homo". But his colleague, Dr. Waldorf, prefers a broad usage for "Hominidae". Dr. Waldorf isn't really that interested in phylogenetic nomenclature, but when he notes that "Hominidae" is not in the registration database, he sees an opportunity. He writes a quick paper defining "Hominidae" as a node-based clade: "The clade originating with the last common ancestor of humans (Homo sapiens Linnaeus 1758), Bornean orangutans (Pongo pygmaeus Linnaeus 1760), common chimpanzees (Pan troglodytes Oken 1816, originally Simia troglodytes Blumenbach 1775), and western gorillas (Gorilla gorilla Geoffroy 1852, originally Troglodytes gorilla Savage 1847)."

Dr. Statler is, of course, outraged. Not that he cares that much about phylogenetic nomenclature, but what if anthropologists do start using it? What if someone ruins another taxonomic name? His colleagues Drs. Honeydew and Beaker prefer a strict definition of "Homo"—what if they author a paper cementing that definition under the PhyloCode?

This cannot come to pass! Dr. Statler does some reading on the code and decides that a branch-based definition would work nicely for his broader usage. He defines "Homo" as, "The clade consisting of Homo sapiens Linnaeus 1758 and all organisms that share a more recent common ancestor with H. sapiens than with Australopithecus africanus Dart 1925, Paranthropus robustus Broom 1938, Zinjanthropus boisei Leakey 1959, or Australopithecus afarensis Johanson & White 1978." This sets off another anthropologist, and soon all sorts of anthropological/primatological names are being defined under the PhyloCode, as workers struggle to assert their usages.




This is not an ideal situation. It would be much nicer if a group of anthropologists were to come together, discuss the matters rationally, and arrive at an agreement which they then publish together. But it's still not a horrible situation—at least people are defining phylogenetic names and at least interest in phylogenetic nomenclature is being spread. I can't predict the future, but I feel like this sort of "land run" is bound to occur at least in some fields—and maybe that's okay.

23 February 2009

Brand New Forum for Discussion of Phylogenetic Nomenclature

The title says it all. As some of you may know, the ISPN's online forum has been down for a while. Daniel Madzia, of Wild Prehistory, has taken it upon himself to create a new forum: PhyloNom.


We've started a few threads. If you are interested in biological nomenclature, come on over and check it out!

12 February 2009

Extinct or Extant?

It's pretty easy to tell whether something's alive, right? You might have to jab it with a stick a couple of times to make sure (assuming it's an animal), but generally it's not too hard. So you'd think.

The International Union for Conservation of Nature is devoted to the preservation of life's diversity, so, naturally, it has a big stake in this question. When should we expend energy to try to save a critically endangered species, and when should we throw in the towel? Their Red List Guidelines say this about extinction:
Extinction is defined as population size reaching zero.
That made me laugh when I first read it. Really? You don't say! But I read on, and it became clear that there was much more to this seemingly simple definition:
Population size is the number of all individuals of the taxon (not only mature individuals). In some cases, extinction can be defined as population size reaching a number larger than zero. For example, if only females are modelled, it is prudent to define extinction as one female (instead of zero) remaining in the population. More generally, an extinction threshold greater than zero is justified if factors that were not incorporated into the analysis due to a lack of information (for example, Allee effects, sex structure, genetics, or social interactions) make the predictions of the analysis at low population sizes unreliable.

For Criterion E, extinction risk must be calculated for up to 3 different time periods:
  • 10 years or 3 generations, whichever is longer (up to a maximum of 100 years)
  • 20 years or 5 generations, whichever is longer (up to a maximum of 100 years)
  • 100 years
For a taxon with a generation length of 34 years or longer, only one assessment for 100 years) is needed. For a taxon with a generation length of 20 to 33 years, two assessments (for 3 generations and 100 years) are needed. For a taxon with a generation length less than 20 years, all three assessments are needed.
This is just a small sample of what the IUCN has to say on the subject. So much for just poking things with sticks.

It would be nice if we could simply categorize species as extinct or extant, but it's not always easy. A species may be extant one day and extinct the next. And we may not realize this until years or even decades later. Or, we may think a species extinct only to have individuals turn up again, as may have happened with Campephilus principalis, the ivory-billed woodpecker, a few years ago (Hill et al. 2006).

This question is important not only for conservation efforts, but also for nomenclature. In fact, in some ways, the issues become even thornier for nomenclature. To see why this is so, let's look at the phylogenies of two mammalian taxa.

Whales

Whales, or cetaceans, are related to even-toed ungulates, or artiodactyls. (In fact, they may even be artiodactyls, but that's a discussion that I'm going to try to avoid as much as possible right now.) The chart below shows a sampling of fossil and living species, giving a very rough and highly abridged picture of cetacean evolution:

Time goes from left to right. Arrows point from ancestor species to descendant species. Silhouettes are not to scale.

Cetacea is what we call a "crown group". A crown group is a special type of clade, a clade being an ancestor and all of its descendants. A crown group is the final common ancestor of certain extant organisms, and all descendants of that ancestor. Note that this doesn't mean that all members of a crown group are extant; for example, Aetiocetus, a proto-baleen whale known from fossils, is long extinct. But it is descended from the final common ancestor of living baleen whales (Mysticeti) and living toothed whales (Odontoceti), so it is still a member of the crown group Cetacea.

The cetacean "total group", informally termed "pan-Cetacea", includes everything sharing closer ancestry with cetaceans than with any other extant organisms. A number of extinct taxa, from Pakicetus to Dorudon, are members of the total group, but not of the crown group. Therefore, they are part of the cetacean "stem group", or, more succinctly, "stem-cetaceans". (Indohyus may also be a stem-cetacean, but there are differing hypotheses.) Note that the stem group includes the ancestors of the crown group, but not all members of the stem group are ancestors of the crown group. For example, Basilosaurus cetoides is a stem-cetacean, but it is a somewhat derived offshoot of the cetacean lineage, with a long, snake-like body different from that of modern cetaceans or their ancestors.

Somewhere around the time of the Cretaceous-Paleogene extinction (when non-avian dinosaurs, among many other taxa, became extinct reached a population size of zero), the cetacean line split off from other extant lineages (either from the hippopotamid lineage, the ruminant lineage, or both at once—the artiodactyl lineage). The earliest stem-cetaceans were hoofed, but they soon gave way to amphibious varieties, which looked vaguely like mammalian crocodiles with flippers. Over time, adaptations toward an aquatic lifestyle were accumulated in stem-cetacean populations: tail flukes, dorsal fins, birth in the water. Stem-cetaceans were replaced by cetaceans, which possessed all of these adaptations. Early cetaceans split into two major lineages: one leading to the filter-feeding mysticetes and the other to the echolocating, predatory odontocetes.

Many living species of cetacean are threatened. Perhaps the worst case is that of the Yangtze River dolphin or baiji, Lipotes vexillifer. This human-sized freshwater cetacean was once one of the few animals to be actually protected by superstition (many others, instead, are endangered by it—think of rhinoceros horns as an ingredient in impotence remedies). But, in modern times, this protection has come to mean less. The last uncontested sighting of a baiji was in 2004. The IUCN currently classifies the species as critically endangered, but it may be extinct already. If so, it would be the first aquatic mammal species to go extinct in the 3rd millennium—less than a decade in and we're already off to a bad start.

Not all zoologists use Cetacea in the crown group sense; some paleontologists expand it to include some or all of the stem group. But there is a danger in doing this. Cetacea is primarily a term from the neontological (as opposed to paleontological) literature, so it is most often associated with the suite of characters that the living organisms possess. But members of the stem group may or may not possess these. A recent, spectacular discovery of a fossilized, pregnant Maiacetus (which would go in the above chart somewhere around Rodhocetus) shows that Maiacetus probably gave birth on land. It is not known (to me, anyway) whether they had dorsal fins or tail flukes.

Since extending neontological terms beyond the crown group can result in unwarranted character inferences, some systematists prefer to limit such terms to crown groups when possible. The PhyloCode, a nomenclatural code currently in draft form, advocates this approach (see, for example Recommendation 10.1B). (The PhyloCode is also the source of the "pan-" convention for the names of total groups; see Art. 10.3.)

Moving too fast? Let's slow down....

Sloths

Although today's sloths, or Folivora ("leaf-eaters"), are tree-dwellers, many in the past were terrestrial; some were even amphibious (living sloths are good swimmers when they need to be). Modern sloths exist in two clades: Bradypus, the three-toed sloths, and Choloepus, the two-toed sloths. The closest living relatives to sloths are Vermilingua ("worm-tongues"), or "true" anteaters (not to be confused with other long-tongued mammals that feed on eusocial insects, such as aardvarks, numbats, and echidnas). Together, sloths and anteaters comprise a clade called Pilosa ("hairy ones"). All living pilosans are Neotropical, although some fossil taxa were Nearctic (as are some of their cousins, the armadillos, or Loricata).

Here is a phylogeny with a sampling of species to give an overview of sloth evolution (again, highly abridged, to say the least):

Time goes from left to right. Left-right lines connect ancestor species to descendant species. Silhouettes are not to scale.
Note that I've flipped the living sloths upside-down ... err, right-side-up ... err ... never mind.
The sloth lineage split from its stem-anteater kin during the Paleocene. The original sloths were terrestrial, but at least two clades became highly arboreal (Bradypus and Choloepus, mentioned before). One clade, including Thalassocnus, went in a different direction and became amphibious. Most lineages, however, remained terrestrial, one of them culminating in the enormous Megatherium americanum, a sloth the size of an elephant.

If you look at the above diagram, you might think, "But, look, there are more than just two extant groups." This is because the diagram is on such a vast scale that it's impossible to distinguish the extant from the recently extinct. Here's the same phylogeny to a logarithmic scale, which expands recent time:


Now we can actually see the Holocene, or "Recent", our current geological epoch (unless you accept the Anthropocene—more on that later). And you can see that some taxa, such as Mylodon and Megatherium, died out around the Pleistocene-Holocene transition. This transition was only 11 to 12 thousand years ago (an eyeblink in geological time, as can be seen by the fact that it's not even visible in the first chart).

Some Haitian sloth species persisted until much more recent times. Parocnus serus and Synocnus comes were still hanging around (ha ha—just kidding, they were more or less terrestrial) when European explorers first came to the Caribbean. They may have died out in the 16th century C.E.

Sloths present an interesting case because the clades that can be considered crown groups have changed over the course of human existence. Twelve thousand years ago, when humans were still settling the New World, a sloth crown group would have included Mylodon, and within that group a smaller crown group would have included Choloepus, Hapalops, Thalassocnus, Megatherium, Synocnus, and Parocnus. (Thalassocnus and Hapalops were extinct, but would still be part of that crown group.) After the Holocene-Pleistocene extinctions, Mylodon would no longer be part of the sloth crown group, and the Choloepus-but-not-Bradypus crown group would no longer contain Thalassocnus, Megatherium, or Hapalops. This continued, more or less, until the European/African settling of the Caribbean, at which time Synocnus and Parocnus died out.

Today, some species of Bradypus (B. pygmaeus and B. torquatus) are endangered. Time will tell if conservation efforts win out, or if the Bradypus crown group shrinks further.

Defining Crown Groups

I've been talking about crown groups changing over time, but we need nomenclature to be stable. (Why? Well, for one thing, so we can communicate effectively about conservation efforts.) One way to do this is to tie names to phylogeny-based definitions. This is how the PhyloCode works.

There are three major ways to define a crown group:

1. Node-Based Definition

This is the simplest way: just build up a list of extant specifiers, take their final common ancestor, and add all descendants. As an example, we could define Cetacea as the clade originating with the final common ancestor of Balaena mysticetus Linnaeus 1758 and Delphinus phocaena Linnaeus 1758 (=Phocoena phocaena Gray 1825). One advantage of this type of definition is that we don't need to worry about the meaning of "extant".

There is a peril with this approach, though: what if a new phylogenetic hypothesis shows some member to be outside the delimited clade? Fortunately the PhyloCode allows for expedient "unrestricted" emendations in such cases (i.e., minor, commonsense emendations that don't require committe approval; see Art. 15). But ideally the need for such emendations should be avoided. One way to avoid this need is with modified node-based definitions, which come in two major flavors.

2. Branch-Modified Node-Based Definition

In this approach, we create a node-based definition using all extant members of a given total group. For example, the cetacean total group could be defined as everything sharing closer ancestry with B. mysticetus than with Hippopotamus amphibius Linnaeus 1758 or Bos taurus Linnaeus 1758. Thus, Cetacea could be defined as the clade originating with the final common ancestor of all extant organisms that share a closer common ancestor with B. mysticetus than with H. amphibius or B. taurus.

There are two pitfalls to this approach. One is that you might fail to specify the closest extant outgroup. For example, if pigs (suids) turned out to be closer to whales than cattle or hippos are, then, under that definition, pigs would be cetaceans! Again, this can be fixed with an unrestricted emendation, but it would be nice not to have to do that.

The other pitfall is that the author(s) must define "extant", but more on that later.

3. Apomorphy-Modified Node-Based Definition

This style of definition uses a derived character, or "apomorphy", to delimit a clade, and then creates a node-based clade using the members of that apomorphy-based clade. This requires some apomorphy that evolved within the stem group. Cetacea, for example, could be defined as the clade originating with the final common ancestor of all extant organisms that possess tail flukes homologous (synapomorphic) with those of B. mysticetus.

There are two pitfalls with this approach. One is that the apomorphy may turn out not to have evolved within the stem group. It may have evolved earlier, thus expanding the content of the clade, or it may have evolved independently multiple times within the crown group, thus contracting the content of the clade. (It must be said, though, that in the case of cetacean tail flukes, both possibilities are extremely unlikely.)

The other pitfall is the same as that of branch-modified node-based definitions: what does "extant" mean? Extant when? And by what criteria? Let's look at this in more depth.

The Many Flavors of "Extant"

Although many of the PhyloCode's articles deal with crown groups and total groups, the code doesn't provide a single definition of "extant". Instead, the author of the definition must select a meaning. The author has considerable latitude here. If nothing is specified, there is a default fallback: extant at time of publication (Art. 9.5).

Recent (Holocene)

In just about every place that the PhyloCode uses the word "extant", it is followed with a parenthesis: "(or Recent)". In other words, a crown group may be considered as a clade originating with the final common ancestor of Holocene organisms.

I find this problematic for a couple of reasons. One is that the Holocene covers all of human history and more, so just being Holocene is no guarantee that we'll have good specimens. Some Holocene species went extinct thousands of years before Sumerians ever put wedge to clay tablet. Look at the sloth phylogeny—some of the species, such as Mylodon sp. and M. americanum, seem to have gone extinct right before the Holocene. But what if some small populations endured for a short while in refugia? That could drastically change the content of, e.g., a branch-modified node-based clade including Choloepus but not Bradypus.

The other problem is that "Recent" doesn't really get at the reason why crown groups are interesting. They're interesting because we have a wealth of available data about some of their members, data which can be used to extrapolate ancestral states. The same amount of data is not present for stem groups, which are generally known from fossils, if they are known at all.

Non-Fossil Specimens

Philip Cantino, one of the authors of the PhyloCode, once told me (pers. comm.) his opinion on what "extant" should mean: "I think that any species that was extant recently enough to be represented in museums in a non-fossilized form (e.g., study skins, herbarium specimens) should be treated as extant." Note one big advantage of this approach: it's much simpler to verify whether something is extant.

This approach also gets closer to the basic intent of crown groups. Extra data are available in non-fossil specimens. But it's still short of the data present in living forms; for example, behavior is not observable. Is it enough extra data to warrant recognizing the species as extant for nomenclatural purposes? It boils down to opinion. (And I note that behavior might not be a very important consideration for Phil's purposes, since he works on plants.)

This idea has direct relevance for sloths, because one extinct form is actually represented by non-fossil specimens! Mylodon skins, complete with armor nodules and fur, still exist, having been preserved in caves. Supposed that Folivora were defined as the clade originating with the final common ancestor of all extant organisms sharing closer ancestry with Bradypus tridactylus Linnaeus 1758 than with Myrmecophaga tridactyla Linnaeus 1758 (the giant anteater). The question of whether Mylodon is extant would determine whether an entire clade (Mylodontidae) belongs to Folivora. (Of course, nobody says that has to be the definition of Folivora, or even that Folivora has to be a crown group, but this is just an example.)

Anthropocene

Although the Holocene is already a ridiculously short geological epoch, Cruzen and Stoermer (2000) proposed naming a new, much shorter geological epoch for the Industrial Age. They named the "Anthropocene" in recognition of the global effects that Industrial-Age humans have had upon the environment, and set its starting date as 1784 C.E., with James Watts' invention of the steam engine. (This is also, not coincidentally, around the time that certain effects of pollution start to appear in ice core samples.)

This designation hasn't met widespread adoption, to my knowledge, nor has it been proposed as a criterion for determining whether a species is "extant" for the purposes of nomenclature. But it seems to me like a better candidate than the Holocene. At least Anthropocene species have all coexisted with scientists.

Living at a Given Time in History

A similar candidate to using the Anthropocene, was proposed in a bulletin board discussion by Mike Taylor. Under this proposal, anything living during or after 1758 C.E. would be considered extant, 1758 being the year that the 10th edition of Linnaeus' Systema Naturae was published. That publication is regarded as the beginning of biological nomenclature by the botanical and zoological codes.

Both of these approaches (Anthropocene and Systema Naturae) have similar problems to the use of "Recent", although to a lesser extent. It's difficult to establish whether some species went extinct before or after the selected boundary. For example, the sloths Synocnus and Parocnus probably went extinct a couple of centuries earlier than these dates, but it's possible that they persisted in remote areas. An even closer example is Hydrodamalis gigas, Steller's sea cow, which seems to have gone extinct by 1768 (post-Systema Naturae, pre-Anthropocene!).

Living Now

Right now. Wait, I mean NOW. Wait ... no ... okay ... NOW.

Well, there is no one "now". Every instant is its own "now". Obviously, I mean something closer to the PhyloCode's default definition: extant as of the publication date of the definition.

This is less problematic than using earlier dates in some ways. We have much better ways of tracking populations today than we did in the 1700s. But pushing the date closer to the present also presents problems. Consider Steller's sea cow and the Yangtze River dolphin. It's easy to say that the sea cow is extinct, but the fate of the dolphin is still as unclear as the muddy waters it swims (or swam?) in. Consider: what if, despite the phylogeny presented above, Lipotes was found to be an outgroup to [other] extant cetaceans? Would the cetacean crown group include it or not? (Thanks to Matt Martyniuk for thinking of that example.)

And all of the meanings mentioned so far share another problem: the discovery of a previously unknown species could change everything. There are many example of "Lazarus taxa" (so-called because, like the character of Lazarus in the Christian gospels, they appear to rise from the grave), living organisms that represent clades previously known only from fossils: the Laotian rock rat, Laonastes aenigmamus (Diatomyidae); the Indian Ocean coelacanth, Latimeria; the gladiators, Mantophasmatinae (Insecta: Mantophasmatodea); the monito del monte, Dromiciops gliroides (Marsupialia: Microbiotheria); the Wollemi pine, Wollemia nobilis (Araucariaceae: Wollemia); etc. Although the discovery of such a species is always a wonderful event, it's potentially disruptive to modified node-based definitions.

Living And Published Upon

This last problem can be easily remedied, though: just require that something must be extant and published upon at the time of the definition. This could go a long way toward stabilizing definitions. The only drawback is that it could be seen as a bit arrogant: "If science hasn't heard of it, then it doesn't exist!" But this is only for nomenclatural purposes (of course Wollemi pines make a sound when they fall, whether scientists hear it or not).

But this still doesn't solve the problem of whether Lipotes is extinct or extant.

Let Someone Else Worry About It

The IUCN has put tons of thought and effort into these sorts of questions. One possibility would be to simply leave the question up to their Red List and let them worry about particulars. If I want to know if species X was extant in 2004, I check their database and see if its designation was something other than "extinct" for that year. They may not always be able to pinpoint the exact time of death for every species, but they do as good a job as anyone, or better.

Of course, the IUCN doesn't cover all species, leaving out 1) species that have been extinct for a long time (e.g., Tyrannosaurus rex), and 2) species that haven't been published by scientists yet (e.g., Laonastes aenigmamus in lists prior to 2005). But I think in both of these cases we can consider such species to be "non-extant for the purposes of nomenclature". Long-extinct species are clearly not extant. Treating undiscovered species as non-extant has the same stabilizing benefit as requiring an extant species to be published upon. The only problem spot is the taxa that the IUCN doesn't focus on, e.g., bacteria and archaeans. But this still leaves plenty of taxa that it works just fine for.

I think I like this approach best, at least for the taxa I study (amniotes). Delegate the issue to the experts. Mylodon and Synocnus are extinct. Lipotes is critically endangered (at least as of last year). The nomenclatural problem is taken care of, and we can move on to more crucial problems, like preserving the crown groups that we have.

21 October 2008

Six Ways to Say the Same Thing

Prose
"'Aves' refers to the crown clade stemming from the most recent common ancestor of Ratitae (Struthio camelus Linnaeus 1758), Tinamidae (Tetrao [Tinamus] major Gmelin 1789), and Neognathae (Vultur gryphus Linnaeus 1758)."
—Jacques Gauthier & Kevin de Queiroz 2001 December


Simple Mathematical Formula

Aves := Clade(Struthio camelus + Tetrao major + Vultur gryphus)


Complex Mathematical Formula

Aves Linnaeus 1758 [Gauthier & de Queiroz 2001] := (AD o max o CA)(Struthio camelusTetrao majorVultur gryphus)


Ridiculously Complex Mathematical Formula

C := {x : (∀y ∈ (Struthio camelusTetrao majorVultur gryphus))[xy]}
A := {xC : (∀yC)[xy]}
Aves := {x : (∃yA)[xy]}


Simple MathML-Content
<apply>
xmlns="http://www.w3.org/1998/Math/MathML"
<csymbol
definitionURL="http://namesonnodes.org/2008/phylo/math/nodeClade"/>
<csymbol
definitionURL="urn:isbn:0-85301-006-4/Struthio+camelus"/>
<csymbol
definitionURL="urn:isbn:0-85301-006-4/Tetrao+major"/>
<csymbol
definitionURL="urn:isbn:0-85301-006-4/Vultur+gryphus"/>
</apply>

Complex MathML within Custom Markup
<pn:definition
xmlns="http://www.w3.org/1998/Math/MathML"
xmlns:pn="http://namesonnodes.org/2008/phylo/names">
<apply>
<csymbol
definitionURL="http://namesonnodes.org/2008/phylo/math/clade">
<mi form="prefix">Clade</mi>
</csymbol>
<apply>
<csymbol
definitionURL="http://namesonnodes.org/2008/phylo/math/nodeAncestors">
<mo form="infix">+</mo>
</csymbol>
<csymbol
definitionURL="urn:isbn:0-85301-006-4/Struthio+camelus">
<![CDATA[<i>Ratitae</i> (<i>Struthio camelus</i> Linnaeus 1758)]]>
</csymbol>
<csymbol
definitionURL="urn:isbn:0-85301-006-4/Tetrao+major">
<![CDATA[<i>Tinamidae</i> (<i>Tetrao</i> [<i>Tinamus</i>] <i>major</i> Gmelin 1789)]]>
</csymbol>
<csymbol
definitionURL="urn:isbn:0-85301-006-4/Vultur+gryphus">
<![CDATA[<i>Neognathae</i> (<i>Vultur gryphus</i> Linnaeus 1758)]]>
</csymbol>
</apply>
</apply>
</pn:definition>



References

23 August 2008

What is it that you hate about the PhyloCode?

Mention of the PhyloCode can incite some pretty strong emotions among biologists. Some are supportive, but there's a lot of vitriol out there. Consider, for example the title of Carpenter's (2003) paper: A critique of pure folly. Yes, a paper with that title actually got published in a scientific journal. Why the hate?

The thing is, it's sometimes hard to pin people down on exactly why they dislike it. Part of the problem is that the PhyloCode is surrounded by misconceptions. Much of what's been written about it is shockingly ignorant, considering that the code is freely available online and not horribly long (certainly shorter than any of the other codes). Consider Benton (2000), who seems to have not even read the then-current draft and proceeded to write an entire review based on what he imagined the PhyloCode to be like.

This is not to say that all critiques are uninformed. But of those that are, I find that they fall into two camps. They either raise points that have since been addressed in later drafts, or they are simple matters of taste.

As an example of addressed issues, the critiques of how the PhyloCode was going to handle species are now defunct, since it won't cover species. I myself raised dozens of smaller issues to the authors of the code, who then either emended the draft of the code or convinced me that no change was needed.

And as an example of difference of opinion, some people don't see the utility of the "crown clade convention" adopted by recent drafts. Some people just don't like phylogenetic nomenclature, period. The rank-based systems (which, incidentally, should not be called Linnaean systems, per de Queiroz [2005]) do well enough for many people's purposes, and they don't see a reason to change. Of those who like phylogenetic nomenclature, some don't see the advantages of a centralized approach, and would rather let it grow freely (e.g., Sereno [pers. comm.]).

That's all fine; it's good for people to point out flaws if they are later addressed, and it's understandable that not all people would agree on matters of opinion. But I see so much misinformation out there that I think it has to be the source of much of the dislike out there. One popular article is titled What if we decided to rename every living thing on Earth?, when the PhyloCode has always advocated using existing names when possible. Pickett's (2005) report on the first ISPN meeting is titled The new and improved PhyloCode, now with types, ranks, and even polyphyly, when the PhyloCode has never had types (only specifiers, which are similar but operationally different), has always allowed ranks, and has never allowed polyphyly.

So let me put a question out there: If you dislike the PhyloCode, what is it about it that you dislike? And are you sure it's something actually in the code?

09 June 2008

ISPN3 Meeting: Updates

I've just gotten word of a few changes in the ISPN meeting schedule.
  1. The ISPN meeting will be held on July 21–22, with a social on July 20.
  2. Registration at pre-meeting rate is extended to July 1.
  3. Abstracts will be accepted until July 1.
For more details, see the Protist 2008 website and/or my previous post.

07 May 2008

ISPN3 Meeting: Abstract Deadline

There's only one week left to submit abstracts for the Third Meeting of the International Society for Phylogenetic Nomenclature! (I just submitted two, one for a talk and one for a poster.) The deadline is May 15, which is also the deadline for early registration.

Once again, some important information:
When? 2008 July 21–23
Where? Dalhousie University, Halifax, Nova Scotia, Canada
How much does it cost? $190 (CAD*) if you register by May 15
What if I'm a student? $90 (CAD*) if you register by May 15
Where do I register? At the Protist 2008 website. (Be sure to select "I am registering for ISPN"—unless you're a protistologist, of course.)
How do I submit abstracts? Follow the instructions here, but send the document to harold [dot] bryant [at] gov [dot] sk [dot] ca and use one of these keywords:
  • theory of phylogenetic nomenclature
  • history and development of phylogenetic nomenclature
  • definition of taxon names
  • other (specify).
I'm a U.S. citizen. Do I need a passport? Yes.
Where can I find more information? In the Second Circular.

The last meeting (Yale 2006) was great and hopefully this one will be even better!

* Canadian and U.S. dollars are worth about the same these days.

16 April 2008

The Third Meeting of the ISPN: Second Circular

The second circular for the Third Meeting of the International Society for Phylogenetic Nomenclature has been posted on the ISPN's website.

The Third Meeting of the International Society for Phylogenetic Nomenclature will be held in Halifax, Nova Scotia, at Dalhousie University, from July 21 to July 23, 2008. This meeting is an opportunity to discuss topics that pertain directly or indirectly to phylogenetic nomenclature in general, as well as the International Code of Phylogenetic Nomenclature (PhyloCode) and the Companion Volume in particular. In addition to providing a forum to contribute oral and poster presentations, this meeting will also include plenary talks by invited guest speakers. This meeting is organized in close collaboration with the International Society of Protistologists (ISOP) and the International Society for Evolutionary Protistology, which are hosting the joint Protist 2008 meeting, at the same venue, from July 21 to July 26, 2008.


The deadline for early registration and for abstract submissions is May 15.
(I better go get working on my submission[s].)

31 January 2008

The Nouns of Names on NEXUS

Programming is a mystery to most folks. They see a bunch of overpunctuated gobbledygook with words strewn about here and there and it's completely opaque. They know that it somehow translates into the functionality of the applications, games, websites, etc. that they use. But they have no inroads to understanding how on Earth that works.

I will now attempt a (very) partial explanation for the phylogenetics-literate crowd.

One thing people don't understand is that object-oriented computer languages (which is what I primarily use) are actually designed to be compatible with how humans think. Or at least, they're a sort of compromise between how computers think and how humans think. Natural languages, of course, are totally biased toward how humans think, while machine codes (and their slightly dressed-up cousins, assembly languages) are totally biased toward how computers think. (There are also functional languages which are slightly more computer-biased than object-oriented languages.)

Like natural languages, object-oriented languages have nouns, except they're called objects. They also have verbs, except they're called methods. Methods are usually (but not always) attached to objects. Objects can have attributes which are themselves other objects—these are called fields, and they can work a bit like adjectives (although that's not a perfect analogy).

One of the first tasks I do as a programmer when approaching a new project is to figure out what the nouns of the project are. These will be used as the basis for classes, which are the templates which objects (and their methods and fields) are created from.

So let's use Names on NEXUS as an example. This is my project, hinted at in my paper, to relate the data in NEXUS files (Maddison et al. 1997) to definitions of names as governed by the PhyloCode. So my first step is to come up with lists of nouns (i.e., class candidates) for each side of the equation:

PhyloCode (nomenclature)scientific name (or nomen), uninomen, binomen, prenomen, genus name, clade name, phylonym, definition
PhyloCode (specification)specifier, species, specimen, specimen collection, specimen accession, apomorphy, definition
NEXUSNEXUS file, tree, tree element, tree node, tree terminus, character state
sharedphylogeny, citation, piece of literature, calendar date, URI


The goal of this project is to translate a PhyloCode definition (associated with a phylonym) into a list of NEXUS taxa (i.e., operational taxonomic units) using a NEXUS tree. For that to happen, there need to be some additional nouns that help relate NEXUS entities to PhyloCode entities:

Names on NEXUScharacter state specifier, taxon specifier, character state link, taxon link


The next step is to figure out how these nouns—these classes—relate to each other. Typically, this involves statements of the form "X is a Y" (which has to do with class hierarchy) and the forms "X has a Z", "X has one or more Zs", "X has zero or more Zs", etc. (which have to do with fields). I'll also translate these nouns into capitalized "camel-humped" format, the standard format for class names in the languages I use. Lower-case "camel-humped" nouns are of primitive types (numbers, strings, Booleans) which I don't need to make a class for.

Literature
  • A LiteraturePiece has a CalendarDate, one or more authorNames, and zero or more URIs.
  • A Citation has a LiteraturePiece and zero or more authorNames.


PhyloCode: Nomenclature
  • A Nomen has a Citation, an orthography, and zero or more URIs.
  • A Uninomen is a Nomen.
  • A Binomen is a Nomen and a Phylonym, and has a Prenomen and a Uninomen.
  • A GenusName is a Uninomen and a Prenomen.
  • A CladeName is a Uninomen, a Phylonym, and a Prenomen.
  • A PhyloDefinition has a Citation, a Phylonym, one or more Specifiers, a prose statement, and a mathML statement(see my paper for details on the last one).


PhyloCode: Specification
  • A Specifier has zero or more URIs.
  • An Apomorphy is a CharStateSpecifier, and has a description and a Citation.
  • A Specimen is a TaxonSpecifier, and has one or more SpecimenAccessions.
  • A SpecimenAccession has a code and a SpecimenCollection.
  • A SpecimenCollection has a code, a name, and zero or more URIs.
  • A Species is a TaxonSpecifier, and has one or more Binomens (binomina) and one or more Specimens (name-bearing types).


NEXUS
  • A NexusFile has textData, zero or one Citations, zero or more URIs, a numTaxa amount, a numChars amount, two or more CharStates, zero or more Trees, zero or more CharStateLinks, and zero or more TaxonLinks.
  • A CharState has a character index and a character scoring.
  • A Tree has a TreeNode.
  • A TreeNode is a TreeElement and has two or more TreeElements.
  • A TreeTerminus is a TreeElement and has a taxonIndex.


Names on NEXUS
  • A CharStateSpecifier is a Specifier.
  • A TaxonSpecifier is a Specifier.
  • A CharStateLink has a CharState and a CharStateSpecifier.
  • A TaxonLink has a taxonIndex and a TaxonSpecifier.


Now I can describe the core functionality of Names on NEXUS. Taking a NexusFile, the user selects one of its Trees. Next, the application finds all PhyloDefinitions whose Specifiers are each referred to by one of the NexusFile's CharStateLinks or TaxonLinks. Using the Tree and each PhyloDefinition's mathML statement, it correlates the PhyloDefinition's Phylonym to a set of taxon indices in the NexusFile.

Of course, this is not all the application will do. (In fact, I've been done with that part of the programming for a while now.) There will also need to be a lot of programming for saving these data permanently in a database, presenting the data to the user, and making it easier for the user to enter data (for example, by creating methods for coming up with specifier suggestions based on definition statements). This may take a while....

20 January 2008

Third Meeting of the International Society for Phylogenetic Nomenclature

The ISPN's third biennial meeting has just been officially announced.



Third Meeting of the International Society for Phylogenetic Nomenclature
Halifax, Nova Scotia, July 21 – July 23, 2008

We are pleased to announce that the 3rd Meeting of the International Society for Phylogenetic Nomenclature (ISPN) will be held in conjunction with a joint meeting of the International Society of Protistologists and the International Society for Evolutionary Protistology (https://protist2008.dal.ca/). In addition to featuring communications on the theory and practice of phylogenetic nomenclature, this meeting will be an opportunity to discuss the forthcoming release of the PhyloCode and publication of the Companion Volume, as well as development of the on-line registration database (RegNum). All systematists interested in the development of phylogenetic nomenclature are welcome. Discussions and presentations at this meeting may influence the future development of the PhyloCode.

Venue:
The meeting and associated social gatherings will be held on the campus of Dalhousie University, in the centre of Halifax. In order to make the meeting accessible to all scientists, on-campus dormitory-style accommodation will be available, in addition to nearby hotels. Note that U.S. Citizens traveling to Canada will be required to carry passports.

Conference Language:
English

ISPN Organizing Committee:
Harold Bryant, Chair, Royal Saskatchewan Museum, Canada
Nico Cellinese, University of Florida, U.S.A.
Walter Joyce, Yale University, U.S.A.
Michel Laurin, CNRS, Paris, France

Registration and Abstract Submission:
Instructions on how to register and submit abstracts will be provided in the second circular, which will be distributed in the very near future.

For More Information:
Download the First Circular (PDF)



I'd better brush up on my protistology. Oh, and hurry up with Names on NEXUS....

04 January 2008

Resolutions for 2008

I'm not going to bother you with personal resolutions (lose weight, save money, blah blah blah), but rather creative resolutions.

2007 was kind of a watershed year for me in many ways.
My girlfriend, Susan, also had a very productive year, since she started USC film school a year ago.

Of course, it wasn't entirely positive. I dropped the ball on Parry & Carney, and the Dinosauricon continues to languish. (Some day I plan to re-use code from March of Man and Names on NEXUS for a new version, but that day is still far off.)

Well, with 2007 in mind, here's what I'd like to get done in 2008:
  • Launch Names on NEXUS and give a talk on it at this year's ISPN meeting in Halifax, Nova Scotia (and also try for an SVP talk or poster). Perhaps start working on a related paper, if applicable.
  • Continue developing March of Man and add several dozen images to it. Continue promoting it and get at least another dozen artists to contribute. Perhaps do a poster or something at SVP.
  • Fix a few remaining issues with the PhyloCode website.
  • Help Susan on her filmic endeavors, and continue to develop a sci-fi concept we started.
  • Continue translating Genesis.
  • Release some ActionScript 3.0 source code into the public domain.