06.04.2013 Views

Johnson 2004 - CDLI - UCLA

Johnson 2004 - CDLI - UCLA

Johnson 2004 - CDLI - UCLA

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.

this chapter. And, it is, after all, a syntactic pattern familiar from the center-embedding<br />

genitive construction in Sumerian.<br />

Example Syntactic form Genitive parallel<br />

13 [PP Loc bi 2]-√ [NP-Loc]<br />

14 [PP Loc/Erg NP Bare bi 2]-√ [NP NP-Gen]<br />

15 [PP Loc/Erg [PP LocTerm NP Bare (bi 2)] bi 2]-√ [NP [NP NP-Gen]-Gen]<br />

As I will argue in explicit terms later on, a number of factors indicate that the *bi-√ prefix<br />

is quite similar to the expletive there in English existential sentences such as “there is a<br />

dog in the parlor.” This obviously corresponds in certain respects to the traditional notion<br />

that the *bi-√ prefix “agrees” with a locative argument, but I would like to emphasize two<br />

fundamental distinctions before moving on to the next section. If the *bi-√ prefix is<br />

similar to the expletive there in English existential sentences, then one might expect it to<br />

regularly occur with locative arguments. But it needs to be remembered that there does<br />

not agree with the locative it occurs with, it simply occurs in certain syntactic<br />

configurations that also typically include locative arguments. In other words, it is a matter<br />

of syntax rather than a morphologically-driven agreement relation that holds between a<br />

morpheme on the verb and a locative phrase in the clause. The other difference between<br />

the traditional agreement-based interpretation and my suggestion that the bi-√ prefix is<br />

analogous to expletive “there” is that the use of expletive “there” in English has far<br />

reaching syntactic implications for case-marking, quantification and focus constructions.<br />

44

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

Saved successfully!

Ooh no, something went wrong!