Editor’s Corner
A New
Y-Chromosome Phylogenetic Tree
The long-awaited update to the
Y-Chromosome Consortium (
The Hammer group took the
opportunity of the publication of the new tree to introduce dozens of new SNPs in
the “P” series. Indeed, if these new
SNPs had not been included, the “new”
Publishing dozens of new SNPs at
once almost assures that the detailed testing information provided to support
the proper placement of each SNP on the Y tree will mostly be lacking. One can only hope that the required testing
has been done. However, past experience
is not reassuring. This is the same
group that for a couple of years insisted that Haplogroup I-M223 was not a
subgroup of Haplogroup I-P38. Hopefully,
this new batch of SNPs has been tested more thoroughly than was the case with
P38 and M223.
Still, it is useful to have some
of the leaders in the field get together every few years and share information
and update the Y tree. The coauthorship of
Of course, discoveries are being
made continuously, and the new
One very helpful inclusion in the Karafet article is the listing of all the new SNPs with the
corresponding primers and location of the polymorphic sites. This will allow any commercial lab to develop
tests for any of the new SNPs.
The new Karafet
tree will u
For ISOGG to succeed in
maintaining a phylogenetic tree, it needs to have more cooperation from the
main groups involved in population genetics and SNP discovery. At the beginning of the ISOGG effort, there
seemed to be support. Liaisons were set
up with the major labs and they were supposed to provide input and feedback to
ISOGG. However, if one of the major
groups saw ISOGG make a choice that was different from the choices they were in
the process of making for themselves, by and large they kept it to themselves.
ISOGG is committed to a tree with
the minimum of confusion for users, so naturally, with the publication of the
new tree in Karafet (2008),
ISOGG will be changing several haplogroup names to conform to the choices made
by Karafet.
Hopefully, in the future there will be more communication of discoveries
to the ISOGG committee, so that when a major new effort such as Karafet’s is published, there will be minimal differences
with the then-current ISOGG tree.
If the ISOGG committee were fully
supported by the professional community, it could better provide a valuable
service as a clearing house for haplogroup phylogeny, SNP identification, and
haplogroup names. Researchers who
discovered a new binary polymorphism could see immediately at the ISOGG site
the names that would be available for the new haplogroup.
Meanwhile, new SNPs are being
announced or published almost every month.
ISOGG’s role will be to maintain a tree that
is as up-to-date as possible, allowing us to see where each new SNP fits
in. Some of these will cause additions
or reorganizations of part of the tree, usually resulting in name changes for
affected haplogroups. Slowly, the ISOGG
tree will diverge from the benchmark tree provided in Karafet. The name changes will often be a little
annoying, but that’s just the way progress happens in the Y-chromosome field.
Web Resources
http://www.isogg.org/tree
ISOGG Y Tree
References
Karafet TM, Mendez FL, Meilerman MB, Underhill PA,
Zegura SL, Hammer MF (2008) New binary polymorphisms reshape and increase
the resolution of the human Y chromosomal haplogroup tree. Genome Res, (to be published in May issue).