1887
Volume 14, Issue 2
  • ISSN 2211-6834
  • E-ISSN: 2211-6842
GBP
Buy:£15.00 + Taxes

Abstract

Many morphologically ergative languages display asymmetries in the extraction of core arguments: while absolutive arguments (transitive objects and intransitive subjects) extract freely, ergative arguments (transitive subjects) cannot. This falls under the label “syntactic ergativity” (see, e.g. Dixon 1972, 1994; Manning 1996; Polinsky to appear(b)). These extraction asymmetries are found in many languages of the Mayan family, where in order to extract transitive subjects (for focus, questions, or relativization), a special construction known as the “Agent Focus” (AF) must be used. These AF constructions have been described as syntactically and semantically transitive because they contain two non-oblique DP arguments, but morphologically intransitive because the verb appears with only a single agreement marker and takes an intransitive status suffix (Aissen 1999; Stiebels 2006). In this paper we offer a proposal for (i) why some morphologically ergative languages exhibit extraction asymmetries, while others do not; and (ii) how the AF construction in Q’anjob’al circumvents this problem. We adopt recent accounts which argue that ergative languages vary in the locus of absolutive case assignment (Aldridge 2004, 2008a; Legate 2002, 2008), and propose that this variation is present within the Mayan family. Based primarily on comparative data from Q’anjob’al and Chol, we argue that the inability to extract ergative arguments does not reflect a problem with properties of the ergative subject itself, but rather reflects locality properties of absolutive case assignment in the clause. We show how the AF morpheme -on circumvents this problem in Q’anjob’al by assigning case to internal arguments.

Loading

Article metrics loading...

/content/journals/10.1075/lv.14.2.01coo
2014-01-01
2018-09-21
Loading full text...

Full text loading...

References

http://instance.metastore.ingenta.com/content/journals/10.1075/lv.14.2.01coo
Loading
Keyword(s): case
This is a required field
Please enter a valid email address
Approval was successful
Invalid data
An Error Occurred
Approval was partially successful, following selected items could not be processed due to error