<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"CMU Serif";
panose-1:2 0 6 3 0 0 0 0 0 0;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Malgun Gothic";
panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"\@Malgun Gothic";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"CMU Serif";
color:windowtext;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:779030878;
mso-list-type:hybrid;
mso-list-template-ids:-2007968442 2025748456 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:16;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman \(Body CS\)";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word;overflow-wrap: break-word;-webkit-nbsp-mode: space;line-break:after-white-space">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"CMU Serif"">Dear Ian, Martin, et al. – There are two separate issues here. In no particular order:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:12.0pt;font-family:"CMU Serif"">Generic science journals have begun to publish articles with typological content. That’s not going to change, so there’s little
use in us wishing or demanding that typologists (and notably anyone doing typological research, as many of the authors in question aren’t actually typologists) publish only in linguistics journals or at least cognitive science journals.
<b>However.</b> The problem with the generic science journals is that they typically either don’t bother to recruit trained linguists (let alone typologists) as reviewers for the manuscripts in question, or else the review process they rely on is structured
in such a way that the manuscript is unlikely to be reviewed by a typologist. It’s my understanding that these journals tend to rely on a largish number of associate editors, who are of course recruited from the fields that publish most frequently in the journals.
These AEs are most likely to funnel manuscripts to reviewers they know, and neither the AEs nor anyone they know is likely to be a linguist, let alone a typologist.
<b>How do we address this problem?</b> What, for example, if ALT were to write a letter, signed by as many members as we can gather signatures from, address to the editorial boards of the journals in question, to make them aware of the problem and suggest some
colleagues who would volunteer as consultants for AEs in search of a reviewer for a manuscript with typological content?<o:p></o:p></span></li></ul>
<p class="MsoListParagraph"><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:12.0pt;font-family:"CMU Serif"">Turning to Dunn et al., I think I have been as critical of that article as anybody, yet I’m prepared to partially defend it here
(and accept the flak I’m doubtlessly going to get for that </span><span style="font-size:12.0pt;font-family:"Apple Color Emoji"">😊</span><span style="font-size:12.0pt;font-family:"CMU Serif"">). Yes, by restricting the investigation to just four large language
families, the article became woefully inadequate to the goal of testing the Greenbergian generalizations. But what really turned this limitation into a significant flaw that arguably should have prevented the article from getting published in the form in which
it was is that it way oversold its findings. The article should have been a methods paper, with a narrative along the lines of “Here’s a new way of testing typological generalizations, by looking, instead of at a stratified sample of languages to see whether
the features in question co-occur with statistically significant probability, at phylogenies to see whether those features tend to co-evolve in lineage-specific ways.” Of course, as a methods paper, the article would have been much less likely to get published
in Nature. Now, why was that study restricted to those four phylogenies? Because back then, with Grambank not even having been conceived yet (as far as I know), that was pretty much the limit of what was feasible. Yes, the authors could have looked at a larger
sample of smaller phylogenies – but that would have required some form of stratified sampling, which the authors presumably wanted to avoid
</span><span style="font-size:12.0pt;font-family:"Apple Color Emoji"">😉</span><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p></o:p></span></li></ul>
<p class="MsoListParagraph"><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<p class="MsoListParagraph"><span style="font-size:12.0pt;font-family:"CMU Serif"">Meanwhile, though, Dunn et al. (2011) still has a number of merits to its credit IMO:<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:12.0pt;font-family:"CMU Serif"">It reintroduced the community of typologists to the idea that hypothetical typological generalizations ought to be tested not
only synchronically, but also diachronically. I’m embarrassed to admit that I had not even been aware of Maslova (2000), and might have entirely missed this groundbreaking paper if the controversy over Dunn et al. hadn’t brought it to my attention (although
Dunn et al. unfortunately failed to cite Maslova).<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:12.0pt;font-family:"CMU Serif"">I think it played an important part in making the case for Grambank. The effort that went into Grambank is awe-inspiring from
where I look at it, and Dunn et al. provides a straightforward justification for it,
<i>especially</i> if one accepts that looking at just four large language families will inevitably render any test of typological generalizations invalid.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="font-size:12.0pt;font-family:"CMU Serif"">And of course it brought typology to the attention of a much broader scientific audience. Yes, it did so with an unwarranted
attack on its established research methods. But it still has the merit of having raised awareness for the questions typologists deal with.
<o:p></o:p></span></li></ul>
</ul>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;font-family:"CMU Serif"">For these reasons, I have actually come to see Dunn et al. (2011) as a net-positive.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;font-family:"CMU Serif"">Best – Juergen<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"CMU Serif"">Maslova, E. (2000). A dynamic approach to the verification of distributional universals.
<i>Linguistic Typology</i> 4: 307-333.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica;color:black">Juergen Bohnemeyer (He/Him)<br>
Professor, Department of Linguistics<br>
University at Buffalo <br>
<br>
Office: 642 Baldy Hall, UB North Campus<br>
Mailing address: 609 Baldy Hall, Buffalo, NY 14260 <br>
Phone: (716) 645 0127 <br>
Fax: (716) 645 3825<br>
Email: </span><span style="font-size:11.0pt"><a href="mailto:jb77@buffalo.edu" title="mailto:jb77@buffalo.edu"><span style="font-size:9.0pt;font-family:Helvetica;color:#0078D4">jb77@buffalo.edu</span></a></span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><br>
Web: </span><span style="font-size:11.0pt"><a href="http://www.acsu.buffalo.edu/~jb77/" title="http://www.acsu.buffalo.edu/~jb77/"><span style="font-size:9.0pt;font-family:Helvetica;color:#0563C1">http://www.acsu.buffalo.edu/~jb77/</span></a></span><span style="font-size:9.0pt;font-family:Helvetica;color:black"> <br>
<br>
</span><span style="font-size:11.0pt;color:black">Office hours Tu/Th 3:30-4:30pm in 642 Baldy or via Zoom (Meeting ID 585 520 2411; Passcode Hoorheh) </span><span style="font-size:9.0pt;font-family:Helvetica;color:black"><br>
<br>
There’s A Crack In Everything - That’s How The Light Gets In <br>
(Leonard Cohen) </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="DE" style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:12.0pt;font-family:"CMU Serif""><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Lingtyp <lingtyp-bounces@listserv.linguistlist.org> on behalf of Ian Joo <ian_joo@nucba.ac.jp><br>
<b>Date: </b>Thursday, November 2, 2023 at 15:53<br>
<b>To: </b><LINGTYP@LISTSERV.LINGUISTLIST.ORG><br>
<b>Subject: </b>Re: [Lingtyp] Greenbergian word order universals: confirmed after all<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">Dear Martin,<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">Another recent example of a controversial linguistic paper making it into Nature was Robbeets et al’s (2021) Transeurasian (Altaic) paper.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">The single paper made a claim based on data from three disciplines and - while I cannot speak for the genetics and archaeology - the linguistic data was available only as an online
appendix rather than being scrutinized within the article. And it did not, as argued by Tian et al. (2022), meet the scholarly standards a typical linguistic journal would expect. Despite these problems, being published in Nature itself gave it wide media
coverage all over the world.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">So I wholly agree that a paper should prove its quality in the journal of its own discipline and not in a general science journal. Only after having passed that step can it present
itself to the wider audience of scientists from all fields.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">From Japan,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">Ian<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">- - - - -<br>
JOO, IAN </span><span style="font-size:11.0pt;font-family:"MS Gothic"">朱易安</span><span style="font-size:11.0pt"><br>
Lecturer </span><span style="font-size:11.0pt;font-family:"MS Gothic"">助教</span><span style="font-size:11.0pt"><br>
Faculty of International Studies </span><span style="font-size:11.0pt;font-family:"MS Gothic"">国際学部</span><span style="font-size:11.0pt"><br>
Nagoya University of Commerce and Business </span><span style="font-size:11.0pt;font-family:"MS Gothic"">名古屋商科大学</span><span style="font-size:11.0pt"><br>
Nisshin, Aichi, Japan </span><span style="font-size:11.0pt;font-family:"MS Gothic"">愛知県日進市</span><span style="font-size:11.0pt"><br>
https://ianjoo.github.io<br>
- - - - -<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">2/11/2023
</span><span style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">오후</span><span style="font-size:11.0pt"> 11:21, Martin Haspelmath <martin_haspelmath@eva.mpg.de>
</span><span style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">작성</span><span style="font-size:11.0pt">:<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p style="margin-left:.5in">Dear all, <o:p></o:p></p>
<p style="margin-left:.5in">Twelve years ago, for the first (and so far last) time, typology made it into
<i>Nature</i>, and <i>BBC Online</i> reported at the time: “A long-standing idea that human languages share universal features that are dictated by human brain structure has been cast into doubt.” (<a href="https://www.bbc.com/news/science-environment-13049700">https://www.bbc.com/news/science-environment-13049700</a>).
Our journal <i>Linguistic Typology</i> took this as an opportunity to publish a “Universals Debate” taking up 200 pages (<a href="https://www.degruyter.com/document/doi/10.1515/lity.2011.023/html">https://www.degruyter.com/document/doi/10.1515/lity.2011.023/html</a>).
Younger LINGTYP readers may not remember all this, but a lot of stir was caused at the time by the paper by Dunn et al. (2011), which claimed that "systematic linkages of traits are likely to be the rare exception rather than the rule. Linguistic diversity
does not seem to be tightly constrained by universal cognitive factors“ (<a href="https://www.nature.com/articles/nature09923">https://www.nature.com/articles/nature09923</a>). Their paper argued not only against Chomskyan UG (universal grammar), but also
against the Greenbergian word order universals (Dryer 1992).<br>
<br>
In the meantime, however, it has become clear that those surprising claims about word order universals are not supported – the sample size (four language families) used in their paper was much too small.<br>
<br>
Much less prominently, Jäger & Wahle (2021) reexamined those claims (using similar methods, but many more language families and all relevant
<i>WALS</i> data), finding “statistical evidence for 13 word order features, which largely confirm the findings of traditional typological research” (<a href="https://www.frontiersin.org/articles/10.3389/fpsyg.2021.682132/full">https://www.frontiersin.org/articles/10.3389/fpsyg.2021.682132/full</a>).<br>
<br>
Similarly, Annemarie Verkerk and colleagues (including Russell Gray) have recently reexamined a substantial number of claimed universals on the basis of the much larger Grambank database and found that especially Greenberg’s word order universals hold up quite
well (see Verkerk’s talk at the recent Grambank workshop at MPI-EVA: <a href="https://www.eva.mpg.de/de/linguistic-and-cultural-evolution/events/2023-grambank-workshop/">
https://www.eva.mpg.de/de/linguistic-and-cultural-evolution/events/2023-grambank-workshop/</a>, available on YouTube:
<a href="https://www.youtube.com/playlist?list=PLSqqgRcaL9yl8FNW_wb8tDIzz9R78t8Uk">
https://www.youtube.com/playlist?list=PLSqqgRcaL9yl8FNW_wb8tDIzz9R78t8Uk</a>).<br>
<br>
So what went wrong in 2011? We are used to paying a lot of attention to the “big journals” (<i>Nature, Science, PNAS, Cell</i>), but they often focus on sensationalist claims, and they typically publish less reliable results than average journals (see Brembs
2018: <a href="https://www.frontiersin.org/articles/10.3389/fnhum.2018.00037/full">
https://www.frontiersin.org/articles/10.3389/fnhum.2018.00037/full</a>).<o:p></o:p></p>
<p style="margin-left:.5in">So maybe we should be extra skeptical when a paper is published in a high-prestige journal. But another question that I have is: Why didn’t the authors see that their 2011 results were unlikely to be true, and that their sample size
was much too small? Why didn't they notice that most of the word order changes in their four families were contact-induced? Were they so convinced that their new mathematical method (adopted from computational biology) would yield correct results that they
neglected to pay sufficient attention to the data? Would it have helped if they had submitted their paper to a linguistics journal?<o:p></o:p></p>
<p style="margin-left:.5in">Perhaps I’m too pessimistic (see also this blogpost: <a href="https://dlc.hypotheses.org/2368">
https://dlc.hypotheses.org/2368</a>), but in any event, I think that this intriguing episode (and sobering experience) should be discussed among typologists, and we should learn from it, in one way or another. Advanced quantitative methods are now everywhere
in science, and it seems that they are often misapplied or misunderstood (see also this recent blogpost by Richard McElreath:
<a href="https://elevanth.org/blog/2023/06/13/science-and-the-dumpster-fire/">https://elevanth.org/blog/2023/06/13/science-and-the-dumpster-fire/</a>).<o:p></o:p></p>
<p style="margin-left:.5in">Martin <o:p></o:p></p>
<pre style="margin-left:.5in">-- <o:p></o:p></pre>
<pre style="margin-left:.5in">Martin Haspelmath<o:p></o:p></pre>
<pre style="margin-left:.5in">Max Planck Institute for Evolutionary Anthropology<o:p></o:p></pre>
<pre style="margin-left:.5in">Deutscher Platz 6<o:p></o:p></pre>
<pre style="margin-left:.5in">D-04103 Leipzig<o:p></o:p></pre>
<pre style="margin-left:.5in"><a href="https://www.eva.mpg.de/linguistic-and-cultural-evolution/staff/martin-haspelmath/">https://www.eva.mpg.de/linguistic-and-cultural-evolution/staff/martin-haspelmath/</a><o:p></o:p></pre>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">_______________________________________________<br>
Lingtyp mailing list<br>
Lingtyp@listserv.linguistlist.org<br>
https://listserv.linguistlist.org/cgi-bin/mailman/listinfo/lingtyp<o:p></o:p></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>