Wikipedia:DOIUpload/Saudi Arabian Y-Chromosome diversity and its relationship with nearby regions

From Wikipedia

Saudi Arabian Y-Chromosome diversity and its relationship with nearby regions

, 2009.

BMC Genetics , vol. 10, p.59

 

Abstract[edit]

Background[edit]

Human origins and migration models proposing the Horn of Africa as a prehistoric exit route to Asia have stimulated molecular genetic studies in the region using uniparental loci. However, from a Y-chromosome perspective, Saudi Arabia, the largest country of the region, has not yet been surveyed. To address this gap, a sample of 157 Saudi males was analyzed at high resolution using 67 Y-chromosome binary markers. In addition, haplotypic diversity for its most prominent J1-M267 lineage was estimated using a set of 17 Y-specific STR loci.

Results[edit]

Saudi Arabia differentiates from other Arabian Peninsula countries by a higher presence of J2-M172 lineages. It is significantly different from Yemen mainly due to a comparative reduction of sub-Saharan Africa E1-M123 and Levantine J1-M267 male lineages. Around 14% of the Saudi Arabia Y-chromosome pool is typical of African biogeographic ancestry, 17% arrived to the area from the East across Iran, while the remainder 69% could be considered of direct or indirect Levantine ascription. Interestingly, basal E-M96* (n = 2) and J-M304* (n = 3) lineages have been detected, for the first time, in the Arabian Peninsula. Coalescence time for the most prominent J1-M267 haplogroup in Saudi Arabia (11.6 ± 1.9 ky) is similar to that obtained previously for Yemen (11.3 ± 2) but significantly older that those estimated for Qatar (7.3 ± 1.8) and UAE (6.8 ± 1.5).

Conclusion[edit]

The Y-chromosome genetic structure of the Arabian Peninsula seems to be mainly modulated by geography. The data confirm that this area has mainly been a recipient of gene flow from its African and Asian surrounding areas, probably mainly since the last Glacial maximum onwards. Although rare deep rooting lineages for Y-chromosome haplogroups E and J have been detected, the presence of more basal clades supportive of the southern exit route of modern humans to Eurasian, were not found.

Background[edit]

