JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for WORDGRAMMAR Archives


WORDGRAMMAR Archives

WORDGRAMMAR Archives


WORDGRAMMAR@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

WORDGRAMMAR Home

WORDGRAMMAR Home

WORDGRAMMAR  2002

WORDGRAMMAR 2002

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

admissibility of traces/chains in WG?

From:

And Rosta <[log in to unmask]>

Reply-To:

Word Grammar <[log in to unmask]>

Date:

Fri, 28 Jun 2002 18:18:24 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (61 lines)

Given Dick & Chet's paper on null words, I wonder whether traces/
chains are thereby not necessarily beyond the pale any longer.

They would be fundamentally different in kind from the 'deletions'
(as I would analyse them) discussed in the paper, since they
would involve something like a dependency between two positions,
the import of the dependency being that the filler of the
one position is the filler of the other. But I wonder whether
now that the pandora's box of nonconcreteness has been opened,
the old arguments against traces/chains still hold the same force.

You might reply "But WG has a perfectly good mechanism for
handling extraction phenomena, so why add the complication of
traces?". To this reply, I suggest we compare the following
two models:

A. Standard current WG: dependencies may be 'above the line'
or 'below the line'. Formally this can be modelled by
treating 'above the line' as a relational type in its own
right (called 's-dependency' and 'subordinate' by me in
past work).
  The essence of this view is that the grammar creates
two structures, a hierarchical subordination structure, and
a tangling dependency structure in which words' dependency
requirements are satisfied by other words, and imposes
constraints on the correspondence between these two
structures.

B. Alternative: standard dependencies are all 'above the
line' relations between positions (in which case there is
no need to distinguish dependency from subordination).
Positions can be directly associated with a filler. Or
they can be linked by a 'cofilled' relation to another
position -- handling extraction and control/raising. Or,
arguably, they can simply be unfilled -- handling such
things as "He ate __ (off the plate)".
  The essence of this view is that a word's dependency
requirements create a set of positions, with hierarchical
structure falling out naturally from this. A separate
body of rules and representations governs how these
positions are 'filled'.

The advantage of A is that it requires no distinction between
position and filler. The advantages of B (besides being more
efficacious expositively and pedagogically) are that it
allows for the possibility of unfilled positions, that it
is conceptually more 'explanatory' (i.e. begs fewer questions),
and that by allowing 'traces', affords a way of representing
the nested dependency constraint on multiple extractions.

It's not clear to me that A is cognitively superior in the
sense of there being better extralinguistic analogues. What
are the analogues of the dependency--subordination distinction
(or above/below the line)? Contrastingly, extralinguistically
the distinction between a space/place and the occupancy of
the space is pretty straightforward: we can distinguish
between places that are occupied, places that are unoccupied
but owned, and places that are neither occupied nor owned.

--And.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
June 2021
October 2020
April 2020
March 2020
September 2019
June 2019
May 2019
April 2019
December 2018
September 2018
August 2018
July 2018
June 2018
April 2018
June 2017
April 2017
March 2017
February 2017
January 2017
December 2016
September 2016
August 2016
July 2016
June 2016
February 2016
November 2015
July 2015
April 2015
March 2015
February 2015
September 2014
August 2014
July 2014
June 2014
May 2014
March 2014
February 2014
October 2013
July 2013
June 2013
April 2013
March 2013
February 2013
January 2013
February 2012
February 2011
January 2011
June 2010
April 2010
March 2010
December 2009
August 2009
June 2009
April 2009
March 2009
February 2009
November 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
December 2007
October 2007
September 2007
August 2007
July 2007
June 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager