09.07.2015 Views

Practical Information - Generative Linguistics in the Old World

Practical Information - Generative Linguistics in the Old World

Practical Information - Generative Linguistics in the Old World

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The absence of coreferential subjects <strong>in</strong> TP coord<strong>in</strong>ationBronwyn M. Bjorkman (University of Toronto)S<strong>in</strong>ce Ross (1967) much work on <strong>the</strong> syntax of coord<strong>in</strong>ation has been concerned with <strong>the</strong> conditionsgovern<strong>in</strong>g optionally “shared” material between twoconjuncts.Muchlessattentionhasbeen given, however, to cases <strong>in</strong> which such shar<strong>in</strong>g is obligatory. This paper <strong>in</strong>vestigates arequirement of this k<strong>in</strong>d, previously undiscussed <strong>in</strong> <strong>the</strong> literature, govern<strong>in</strong>g <strong>the</strong> availability ofcoreferential subjects <strong>in</strong> coord<strong>in</strong>ated clauses. I argue that thisrequirementarisesduetoconditionsgovern<strong>in</strong>g <strong>the</strong> l<strong>in</strong>earization of multidom<strong>in</strong>ant structures for coord<strong>in</strong>ation.Puzzle: As (1a) shows, English generally allows coord<strong>in</strong>ated clausestohavecoreferentialsubjects,though coord<strong>in</strong>ation below a s<strong>in</strong>gle subject, as <strong>in</strong> (1b), is sometimes preferred.(1) a. [Alice i always wanted a car] and [she i f<strong>in</strong>ally bought one last year.]b. Alice [always wanted a car] and [f<strong>in</strong>ally bought one last year.]Strik<strong>in</strong>gly, such coreferential subjects become ungrammatical no longer available <strong>in</strong> a questionis formed by Across-<strong>the</strong>-Board (ATB) Wh-movement, as <strong>in</strong> (2a). Coord<strong>in</strong>ation of a smallerconstituent, as <strong>in</strong> (2b), becomes <strong>the</strong> only available structure.(2) a. *What k did [Alice i always want t k ]and[she i f<strong>in</strong>ally buy t k last year]? (cf. (1a))b. What k did Alice [always want t k ]and[f<strong>in</strong>allybuyt k last year]? (cf. (1b))We f<strong>in</strong>d <strong>the</strong> same ban on coreferential subjects <strong>in</strong> coord<strong>in</strong>ationembeddedbelowanobligatorycomplementizer, as <strong>in</strong> (3), demonstrat<strong>in</strong>g that this restriction cannot be attributed simplyto properties of ATB movement. The embedd<strong>in</strong>g environment allows us to see also, moreover,that though coreferential subjects are excluded below a s<strong>in</strong>gle shared complementizer <strong>in</strong> (3a),<strong>the</strong>y are once more possible when <strong>the</strong> complementizer is also repeated, as <strong>in</strong> (3c).(3) The TSA asks. . .a. * that [passengers i remove <strong>the</strong>ir shoes] and [<strong>the</strong>y i move quickly through security].b. that passengers [remove <strong>the</strong>ir shoes] and [move quickly through security].c. [that passengers i remove <strong>the</strong>ir shoes] and [that <strong>the</strong>y i move quickly through security].These data cannot be accounted for by a general requirement that conjuncts be as small aspossible: such a restriction would be unable to account for <strong>the</strong> grammaticality of ei<strong>the</strong>r (1a) or(3c), <strong>in</strong> which both conjuncts conta<strong>in</strong> identical or coreferential material at <strong>the</strong>ir left edge. Whatunifies <strong>the</strong> ungrammatical sentences <strong>in</strong> (2a) and (3a) is that both exhibit coreferential subjectsbelow a s<strong>in</strong>gle shared element <strong>in</strong> C 0 (an <strong>in</strong>verted auxiliary <strong>in</strong> (2a), and that <strong>in</strong> (3a)). In o<strong>the</strong>rwords, it is <strong>the</strong> subjects of coord<strong>in</strong>ated TPs that cannot corefer.Proposal: Iarguethatthisrestrictiononcoreferencecanbeaccountedforby<strong>in</strong>dependentconditionson l<strong>in</strong>earization, specifically <strong>the</strong> l<strong>in</strong>earization of multidom<strong>in</strong>antstructures. Thelimitationof <strong>the</strong> ban to TP conjuncts, meanwhile, can be attributed to <strong>the</strong> cyclic nature of l<strong>in</strong>earization(Fox and Pesetsky, 2005, a.o.).First, <strong>the</strong> ban on coreference itself. Multidom<strong>in</strong>ant representations, <strong>in</strong> which a s<strong>in</strong>gle constituentoccupies two (or more) dist<strong>in</strong>ct syntactic positions, nei<strong>the</strong>r of which c-commands <strong>the</strong>o<strong>the</strong>r, have been argued to exist <strong>in</strong> coord<strong>in</strong>ate structures at least s<strong>in</strong>ce Moltmann (1992). ?proposes that multidom<strong>in</strong>ant representations are constra<strong>in</strong>ed, however, by whe<strong>the</strong>r <strong>the</strong>y can bel<strong>in</strong>earized. More specifically, Citko proposes that a multiply-dom<strong>in</strong>ated element cannot be l<strong>in</strong>earized<strong>in</strong> situ, andthusisonlygrammaticalwhenitundergoessubsequentmovement to somehigher position – as <strong>in</strong> ATB Wh-movement.The ungrammaticality of (2a) and (3a), can be expla<strong>in</strong>ed by Citko’s proposal, if we make <strong>the</strong>s<strong>in</strong>gle assumption that coreferential subject DPs <strong>in</strong> coord<strong>in</strong>ated clauses are representationallyequivalent to a s<strong>in</strong>gle multiply-dom<strong>in</strong>ated subject DP. In o<strong>the</strong>r words, <strong>the</strong> process of l<strong>in</strong>earizationcannot dist<strong>in</strong>guish <strong>the</strong> representation <strong>in</strong> (4a) from <strong>the</strong> representation <strong>in</strong> (4b):1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!