The arid Arabian Peninsula can be viewed as a geographic cul de sac and passive recipient of Near East cultural and demic expansions since the Bronze Age. However, southern Arabian late Neolithic excavations revealing sorghum and date palm cultivation attest to earlier influences from East Africa and South western Asia [1]. However, after the southern dispersal route of modern humans across the Bab el Mandeb Strait was proposed [[2] and further developed [[3], multidisciplinary interest on this region has dramatically increased in the search for traces of such putative early southern dispersals across the Arabian threshold. From an archaeological perspective, Lower Paleolithic Oldowan industries found in the Arabian Peninsula indicated that, presumably, H. erectus or H. ergaster may have been making forays into this region [[4]. There is also evidence of Middle Paleolithic Mousterian and Aterian technologies in Arabia suggesting the possibility of an expanded southern border for H. neanderthalensis and potential links with populations from Northern Africa [[5]. More recent field work has sampled new Palaeolithic sites in Oman, under covering lithic assemblages with typological affinities to industries in the Levant, India and the Horn of Africa, suggesting there were a series of hunter-gathers range expansions into southern Arabia from all three refugia over the last quarter of a million years [[6]. However, there are few reliable age estimates for these industries. Furthermore, the passage of these hominids to Arabia could be either through an overland route or across a waterway.

From a population genetics perspective, the most recent studies on the Arabian Peninsula have been carried out using mainly uniparental, mitochondrial DNA (mtDNA) and Y-chromosome, markers. Analysis based on maternal lineages in the region has been interpreted to represent traces of late Palaeolithic, Neolithic and more recent inputs from nearby regions into Arabia as well as signatures of authochtonous expansions [7]-[8]. However, the lack of deep rooting M and N sequences in the contemporary Arabian mtDNA pool leaves the proposed southern coastal route without empirical support. Although Y-chromosome basal lineages remain undetected, phylogeographic patterns indicate that the Levant was an important bidirectional corridor of human migrations [[9],[10]. Moreover, the Levant appeared as the main source of male lineages to the Arabian Peninsula [[11]. However, Saudi Arabia, a country that occupies about 80% of the Arabian Peninsula, was not directly included. In order to fill this void, we performed a high resolution Y-chromosome SNP analysis of 157 Saudi Arabian males and a STR-based analysis of J1-M267, the most frequent Y-chromosome haplogroup in Saudi Arabia. Comparisons to other published Arabian Peninsular populations and nearby regions were made to further explore paternal traces of the modern human transit across Arabia.

Methods[edit]

Sample and typing[edit]

All sample collecting and genotyping tasks were performed by the Saudi Arabian collaborators of this study. Buccal swabs or peripheral blood were obtained from 157 paternally unrelated Saudi Arab males whose all known paternal lineages, at least for two generations, were of Saudi Arabia origin. Due to its moderate size we have not performed a regional subdivision of the sample. Informed consent was obtained from all the participants. This research followed the tenets of the Declaration of Helsinki. DNA was extracted using the Nucleon™ BACC Genomic DNA Extraction Kit (GE healthcare, Piscataway, NJ, USA). Sixty-seven Y-Chromosome binary genetic markers were genotyped hierarchically. Primers, polymorphic positions and haplogroup nomenclature were as recently actualized [12]. After amplification and purification, haplogroup typing was carried out in all cases by direct sequencing on the ABI 3130 xI Genetic Analyzer (Applied Biosystems, Foster city, CA, USA). The following 17 Y-STR loci: DYS19, DYS385 a/b, DYS389I/II, DYS390, DYS391, DYS392, DYS393, DYS437, DYS438, DYS439, DYS448, DYS456, DYS458, DYS635 and Y-GATA H4 were amplified in a Gene Am PCR System 2700 (Applied Biosystems) using the AmpF/STR Yfiler Amplification Kit (Applied Biosystems) following the manufacturers instructions. DNA fragment separation was carried out in an ABI Prism 3100 Genetic Analyzer (Applied Biosystems). STR alleles were identified by comparison to a commercial allelic ladder using Genotyper 3.7 NT software.

Our Saudi Arabia sample was compared to other Arabian Peninsula populations and to surrounding areas using data from previous studies performed at a similar level of haplogroup resolution. These samples comprise, 72 Qatari, 164 United Arab Emirate and 62 Yemeni [11]; 121 Omani and 147 Egyptian [[10]; 201 Somalis [[13]; 916 Lebanese [[14]; 146 Jordanian [[15]; 203 Iraqi (139 from Al-Zahery et al. [[16] and 64 from Sanchez et al. [[13]); 523 Turks [[17];150 Irani [[18] and 176 Pakistani [[19].

Statistical analysis[edit]

To make comparisons reliable, haplogroup frequencies were normalized to the same phylogenetic level as the sample in the published studies with the most unrefined haplogroup resolution. Analysis of molecular variance (AMOVA) and haplogroup frequency pairwise FST genetic distances [20] were performed using the ARLEQUIN 2000 package [[21]. Principal component (PC) analysis and two-dimensional graphics were carried out using the SPSS statistical package 11.5 (SPSS, Inc). Times to most recent common ancestor (TMRCA) for the J1-M267 clade were calculated from STR variances and by coalescence methods (see Additional File 1). Mean STR variance was estimated as proposed by Kayser and others [22] and transformed in divergence time using a mean STR mutation rate of 0.00069 per generation of 25 years [[23]. For coalescence age estimations STR loci were weighted by their respective variances as described in Qamar and others [[24]. Then, median-joining networks were constructed after processing the data with the reduced median network method using Network version 4.5.1.0 [[25]. The rho-statistic was estimated with Network and converted into time using the above mentioned Zhivotovsky and others [[23] mutation rate. For these estimations loci DYS385 were excluded and the repeats of DYS389I were subtracted to the DYS389II so that its diversity was not considered twice.

Results[edit]

Y-SNP analysis[edit]

Only 27 of the 67 binary markers analyzed were informative in defining the haplogroup census of the Saudi Arabian sample (Table 1). The following 40 polymorphisms (M60, M130, M217, M174, P147, M33, M75, P177, P2, M215, M78, M81, M123, M329, M89, M282, M201, P20, P16, M286, M52, M197, M370, M170, M172, M410, M92, M241, M9, M20, M317, M231, M214, M119, M207, M173, M343, P25, M18 and M124) were observed at ancestral allele status in the sample set. The most abundant haplogroups in Saudi Arabia, J1-M267 (42%), J2-M172 (14%), E1-M2 (8%), R1-M17 (5%) and K2-M184 (5%) are also well represented in other Arabian populations (Table 1). When the AMOVA analysis compared all regions as unitary groups except the Arabian Peninsula, it showed a partition of variance within populations (91%) and among groups (6.8%) to be highly significant (p < 0.0001 in both cases) but an analysis among the samples within the Arabian Peninsula (2.2%) did not reach statistical significance (p = 0.10 ± 0.01). The same trend is also reflected in FST based pairwise distances (Table 2), as all the distances not involving pairs of Arabian samples were statistically highly significant (p < 0.0001) but those within the Arabian Peninsula showed lower levels of significance, except when affecting Yemen (p < 0.0001) that is the most divergent population of Arabia, although showing its least distance to Qatar (p = 0.048). Precisely, in addition to Yemen, Saudi Arabia has significant haplogroup frequency differences only with Qatar (p = 0.009). Quantitatively, the main peculiarity of the Saudi male pool with respect to the rest of the Arabian samples is a significant higher presence of the J2-M172 related haplotypes (p = 0.001). On the other hand, the high divergence of Yemen is mainly due to a significant excess of J1-M267 (p < 0.0001) types, a nearly significant excess of J2-M67 types (p = 0.062), and to a lack of R1-M17 representatives (p = 0.04). In addition, southern Arabia, represented by Yemen and Oman, show a greater E1-M123 account than in northern areas (p = 0.006). As the Y-chromosome phylogeography is well structured [26],[27], it is possible to roughly quantify the different male inputs from surrounding regions into Arabia. When haplogroups A, B, E-M96, E1-P2, E1-M2, and E1-M35 frequencies are assumed to be representative of the Africa contribution and frequencies of C, F, G, H, L, O, Q and R1-M17 as arrivals, across Iran, from Central, southern, and southeastern Asia, inputs of 13.4% and 16.6% from both areas are estimated for Saudi Arabia. UAE is the region with the least African (5.5%) and the greatest Iranian influence (36.8%). If the global inputs for the Arabian Peninsula are estimated to approximate 10% from sub-Saharan Africa and 22% from Iran, the remaining 68% could be considered of direct or indirect Levantine ascription. Relative relationships among the Arabian samples to nearby regions are graphically represented in bidimensional plots, resulting from MDS analysis obtained from a matrix of FST distances (Figure 1a) and as the two first components of a PC analysis (Figure 1b). In the first analysis, congruently with its pair-wise distances, Somalia appears as an outlier, and the close relationship found between Qatar and Yemen is also reflected in the plot. For the rest of the Arabian samples a clear partition exists, whereas Oman and UAE appear closer to the Levant samples that include Egypt, the Saudi component positions approximates towards the northeast edge of the Near East. However, the population spatial distribution along to the first and second principal components in the PC analysis is quite different. In this case, the main haplogroups (C, H, L, O, Q and R1-M17), responsible for the positive displacement along the first component, are most abundant in Iran, Pakistan and UAE. On the opposite side are E1-M35, E1-M123 and J1-M267 that drives Yemen to the negative edge. For the second component, the main positive values correspond to the Eurasian haplogroups G-M201. I-M170, J2-M67 and R1-M269, that group all the Near East populations, including Egypt, whereas the Arabian samples and Somalia fall on the negative side pulled by their comparatively higher frequencies of the sub-Saharan Africa haplogroups E1-M2 and E2-M75 and, again, the most prevalent haplogroup in Arabia J1-M267. As the first and second principal components only capture the 26% and the 17% of the variance respectively and haplogroup E1-M78 has a minor contribution in the first and second component matrix, Somalia, that has the highest E1-M78 frequency of all the samples, does not behave as an outlier in the bidimensional PC representation. Finally, it deserves mention that, qualitatively, Saudi Arabia is also peculiar because of the presence, in low frequencies, of two underived E-M96* (1.3%) and J-M304* (1.9%) lineages that were not detected in other surveys of the Arabian Peninsula [10],[11].

Bidimensional plots based on Y-chromosome haplogroup frequency data in the Arabian Peninsula and adjacent populations. [A] MDS analysis (stress value = 0.265); [B] PC analysis. Abbreviations: ANA, Anatolia; EGY, Egypt; IRN, Iran; IRQ, Iraq; JOR, Jordan; LEB, Lebanon; OMA, Oman; PAK, Pakistan; QAT, Qatar; SAR, Saudi Arabia; SOM, Somalia; UAE, United Arab Emirates; YEM, Yemen.

Table 1[edit]

"Ychromosome haplogroup frequencies observed for Saudi Arabia and nearby regions"
HaplogroupSNPSarQatarUAEOmanYemenSomaliaEgyptLebanonJordanIraqAnatoliaIranPakistan
A3aM320.50
A3b2*M131.003.000.680.38
B*M1391.00
B2a*M1500.641.39
B2a1aM1092.00
B2b*M1121.271.39
C*RPS4Y2.000.11
C3*M2170.960.676.82
C5*M3561.271.230.380.57
E*M961.270.55
E1a*M331.000.22
E1b1*P20.38
E1b1a*M23.825.003.231.501.000.660.990.191.330.57
E1b1a7*M1913.822.785.522.001.00
E1b1b*M2151.61
E1b1b1*M352.553.231.503.000.22
E1b1b1a*M781.390.612.0077.6018.0010.4810.279.364.973.331.14
E1b1b1a2*V131.390.61
E1b1b1a3*V220.641.396.75
E1b1b1b*M810.611.508.001.22.740.19
E1b1b1c*M12312.000.507.004.261.48
E1b1b1c1*M344.461.393.078.0613.015.540.67
E1b1cM3291.39
E2*M751.392.000.50
E2b*M982.78
F*M893.680.680.49
F1*M2820.611.33
G*M2012.000.509.006.552.460.191.33
G1*M2850.641.840.194.670.57
G1aP200.610.76
G2a*P152.552.781.841.613.428.417.334.55
G2a1*P160.680.96
G2a2M2860.19
G2bM2870.19
G2cM3771.14
H*M691.272.452.000.57
H1*M520.500.385.11
H1a*M820.641.391.842.00
H1a1M1970.57
H1bM3700.19
I*M1701.004.83.420.491.150.57
I1*M2531.15
I2a*P372.29
I2a1M3590.19
I2b*M2230.57
J*M3041.910.19
J1*M26740.1358.3334.9738.0072.582.5019.0020.0930.8231.038.4111.333.41
J1bM3650.19
J1e1M3680.19
J1e2M3690.19
J2*M1725.000.508.006.1626.614.34
J2a*M4101.234.844.008.52
J2aDYS41311.462.784.299.33
J2a1M472.551.391.8415.281.153.33
J2a2*M670.641.390.611.004.843.007.754.793.632.001.14
J2a2a*M921.230.112.681.33
J2a5M1580.38
J2a9M3390.19
J2a10M3400.19
J2b*M121.271.391.234.001.002.732.050.762.00
J2b2*M2411.390.961.332.27
K*M90.870.680.990.57
K2M1845.104.918.0010.408.004.695.912.492.67
L*M201.005.240.994.02
L1M761.272.782.452.67
L2*M3170.67
L2a*M2740.67
L2b*M3490.190.67
L3*M3570.640.610.67
N*M2312.87
N1c*Tat0.99
N1c1*M1780.96
N2*P432.00
O*M1750.640.611.000.110.190.67
O1a*M1190.61
Q*M2421.911.231.001.001.531.72
Q1a2*M250.440.194.00
Q1a3*M3460.640.61
L1M765.11
L2*M3171.14
L3*M3576.82
O3*M1221.7
O3a3c*M1340.57
Q1a1M1200.57
Q1a3*M3461.7
Q1bM3781.14
R*M2071.313.41
R1*M1730.611.002.000.490.192.670.57
R1a*SRY15320.67
R1a1*M175.106.947.369.001.003.002.511.376.906.8812.6724.43
R1a1cM2040.67
R1b*M3430.2213.70.19
R1b1*P250.610.990.38
R1b1aM180.55
R1b1b1M730.764.55
R1b1b2*M2691.911.393.681.002.007.314.119.8514.538.002.84
R1b1cM3350.19
R2M1241.391.000.221.370.961.337.39
Sample1577216412162201147916146203523150176

Table 2[edit]

"Fst distances between populations. Codes as in figure 1"
SARQATUAEOMAYEMSOMEGYLEBJORIRQANAIRNPAK
SAR-
QAT0.023**-
UAE0.004ns0.031-
OMA0.020**0.0390.017**-
YEM0.0820.021*0.1020.107-
SOM0.6640.990.6020.6711.367-
EGY0.0650.120.050.0450.2150.33-
LEB0.0570.1080.0450.0530.1880.3260.028-
JOR0.040.0730.0330.0480.1370.5020.0390.046-
IRQ0.0660.1010.0550.0470.1850.5230.0410.0660.051-
ANA0.0890.1620.0680.0850.2620.3810.0480.0470.0540.046-
IRN0.0560.1350.0410.0670.2550.4840.0480.0370.0590.0770.025-
PAK0.1260.210.0950.1160.3520.5390.0930.0860.1130.1280.0550.029-
* p < 0.05; ** p < 0.01; the rest of pairwise comparisons have p < 0.001 values

Y-STR analysis[edit]

Y-chromosome STR diversity was used to obtain age estimates in Saudi Arabia for the most frequent J1-M267 haplogroup. In order to compare these estimations with other Arabian peninsula regions, we re-calculated the J1-M267 ages in UAE, Qatar and Yemen using the STR data already published for these countries [11]. STR haplotypes found in Saudi Arabia are listed in Additional file 1. Divergence times obtained using mean variance and coalescence methods are presented in Table 3. Values obtained using coalescence resulted always larger than those based on variance.

Table 3[edit]

"Y-haplogroup J1-M267 variance and divergence times deduced from Y-STR loci"
Populationsample sizek17ak14bM-267 varianceT(ky)Divergence time (ky) Mean ± SE
UAEc5740330.165.816.81 ± 1.53
Qatarc4233280.196.717.27 ± 1.83
Yemenc4541400.279.6911.27 ± 2.03
Saudi Arabia4841390.2910.3711.59 ± 1.93
Arabian Peninsula1921491290.248.8510.78 ± 1.65
a Haplotype number using 17 Y-STR locib Haplotype number using 14 Y-STR locic Estimated from the Cadenas et al. (2007) data

Discussion[edit]

Consistent with the rest of the Arabian Peninsula, haplogroup J is the most abundant component in Saudi Arabia embracing 58% of its Y-chromosomes. Its two main subclades (J1-M267 and J2-M172), show opposite latitudinal gradients in the Middle East. J1-M267 is more abundant in the southern areas, reaching a frequency around 73% in Yemen, whereas J2-M172 is more common in the Levant. Most probably, the significant higher presence of J2-M172 in Saudi compared to other Arabian populations is due to the larger northern boundary that Saudi Arabia shares with the Levant. The Fertile Crescent region has been considered the most probable origin of the earliest dispersions of both subclades [17],[28],[29]. Further subdivisions of J1-M172 have uncovered more recent Bronze age expansions from Turkey and the Balkans traced by the J2-M67/M92 and J2-M12 subgroups [[17],[30],[31].

In a similar way, it is possible that J2-M47 signals a more recent expansion from the Levant that also affected the Arabian Peninsula. The peculiar distribution of J2-M67 in Arabia could be explained assuming maritime contacts from classical Mediterranean cultures. The presence in Saudi Arabia of three males harbouring underived J1-M304 chromosomes is intriguing. It could be that they came together with the J1-M267 or J2-M172 expansive waves, or they could represent the remnants of an old and geographically widespread Palaeolithic substrate. This type of underived chromosomes has been detected rarely in Turkey [17], in Oman and in the eastern Mediterranean area [[30]. However, as the critical Levantine region has not yet been adequately dissected for J1, it seems premature to favor any of these hypotheses. The geographic pattern and most probable origin of the Y-chromosome haplogroup J in Arabia faithfully mirrors those found for the most prevalent J and R0a mtDNA haplogroups in the same region [[7]-[32],[8]. In addition, J1-M267 divergence age calculated for Saudi Arabia (11.6 ± 2 kya) and Yemen (11.3 ± 2 kya) are also very coincidental with those calculated for J1b (11.1 ± 8.4 kya) and R0a1 (9.6 ± 2.9 kya) in Saudi Arabia [[7],[33]. It is worth mentioning that J1-M267 ages in Saudi Arabia and Yemen are significantly older than those obtained for UAE and Qatar (Table 3)[11] and for Oman [[10] pointing to a terrestrial more than to a maritime colonization. It has been suggested that Yemen could be a center of expansion for mtDNA haplogroup R0a [[32].

Although the comparatively high divergence calculated for J1-M267 Y-chromosomes in Yemen [11] could be in support of primary or, at least, secondary human expansions from southern Arabia, it could also be explained as result of successive arrivals of J1 chromosomes from different source regions. Furthermore, J 1-M267 diversities found here for Saudi Arabia are of the same range than in Yemen and both smaller than the one estimated for Turkey [[17]. This southwards decreasing trend is more compatible with a Neolithic arrival to Arabia via the Levant as proposed by others [[11]. In fact, the coalescence ages calculated in Saudi Arabia for their most prominent mtDNA and Y-chromosome lineages merged around 10 kya. This period is coincidental with an improvement of the climatic conditions in the area that facilitated the spread of Natufian and Neolithic cultures from the Fertile Crescent north and southwards. The haplogroup E1-M123/M34 has an extended but sparse geographic distribution in Eastern Africa, the Middle East and the Mediterranean basin [[10],[28],[31]. However, its frequency rises considerably in some populations, most probable because of isolation and genetic drift effects. This would explain frequencies as high as 11% found in some Ethiopian samples [[31] or the highest (31%) found, until now, in the Dead Sea region of Jordan (Flores et al. 2005). In the Arabian Peninsula this clade is, in general, well represented but reaches significant higher frequencies in the southern countries of Yemen and Oman compared with northern areas. An East African origin, and posterior spread to the Near East through the Levantine corridor, of this lineage was proposed based on the much larger variance of this clade in Egypt (0.5) versus Oman (0.14) [[10]. On the contrary, other authors have suggested that E1-M123 may have originated in the Near East because of its generalized implantation there [[17] compared to its presence in Eastern Africa, mainly just localized in Ethiopia [[28]. Recent E-M123 haplogroup variances calculated for Yemen (0.14) and UAE (0.25) were also lower than the Egyptian one [[11]. In addition, haplotypic differences found for those two Arabian countries indicated that they do not share a common ancestry [[11]. So, from an Arabian Peninsula perspective, E1-M123 could have come from Ethiopia, across the Horn of Africa, or from the Levant, or even from both sources, forming independent isolates. Global male inputs from Sub-Saharan Africa and Asia across Iran, not the Levant, into the Arabian Peninsula have been estimated in this study, as 13.4% and 16.6% from both source areas respectively. Recent mtDNA studies on the same Arabian Peninsula countries [[7]-[32],[8] have confirmed a notable female-driven sub-Saharan African input with a mean value around 15% for all the Peninsula, although frequencies as high as 60% have been detected in Hadramawt populations of Yemen [[32]. Curiously, the Iranian female flow (18%) was also rather similar to that calculated for Africa. Although a slight ratio excess of Sub-Saharan African female versus male gene flow is detected (1.12) we do not found the strong sexual bias proposed by other authors for Arabian populations and attributed to the peculiarities of the recent slave-trade [[8],[34]. Without dismissing the role mediated by slavery, the geographical distribution of these sub-Saharan African lineages in the Arabian Peninsula seems to indicate a prehistoric entrance of a noticeable portion of these lineages that participated in the building of the primitive Arabian population [[33],[32]. The presence of two underived E-M96 Saudi lineages raises interesting questions related to the macrohaplogroup DE-YAP phylogeography. The recent resolutions of the CDEF-M168 tripartite structure to the bipartite DE-YAP and CF-P143 [[12],[27] extends the conversation regarding the early successful colonization of Eurasia. While several scenarios remain potentially possible the most parsimonious model is the most prudent. This model proposes the successful colonization of Eurasia by migration(s) of populations containing precursor Y-chromosome founder macrohaplogroup CDET-M168 and basal mtDNA L3 representatives. Regions near but external to northeast Africa, like the Levant or the southern Arabian Peninsula could have served as an incubator for the early diversification of non-African uniparental haplogroup varieties like Y chromosome DE-YAP*, CF-P143* and mtDNA M and N molecular ancestors. These would have spread globally and diversified over time and space. This model would imply that both CF-P143 and the DE-YAP evolved nearby but outside Africa. One DE-YAP* ancestor would have spread to Asia and evolved to haplogroup D while another DE-YAP* returned to northeast Africa and evolved into hg E. It is noteworthy that DE-YAP* has been detected at low frequency in Africa [[35]. Again, this hypothesis has its mtDNA counterpart as it is well documented that, in the Palaeolithic, at least three clades (X1, U6, M1) derived respectively from the three main Eurasian macrohaplogroups (N, R, M) came back to North Africa from Asia [[36]-[37].

Within this frame, it should be expected that E-M96* types appear in Africa although its presence in the Arabian Peninsula instead Eastern Africa would not compromise the last proposed model. It could be suggested that these E-M96 Saudi lineages have a sub-Saharan Africa ancestry. However, at least for one of them, all their known male ancestors belong to a big Shammar Arab tribe that ruled much of central and northern Arabia from Riyadh to the frontiers of Syria and northern Iraq. In addition, it might be present in Lebanon [14]. However, as the authors did not type more markers derived within the E-M96 background such as P147, P177, P2, P75 or M329, more comprehensive phylogenetic resolution of YAP derived Y-chromosomes in the Middle East and North and East Africa are necessary to explore the topic further. In any case, the presence of E-M96* in Saudi Arabia should not be taken as support of the southern exit of modern humans across the Srait of Bab el Mandab as no D nor CF underived lineages have been yet found in this area.

Conclusion[edit]

The Y-chromosome genetic structure of the Arabian Peninsula seems to be mainly modulated by geography. The data confirm that this area has mainly been a recipient of gene flow from its African and Asian surrounding areas, probably mainly since the last Glacial maximum onwards. Although rare deep rooting lineages for Y chromosome haplogroups E and J have been detected, the presence of more basal clades supportive of the southern exit route of modern humans to Eurasian, were not found.

Authors' contributions[edit]

KKA and AH was in charge of carrying out the sequences, collection of samples, haplogrouping and writing part of the manuscript. AMG, JML, VMC and PAU were in charge of design of the experiments, analysis of the data and writing manuscript. All authors read and approved the final version of the manuscript.

Supplementary Material[edit]

Additional file 1[edit]

Table S1. Y-chromosome STR haplotypes for haplogroup J1-M267 in Saudi Arabia.

File:1471-2156-10-59-S1.XLS
Click here for file

Acknowledgements[edit]

Dr. Abu-Amero is supported by grants from the Glaucoma Research Chair at the Dept. Of Ophthalmology, College of Medicine, King Saud University, Riyadh, Saudi Arabia. This research was also supported by grant BFU2006-04490 from Ministerio de Ciencia y Tenologia to J.M.L and Saad Specialist Hospital, Al-Khobar (AH).

References[edit]

  1. 1 Cite error: Invalid <ref> tag; name "B1" defined multiple times with different content
  2. 2 Cite error: Invalid <ref> tag; name "B2" defined multiple times with different content
  3. 3 Cite error: Invalid <ref> tag; name "B3" defined multiple times with different content
  4. 4 Cite error: Invalid <ref> tag; name "B4" defined multiple times with different content
  5. 5 Cite error: Invalid <ref> tag; name "B5" defined multiple times with different content
  6. 6 Cite error: Invalid <ref> tag; name "B6" defined multiple times with different content
  7. 7.0 7.1 7.2 7.3 7 Cite error: Invalid <ref> tag; name "B7" defined multiple times with different content
  8. 8.0 8.1 8.2 8.3 12 Cite error: Invalid <ref> tag; name "B12" defined multiple times with different content
  9. 13 Cite error: Invalid <ref> tag; name "B13" defined multiple times with different content
  10. 10.0 10.1 10.2 10.3 10.4 10.5 14 Cite error: Invalid <ref> tag; name "B14" defined multiple times with different content
  11. 11.0 11.1 11.2 11.3 11.4 11.5 11.6 11.7 11.8 15 Cite error: Invalid <ref> tag; name "B15" defined multiple times with different content
  12. 12.0 12.1 16 Cite error: Invalid <ref> tag; name "B16" defined multiple times with different content
  13. 13.0 13.1 17 Cite error: Invalid <ref> tag; name "B17" defined multiple times with different content
  14. 14.0 14.1 18 Cite error: Invalid <ref> tag; name "B18" defined multiple times with different content
  15. 19 Cite error: Invalid <ref> tag; name "B19" defined multiple times with different content
  16. 20 Cite error: Invalid <ref> tag; name "B20" defined multiple times with different content
  17. 17.0 17.1 17.2 17.3 17.4 17.5 21 Cite error: Invalid <ref> tag; name "B21" defined multiple times with different content
  18. 22 Cite error: Invalid <ref> tag; name "B22" defined multiple times with different content
  19. 23 Cite error: Invalid <ref> tag; name "B23" defined multiple times with different content
  20. 24 Cite error: Invalid <ref> tag; name "B24" defined multiple times with different content
  21. 25 Cite error: Invalid <ref> tag; name "B25" defined multiple times with different content
  22. 26 Cite error: Invalid <ref> tag; name "B26" defined multiple times with different content
  23. 23.0 23.1 27 Cite error: Invalid <ref> tag; name "B27" defined multiple times with different content
  24. 28 Cite error: Invalid <ref> tag; name "B28" defined multiple times with different content
  25. 29 Cite error: Invalid <ref> tag; name "B29" defined multiple times with different content
  26. 30 Cite error: Invalid <ref> tag; name "B30" defined multiple times with different content
  27. 27.0 27.1 31 Cite error: Invalid <ref> tag; name "B31" defined multiple times with different content
  28. 28.0 28.1 28.2 32 Cite error: Invalid <ref> tag; name "B32" defined multiple times with different content
  29. 33 Cite error: Invalid <ref> tag; name "B33" defined multiple times with different content
  30. 30.0 30.1 34 Cite error: Invalid <ref> tag; name "B34" defined multiple times with different content
  31. 31.0 31.1 31.2 35 Cite error: Invalid <ref> tag; name "B35" defined multiple times with different content
  32. 32.0 32.1 32.2 32.3 32.4 9 Cite error: Invalid <ref> tag; name "B9" defined multiple times with different content
  33. 33.0 33.1 8 Cite error: Invalid <ref> tag; name "B8" defined multiple times with different content
  34. 36 Cite error: Invalid <ref> tag; name "B36" defined multiple times with different content
  35. 37 Cite error: Invalid <ref> tag; name "B37" defined multiple times with different content
  36. 38 Cite error: Invalid <ref> tag; name "B38" defined multiple times with different content
  37. 42 Cite error: Invalid <ref> tag; name "B42" defined multiple times with different content

Template:CC-BY-2.0