Y-DNA J1 retrospective 2015
Autor: Ricardo Costa de Oliveira | Publicado: 2015-12-22T05:46:00-08:00


- We had three ancient Northern J1 results:

1- Sarmatian J1, Beslan, North Ossetia (2/3 C. A.D.) Gennady 
Afanasiev. Khazar Confederates in the Don basin. Pure research methods 
and the paradigm of modern archeology. M. 2015. S.146-153. 
(Afanasiev:2015).

2 - Karelian J1 Eastern Hunther-Gatherer from Russia, Yuzhnyy Oleni Ostrov [I0211/UzOO 40], M, 5500-5000 BC. (Mathieson:2015).

3 - Satsurblia cave J1, Georgia, F4306+, 13000 YBP (Jones:2015). 

- We have discovered and confirmed our own 14000 years old branch 
SNP FGC6064 comparing my results FTDNA 73612-YFull YF01554 (I have 188 
new SNPs to be tested FGC5987 to FGC6175) with the Big Y results from 
Kitching, England, 381875-YF03848. 

-
 FTDNA is still boycotting our J1-M365 SNP. M365 was discovered in 2004,
 the M365 SNP has been in ISOGG's list since 2006 and M365 is also 
present at the last Y Chromosome Consortium (YCC). I had M365 as my 
terminal SNP in FTDNA in 2007. People from my J-M365 Project
 paid and tested positive for M365. We have M365+ in our J1 report. We 
have several people now listed as J1-M267 and not J1-M365 as our 
terminal SNP. We have recurrent SNPs in the case of almost all SNPs and 
M365 is quite old, so it was found and listed in other branches, like 
R-M365 in FTDNA's haplotree. Our J1-M365 was discovered in 2004 and is 
extremely valid, useful and important. So we are only asking to our 
terminal J1-M365 SNP to be where it was in FTDNA haplotree in 2007 
because we paid, tested positive and that's our J1 group. Please FTDNA, 
we need our J1-M365 downstream SNP of FGC6064 in the haplotree.

-
 YFull tree, the best NGS public tree, now has J1-M365 as a node. Now we
 are waiting the analysis of another Portuguese Big Y BAM YF04781 
results there.

- Now
 it's obvious that J1 was born and emerged in the Northern Near Eastern 
regions around the Black Sea, Eastern Anatolia, the Caucasus, the 
Caspian Sea and Northern Iran where the ancient types of J1 and the 
basal branches were discovered and still can be found there nowadays.
 No research or article has ever investigated basal types and SNPs of J1
 from the cradle areas. We depend on the private tests and the citizen 
scientists only. I need some Gilaki and Caspian or Northern Iranian J1 
types matching our M365 cluster in terms of STR to be fully sequenced 
with NGS. 
Let's wait 2016.

&nbsp;

I think most of the European J1 is historical and related to historical 
migrations and wars in Europe arriving after the Iron Age or even after 
the Roman Empire. There's no homogeneity in the European J1 branches and
 the gaps can only be understood in reference to the J1 original lands 
because the European J1 clusters usually match more closely similar Near
 Eastern J1 branches than other European J1 clusters. No J1 was never 
found in any European Neolithic site and even in the Mediterranean areas
 possibly associated to Late Neolithic movements like the Sardinian J1 
is always a local or regional cluster not found spreaded in other 
distant European regions because no Western European J1 has a deep 
chronology in Europe demonstrating an ancient presence there like the 
Karelian Mesolithic or the Caucasian CHG and the living Finn J1 
individual as revealed in the last articles files only because the 
authors couldn't assume or could write about the major breakthrough of 
the ancient J1 remains and sequences in the texts for incompetence or 
other hidden interests. The Near Eastern differences between Northern 
Near Eastern basal types of J1 of Caucasian, Iranian, Anatolian, 
Armenian and Byzantine origins also can offer a big contrast with 
downstream derived P58 and subsequent downstream SNPs with origins 
associated to Southern Near Eastern, Levantine and Semitic origins in 
Europe like Phoenicians, Jews or Arabs depending on the phylogenetic 
positions in the J1 tree already found and occupied by J1 in Western 
Asia.&nbsp;
      

&nbsp;

Ricardo
Merry Christmas and Happy New Year !