26.01.2013 Views

Presuppositions in Spoken Discourse

Presuppositions in Spoken Discourse

Presuppositions in Spoken Discourse

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Accommodation and Presupposition<br />

It should be clear that the ma<strong>in</strong> problem with Zeevat and Blutner’s<br />

explanation lies <strong>in</strong> the def<strong>in</strong>ition of expression alternatives, <strong>in</strong> particular the role of<br />

the <strong>in</strong>put context <strong>in</strong> their identification. If we require the same <strong>in</strong>put context, we<br />

can predict correctly that factives will accommodate, but we will also predict<br />

<strong>in</strong>correctly that too should be able to accommodate as well. On the other hand, if<br />

we loosen our requirement on the <strong>in</strong>put context, we can correctly predict that the<br />

presuppositions triggered too will not accommodate, but we now <strong>in</strong>correctly predict<br />

that presuppositions triggered by factives should not accommodated either. Even if<br />

we know more about alternatives, I don’t see how we can ever get this explanation<br />

to account for the behavior of factives and too simultaneously.<br />

We saw <strong>in</strong> the examples <strong>in</strong> (23) and the OT analysis that the proposal can<br />

expla<strong>in</strong> why def<strong>in</strong>ite NPs do not accommodate well, and this explanation predicts<br />

the same result regardless of the effect of the <strong>in</strong>put context on alternatives. If <strong>in</strong>put<br />

contexts affect alternatives, then def<strong>in</strong>ite NPs will either be bound or won’t<br />

compete with the <strong>in</strong>def<strong>in</strong>ite. If we use a looser def<strong>in</strong>ition, then the <strong>in</strong>def<strong>in</strong>ite will<br />

always w<strong>in</strong> because the def<strong>in</strong>ite will be penalized by AVOIDACCOMMODATION.<br />

Here the account makes the correct predictions. Unfortunately, big def<strong>in</strong>ite NPs<br />

accommodate well, and no matter how we def<strong>in</strong>e alternatives <strong>in</strong> relation to the<br />

<strong>in</strong>put we can’t expla<strong>in</strong> this.<br />

Zeevat recognized this and <strong>in</strong> order to deal with big def<strong>in</strong>ite NPs he develops<br />

a detailed proposal for what constra<strong>in</strong>ts are at work <strong>in</strong> the generation of NP forms.<br />

These depend on the characteristics of the referent of the NP <strong>in</strong> the context <strong>in</strong><br />

which it is used (see Zeevat, to appear) and are <strong>in</strong> the form of parse constra<strong>in</strong>ts.<br />

Parse constra<strong>in</strong>ts <strong>in</strong> OT are constra<strong>in</strong>ts that say what features present <strong>in</strong> the <strong>in</strong>put<br />

must be marked <strong>in</strong> generated forms. One of the parse constra<strong>in</strong>ts he proposes is<br />

PARSEUNIQUE. In generation, PARSEUNIQUE will demand that unique NPs are<br />

marked for their uniqueness, and this is satisfied by us<strong>in</strong>g a def<strong>in</strong>ite article.<br />

Therefore only non-unique def<strong>in</strong>ites have <strong>in</strong>def<strong>in</strong>ites as assertional alternatives.<br />

This then expla<strong>in</strong>s why big def<strong>in</strong>ite NPs are able to accommodate easily, because<br />

the additional <strong>in</strong>formation that makes them “big”, also makes them unique <strong>in</strong> their<br />

context, and an <strong>in</strong>def<strong>in</strong>ite would not be a w<strong>in</strong>n<strong>in</strong>g candidate because it wouldn’t<br />

fulfill the parse requirement. Zeevat even explicitly states that only unique def<strong>in</strong>ites<br />

can accommodate. 10<br />

This explanation is problematic for two reasons. The first reason is that a<br />

majority of def<strong>in</strong>ite NPs refer to referents that are unique <strong>in</strong> their context, but only<br />

big NPs tend to be used to <strong>in</strong>troduce discourse-new <strong>in</strong>formation. With the addition<br />

of this constra<strong>in</strong>t, however, most def<strong>in</strong>ite NPs should be able to accommodate,<br />

even small def<strong>in</strong>ite NPs. Potentially, we could say that the bigger the NP is, the<br />

more unique it must be because we have more specific <strong>in</strong>formation, but this would<br />

seem to be just a rework<strong>in</strong>g of van der Sandt’s descriptive content explanation <strong>in</strong><br />

the form of an OT parse constra<strong>in</strong>t. The second reason why this explanation is<br />

10 The order<strong>in</strong>g for the constra<strong>in</strong>ts considered relevant for choices between def<strong>in</strong>ite descriptions<br />

and <strong>in</strong>def<strong>in</strong>ites are PARSEOLD >> PARSEUNIQUE and then AVOIDACCOMMODATION .<br />

127

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

Saved successfully!

Ooh no, something went wrong!