Show Summary Details

Page of

PRINTED FROM OXFORD HANDBOOKS ONLINE ( © Oxford University Press, 2018. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Handbooks Online for personal use (for details see Privacy Policy and Legal Notice).

date: 15 August 2020

Abstract and Keywords

Canonical transitive events involve a volitional and controlling agent and a thoroughly affected patient. Any deviation from this prototype may result in a change in the coding of the denoted event. Case plays a central role in this process: accusative marking of patients (nom-acclanguages) and ergative marking of agents (abs-erg-languages) are usually associated with the coding of prototypical transitive events, while other case frames (such as nom-dat/ins or abs-dat/ins) usually code events with a decreased degree of transitivity. The changes in the case marking of (core) arguments may be motivated basically in two ways. First, the changes may follow from verbal morphology as is the case with such derived constructions as passive and antipassive. Second, the changes may follow independently of verb morphology. This article focuses on transitive clauses and the changes in the marking of agent and patient arguments. It first discusses the relation between case marking and transitivity from a formal perspective, and then considers the semantics of case in transitivity alternations.

Keywords: case, transitivity, agent, patient, verb morphology, transitive clauses, case marking, semantics, transitivity alternations

Access to the complete content on Oxford Handbooks Online requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can''t find the answer there, please contact us.