Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Noms #50

Open
BrettRey opened this issue Aug 25, 2022 · 10 comments
Open

Noms #50

BrettRey opened this issue Aug 25, 2022 · 10 comments

Comments

@BrettRey
Copy link
Collaborator

From John Payne: "The one way that CGELBank deviates quite significantly from CGEL itself , it strikes me, is in the treatment of the phrasal category Nom. Quite specifically, Rodney and I did not want CGEL Nom to be identified with the X-bar construct N-bar. Thus in CGEL, it is not the case that Complements are invariably sisters of N and Modifiers are invariably sisters of Nom. If there is just one Modifier, or a Modifier is the lowest dependent, it will be sister of N and daughter of Nom. And if a Complement is not the lowest dependent it will be a sister of Nom. This allows for relatively free ordering of Complements and Modifiers of similar weight (e.g. his exit in haste from the bar) without the necessity for gaps and postposing. It is also compatible with the idea that the distinction between Complements and Modifiers in NP structure is far from secure (no supposed Complements are obligatory; anaphoric one is not an N-bar replacement), as argued explicitly in ‘Anaphoric one and its implications’ (John Payne, Geoffrey K. Pullum, Barbara C. Scholz and Eva Berlage). Language 89.4, 2013, 794-829. Note then that your tree (40) does not reflect CGEL (see CGEL page 1061 for a corresponding CGEL tree). Going back to the N-bar concept strikes me as a retrograde step."

John was the primary author on chapter 5: Nouns and noun phrases. Geoff prefers the N-bar concept but was not an author on chapter 5.

@nschneid
Copy link
Contributor

nschneid commented Aug 25, 2022

Hmm. I can see the logic of the N-bar concept from a theoretical perspective, and if the goal is to keep the number of grammar rules to a bare minimum. From a practical descriptive perspective, it is kind of tedious to have all those extra unary levels. People might find the data easier to understand without them. A script could add them automatically if somebody needed them. Also, the current approach (generalized to VPs as well) creates puzzles like medial Mods in #49.

One option is to revise the Lexical Projection Principle to say that every lexeme (besides Coordinators/Sdrs) projects a phrasal category, which may contain complements OR a modifier (and modifiers always adhere to binary branching). Would that be straightforward to apply or would it open up new questions?

@nschneid
Copy link
Contributor

nschneid commented Aug 25, 2022

Looking at his comment I think he's also saying that Complements should be binary-branching within the Nom, and can interleave with Mods to avoid the need for postposing. (We have one annotation of a postposed Comp in a Nom, 051: "strong hints in the country that..."; and there is "the arrival recently of..." in #49.) I don't have a strong feeling about that but I assume it's different from VP structure (for ditransitives or transitive particle verbs we wouldn't want to introduce additional nesting right?).

@BrettRey
Copy link
Collaborator Author

I've started rereading the Anaphoric one paper. I should have reread it some time ago. I think it will be very helpful here.

@nschneid nschneid mentioned this issue Aug 26, 2022
@nschneid
Copy link
Contributor

It sounds like John is arguing for treating Mods and Comps the same within Noms. A revised approach could be:

  1. Binary Branching Principle: CGELBank branching is no more than binary except in limited circumstances:*

    • Coordinations with more than two coordinates
    • Flat structures
    • Internal complements in VPs (Comp, Obj, Particle, etc.) should be sister to the head V
    • Supplements never add an additional layer and do not count toward the branching limit

    Extra layers are added (typically for Mod) where necessary in order to avoid prohibited ternary+ structures. (But a Mod may also form a binary structure with a lexical head, e.g. [AdjP [Mod:AdvP [Head:Adv very]] [Head:Adj tall]].)

  2. Lexical Projection Principle: Outside of flat structures, and excepting Coordinators and Sdrs, a lexical node almost always projects a phrase of the corresponding category: i.e. N projects Nom (which typically projects NP), V projects VP (which typically projects Clause), P projects PP, Adv projects AdvP, etc. The one exception is that subject-auxiliary inversion targets auxiliaries specifically (rather than the VP they would project in normal position), so if the V_aux in Prenucleus position is monolexemic (not coordinated or modified), it will not project a VP there.

* This assumes that AdjP, AdvP, PP, DP, IntP are more like Noms than VPs—multiple complements (if that ever happens) would be layered.

@nschneid
Copy link
Contributor

nschneid commented Sep 2, 2022

@BrettRey what do you think of the above, with the special exception for auxiliaries?

@BrettRey
Copy link
Collaborator Author

BrettRey commented Sep 3, 2022

Yes, I think this is clear, simple, and accurate. I also think multiple complements are possible: a bet [with Nathan] [for $50] [that multiple complements are possible]

@nschneid
Copy link
Contributor

nschneid commented Sep 3, 2022

Yes, I think this is clear, simple, and accurate.

OK, will work on updating the data

I also think multiple complements are possible: a bet [with Nathan] [for $50] [that multiple complements are possible]

Sorry I meant multiple complements in an AdjP, AdvP, PP, DP, or IntP

@BrettRey
Copy link
Collaborator Author

BrettRey commented Sep 3, 2022

happy [for us] [that we've got this far]

@nschneid
Copy link
Contributor

nschneid commented Sep 3, 2022

OK—would you want those to be layered like in a Nom, or all on the same level like in a VP?

@BrettRey
Copy link
Collaborator Author

BrettRey commented Sep 4, 2022

Layered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants