30.01.2015 Views

Untitled

Untitled

Untitled

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

18<br />

1. INTRODUCTION<br />

The evidences from ITS and trnL-F sequences might weight in favour of the Lolium evolution<br />

from a perennial, European Schedonorus ancestor (Catalan et al. 2004). On the other<br />

hand, experimental data from protein studies (Bulińska-Radomska and Lester 1988) and<br />

patterns of cross-hybridization (Xu et al. 1992) make more plausible the Stebbins (1958)<br />

hypothesis that both genera had a common ancestral form with a base chromosome number<br />

x=7. Notwithstanding these difficulties in finding any ancestral form, the ease of interspecific<br />

hybridization between Lolium and Festuca from the subgenus Schedonorus and<br />

similarity of large number of morphological characters convinced some taxonomists for<br />

classification of Schedonorus within the genus Lolium (Darbyshire 1993; Stammers et al.<br />

1995). Under this taxonomic scheme Lolium is not any longer a small genus with only diploid<br />

species but it consists from a number of species with various ploidy levels. The incorporation<br />

of Schedonorus into the genus Lolium suggests that polyploidy has played<br />

an important role in its evolution (Craven et al. 2005). If we assume, as most grass taxonomists<br />

will argue, that diploidy is the ancestral condition, then all Lolium species should<br />

be regarded as more ancient than all polyploid fescues from Schedonorus. It should be<br />

noticed, however, that the above classification is not widely accepted. One emerging consensus<br />

seems to be that the relationship between Festuca and Lolium is difficult to deduce<br />

conclusively on the basis of available molecular data.<br />

1.4. TAXONOMY OF THE GENUS LOLIUM<br />

Another challenge underlying the genus Lolium is in finding the progenitor and defining<br />

exactly a kind of species differentiation. In principle, monophyly of Lolium has been accepted<br />

but it is still a source of contention either L. perenne or L. rigidum is the common ancestor<br />

of the genus. Based on total nuclear DNA content, which increases from L. perenne (4.2 pg)<br />

to L. temulentum (6.2 pg), Thomas (1981) speculated that speciation of Lolium might have<br />

involved isolates of L. perenne. Protein studies suggest as well that the ancestral forms of<br />

Lolium have been most like the present perennial ryegrass (Bulińska-Radomska and Lester<br />

1988). An evolutionary trend in reduction of life-cycle from the perennial forms to the annual<br />

taxa seems to be supported by the combined analyses of ITS and trnL-F sequences (Catalan<br />

et al. 2004). Alternatively, most authors agree that the common ancestor has its closest<br />

affinity with L. rigidum (Malik 1967; Charmet and Balfourier 1994). But somewhat an intriguing<br />

calculation when the differentiation of the genus into species has begun was proposed.<br />

Firstly, using isozymes Charmet and Balfourier (1994) postulated that the evolution of Lolium<br />

has started about 10 000 years ago in close association with primitive agriculture. When<br />

the data from chloroplast DNA were employed it turned out that differentiation of the genus<br />

into species has begun much earlier, about one million years ago in the Middle East, at the<br />

same time as reported for the genus Triticum (Charmet et al. 1997). So, there is tremendous<br />

discrepancy.<br />

The uncertainties related with Lolium phylogeny contribute greatly to the ambiguity of<br />

the taxonomic classification of the genus. Moreover the frequent revision of classification<br />

schemes using the different names for slightly dissimilar variants of the same species makes<br />

them confusing. Terrel (1968), for example, found almost 500 published names for the dif-

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!