Skip Navigation


AOBPreview originally published online on June 25, 2007
Annals of Botany 2007 100(2):219-224; doi:10.1093/aob/mcm116
This Article
Right arrow Full Text Freely available
Right arrow FREE Full Text (PDF) Freely available
Right arrow Content Select
Right arrow All Versions of this Article:
100/2/219    most recent
mcm116v1
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Similar articles in PubMed
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Lim, K. Y.
Right arrow Articles by Leitch, A.
Right arrow Search for Related Content
PubMed
Right arrow PubMed Citation
Right arrow Articles by Lim, K. Y.
Right arrow Articles by Leitch, A.
Agricola
Right arrow Articles by Lim, K. Y.
Right arrow Articles by Leitch, A.
Social Bookmarking
Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?


© The Author 2007. Published by Oxford University Press on behalf of the Annals of Botany Company. All rights reserved. For Permissions, please email: journals.permissions@oxfordjournals.org

Parental Origin and Genome Evolution in the Allopolyploid Iris versicolor

K. Yoong Lim1,*, Roman Matyasek2, Ales Kovarik2 and Andrew Leitch1

1 School of Biological and Chemical Sciences, Queen Mary, University of London, London E1 4NS, UK
2 Institute of Biophysics, Academy of Sciences of the Czech Republic, Kralovopolska 135, CZ-61265 Brno, Czech Republic

* For correspondence. E-mail y.k.lim{at}qmul.ac.uk

Received: 9 February 2007    Returned for revision: 26 March 2007    Accepted: 1 May 2007    Published electronically: 25 June 2007

Background Aims: One of the classic examples of an allopolyploid is Iris versicolor, ‘Blue Flag’ (2n = 108), first studied by Edgar Anderson and later popularized by George Ledyard Stebbins in cytogenetics and evolutionary text-books. It is revisited here using modern molecular and cytogenetic tools to investigate its putative allopolyploid origin involving progenitors of I. virginica (2n = 70) and I. setosa (2n = 38).

Methods: Genomic in situ hybridization (GISH), fluorescent in situ hybridization (FISH) and Southern hybridization with 5S and 18–26S ribosomal DNA (rDNA) probes were used to identify the parental origin of chromosomes, and to study the unit structure, relative abundance and chromosomal location of rDNA sequences.

Key Results: GISH shows that I. versicolor has inherited the sum of the chromosome complement from the two progenitor species. In I. versicolor all the 18–26S rDNA units and loci are inherited from the progenitor of I. virginica, those loci from the I. setosa progenitor are absent. In contrast 5S rDNA loci and units from both progenitors are found, although one of the two 5S loci expected from the I. setosa progenitor is absent.

Conclusions: These data confirm Anderson's hypothesis that I. versicolor is an allopolyploid involving progenitors of I. virginica and I. setosa. The number of 18–26S rDNA loci in I. versicolor is similar to that of progenitor I. virginica, suggestive of a first stage in genome diploidization. The locus loss is targeted at the I. setosa-origin subgenome, and this is discussed in relation to other polyploidy systems.

Key words: Allopolyploid, diploidization, genome evolution, rDNA, Laevigatae irises, Iris versicolor


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer: Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.