CAS LX 522 Syntax IRecap: featuresRecap: uninterpretable featuresRecap: Matching and CheckingRecap: MergeRecap: Adjoin, Agree, HoPMovePat ate lunchSlide 9Slide 10Slide 11Interlude: What happens when V moves to v?Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Back to our story…Pat was not eating lunch.French vs. EnglishSlide 24V raises to T in FrenchJean (ne) téléphone pas MarieSlide 27Slide 28Slide 29Slide 30SwedishTypology of verb/aux raisingIrishSlide 34SVO to VSOFrench vs. IrishParametric differencesdo-supportSlide 39PTRSlide 41Pat did not call ChrisSlide 43Pat never called ChrisEpisode 6a. Head movementEpisode 6a. Head movement5.4-5.55.4-5.5CAS LX 522CAS LX 522Syntax ISyntax IRecap: featuresRecap: featuresThe The lexiconlexicon contains bundles of features. These contains bundles of features. These feature bundles are assembled by a computational feature bundles are assembled by a computational process into syntactic structures for interpretation by process into syntactic structures for interpretation by the conceptual-intensional an articulatory-perceptual the conceptual-intensional an articulatory-perceptual systems.systems.Among these features, we haveAmong these features, we haveInterpretable featuresInterpretable features (such as the category feature that (such as the category feature that determines the category of the lexical item)determines the category of the lexical item)Uninterpretable featuresUninterpretable features (such as the selectional feature (such as the selectional feature [[uuN] on a transitive verb). Uninterpretable features are N] on a transitive verb). Uninterpretable features are intolerable at the interfaces, and must be removed (by intolerable at the interfaces, and must be removed (by checkingchecking) or the derivation crashes.) or the derivation crashes.Recap: uninterpretable featuresRecap: uninterpretable featuresUninterpretable features vary along two dimensions. Uninterpretable features vary along two dimensions. PrivativePrivative vs. vs. unvaluedunvalued and and strongstrong vs. vs. weakweak..Privative featuresPrivative features (such as [ (such as [uuN]) which are checked by N]) which are checked by matching features (such as [N] or [matching features (such as [N] or [uuN]).N]).Unvalued featuresUnvalued features (such as [uInfl:]) which are checked by (such as [uInfl:]) which are checked by features that can provide a value (such as [tense:past]).features that can provide a value (such as [tense:past]).StrongStrong uninterpretable features can only be checked if they uninterpretable features can only be checked if they are are locallocal (sister) to the feature that checks them. (sister) to the feature that checks them.WeakWeak uninterpretable features can be “checked at a distance.” uninterpretable features can be “checked at a distance.”Strong features can force movement, but because the Strong features can force movement, but because the system is economical (lazy), no movement is allowed system is economical (lazy), no movement is allowed just to check a weak feature.just to check a weak feature.Recap: Matching and CheckingRecap: Matching and CheckingCheckingChecking is relation between an uninterpretable is relation between an uninterpretable feature and a feature and a matching matching feature, allowing the feature, allowing the uninterpretable feature to be ignored at the interface.uninterpretable feature to be ignored at the interface.For two features to match:For two features to match:One must c-command the other.One must c-command the other.There must not be a closer feature that could match. (p218)There must not be a closer feature that could match. (p218)[[uuF] … [F] … [F]F] … [F] … [F][F] … [F] … [[F] … [F] … [uuF]F]If the uninterpretable feature is strong, the matching If the uninterpretable feature is strong, the matching feature must be local (e.g., a feature of the sister) in feature must be local (e.g., a feature of the sister) in order for the uninterpretable feature to be checked.order for the uninterpretable feature to be checked.For [For [uuV*V*] on ] on vv, it matches the [V] feature of the verb below , it matches the [V] feature of the verb below it, then the verb must move up to it, then the verb must move up to vv to check [ to check [uuV*V*].].For [For [uuInfl:*Infl:*] on an auxiliary, the [tense:past] feature (above ] on an auxiliary, the [tense:past] feature (above it) matches it and values it, then the auxiliary must move it) matches it and values it, then the auxiliary must move up to T for the feature to be checked.up to T for the feature to be checked.Recap: MergeRecap: MergeMergeMerge: create a new syntactic object from two existing : create a new syntactic object from two existing syntactic objects, with the label (features) syntactic objects, with the label (features) projectingprojecting from one. Merge happens for one of two reasons:from one. Merge happens for one of two reasons:To check an uninterpretable featureTo check an uninterpretable feature: the label of the : the label of the one with the uninterpretable feature projects.one with the uninterpretable feature projects.Now that we have strong features, we will consider Now that we have strong features, we will consider selectional features to be strong features, i.e. [selectional features to be strong features, i.e. [uuN*], checked N*], checked locally under sisterhood created by Merge.locally under sisterhood created by Merge.To satisfy the Hierarchy of ProjectionsTo satisfy the Hierarchy of Projections: the label of : the label of the higher one in the hierarchy projects and no the higher one in the hierarchy projects and no features are checked.features are checked.This only happens once all of the strong uninterpretable This only happens once all of the strong uninterpretable features in the non-projecting object have been checked (and features in the non-projecting object have been checked (and any adjunctions to be done have been done)any adjunctions to be done have been done)Recap: Adjoin, Agree, HoPRecap: Adjoin, Agree, HoPAdjoinAdjoin is like Merge, but it does not result in the is like Merge, but it does not result in the checking of a feature.checking of a feature.Merge always takes priority over Adjoin, so Adjoin Merge always takes priority over Adjoin, so Adjoin only happens once the (strong)
View Full Document
![Nom from finite T no case from nonfinite T (T [inf], M to)](https://media.gradebuddy.com/documents/386389/7a3e15e0-7507-4825-a32d-f3e6fb67d2eb.png)
Unlocking...