2011
DOI: 10.1007/s11049-011-9155-z
|View full text |Cite
|
Sign up to set email alerts
|

Asymmetries between person and number in syntax: a commentary on Baker’s SCOPA

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

2
34
0

Year Published

2011
2011
2024
2024

Publication Types

Select...
8
1

Relationship

1
8

Authors

Journals

citations
Cited by 43 publications
(36 citation statements)
references
References 25 publications
2
34
0
Order By: Relevance
“…In sum, while there are many possible explanations for the fact that an intended agreement pattern fails to surface (Preminger 2011a, 2011b, Bock and Middleton 2011, interface or performance factors are particularly likely reasons for such a failure. This is especially true when the agreement controller and its target are in a specifier-head relationship, since this is considered the strongest context for agreement to surface (Franck et al 2006).…”
mentioning
confidence: 99%
“…In sum, while there are many possible explanations for the fact that an intended agreement pattern fails to surface (Preminger 2011a, 2011b, Bock and Middleton 2011, interface or performance factors are particularly likely reasons for such a failure. This is especially true when the agreement controller and its target are in a specifier-head relationship, since this is considered the strongest context for agreement to surface (Franck et al 2006).…”
mentioning
confidence: 99%
“…As Nevins (: 952) puts it, ‘Person‐Case Constraints, while very widespread, never find a parallel in Number‐Case Constraints’ (cf. also Baker ; Preminger 2011b). This is also true for Hittite.…”
Section: The Person Case Constraint In Hittitementioning
confidence: 96%
“…As noted by Preminger (2011b), this requirement appears to be a sui generis requirement on marked features, which does which does not extend to other ϕ-feature classes ( , (pace Baker 2008).…”
Section: X43 the Formal Agreement Requirement On 1st/2nd Person Promentioning
confidence: 96%
“…or (28) will correctly rule out cases like (26), but it leaves open the question of how the local direct object pronoun in the infinitival clause in (25) satisfies its licensing requirements. SeePreminger (2011b) for an explanation based on locality.…”
mentioning
confidence: 99%