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: 05 December 2020

Abstract and Keywords

This chapter provides a review of research on morphological aspects of first language (L1) attrition, focusing on derivational and inflectional morphology in various languages. Morphological attrition is considered from perspectives of the Markedness Theory (e.g., Sharwood Smith, 1994), Regression Hypothesis (e.g., Keijzer, 2010a), Activation Threshold Hypothesis (e.g., Paradis, 2007), Interface Hypothesis (e.g., Sorace, 2011), and 4-M Model (e.g., Myers-Scotton & Jake, 2017). Two main directions in accounting for differential susceptibility of morphemes to attrition are identified: a) focus on inherent properties of morphemes; and b) focus on mechanisms underlying morphological processing. The chapter concludes by considering challenges faced by morphological studies, including lack of consistency in types of informants, data, and data collection techniques, and limitations of the available theoretical approaches for the analysis of the complexity and variety of morphological operations and morphemes that become restructured, modified, and ultimately lost in the course of L1 attrition.

Keywords: derivational, inflectional, morphology, markedness, regression, Activation Threshold, interface, 4-M Model

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.