The Merge Conspiracy [Part 3]

Part 2 and a half showed us the consequences of the MSO-Merge correspondence, both good and bad. In an ideal world, there should be a way to curtail the bad without limiting the good. Alas, ever since J.J. Abrams got his hands on Star Trek I have been uncertain about the degree of idealness of the world we inhabit.

The Merge Conspiracy [Part 2.5]

Yesterday we learned that a constraint can be expressed by Merge iff it can be defined in monadic second-order logic. But is this a good thing or a bad thing? The answer is both.

The Merge Conspiracy [Part 2]

Last time in our riveting story of intrigue and cabal, the seemingly innocuous subcategorization requirements encoded via Merge turned out to have a kinky bent to them: by splitting categories into smaller subcategories, we can regulate dependencies such as case-marking and gender agreement using only Merge. But the rabbit hole goes a lot deeper... ... ... ... (in fact, it is so deep I decided to pull a Wachowski and save the second half of the post for tomorrow).

The Merge Conspiracy [Part 1]

A while ago, Norbert wrote several interesting posts regarding the Specifier Island Constraint (SPIC) that caused me to chime in with some technical observations. The basic upshot was that SPIC cannot reliably block extraction from a specifier because we can use Merge rather than Move to displace constituents, in which case SPIC does not apply. Since the comments section isn't the ideal place for discussing such technical matters in an accessible form, Norbert was so kind to endow me with the divine power of publishing my remarks directly on his blog. So here's the first entry of a three part epic, the story of the power of Merge and how it can be used for both good and evil (rated PG-13 for some technical details; but hey, we're all grown-ups here).