search

langsci / 163

A lexicalist account of argument structure
1 stars 0 forks source link

Inheritance (p. 27) [via PaperHive@docloop] #278

Open docloop[bot] opened 5 years ago

docloop[bot] commented 5 years ago

Annotation imported from PaperHive.

Regarding this part:

a conflict

Remi van Trijp wrote:

I don't understand this argument. I am not necessarily a fan of inheritance (multiple inheritance can be a mess), but there are several solutions for conflict resolution in inheritance-based systems, and default inheritance allows information to be locally overridden.

_Link to original comment. About docloop._

docloop[bot] commented 5 years ago

Annotation imported from PaperHive.

Stefan Müller wrote:

The point is that conflict resolution does not help here. You need embedding. Something that is inherited from something else has to go inside the other thing. So inheriting A and B is neither A nor B. We are not talking about the Nixon Diamond here. The result of inheritance should be A applied to B (or B applied to A). I think this is in the text already and I am a bit frustrated since I do not know how to make this clearer. PS: I do know default unification. Actually my work on Adele's paper on Persian (Words by default) was the result of a seminar on Defaults in Linguistics I gave 2006 in Potsdam. HPSG has pretty cool papers on default inheritance. Lascarides, Alex & Ann Copestake. 1999. Default Representation in Constraint-Based Frameworks. Com- putational Linguistics 25(1). 55–105.

_Link to original comment. About docloop._