FW: "Working Memory"

[Kirschenbaum_Susan]

Into the semantic frey:  I sent the attached message to Christian shortly
after receiving his first  message.  Now, given Dave Klahr's note about
documenting the birth of a technical term/new technical meaning for an old
term, I add it to the discussion.

More than that, I wanted to respond to Chris Schunn's suggestion that "dme"
might be seen as "a hacker's invention" -- I disagree, it is a useful
shorthand for declarative memory element.  Isn't that exactly what the term is
intended to mean?  It is more percise to invent a new term than to try to
redefine and old one, even if some of the associated baggage is "useful and
relevant."  Chris's suggestion that non-ACT-Rers be consulted is a good way to
resolve this question.  Does chunk carry too much baggage or the wrong baggage
(see Wayne's comments re procedural memory)?    Does/can dme, lump, clump,
clod, hunk, gob, nugget, or wad best carry the right, percise, technical
meaning?  My personal vote is for the new term, dme, but I am not a casual or
novice user or reader of this literature.

Susan
_______________________________________________________________________________
From: Kirschenbaum_Susan on Mon, 25 Nov 1996 9:12 am
Subject: RE: "Working Memory"
To: Christian J Lebiere

Christian,

I think this is a good idea.  My personal objection is that the new terms
"addchunk," etc. are longer, giving me more opportunity to make typos.  ;-) 
Seriously, the only real problem that the term "chunk" is used with a slightly
different meaning by other architectures.  This could cause confusion, both
for the researcher who uses both architectures, and for the reader of this
scientific literature.  I wish there were an alternative term such as
"declarative memory element," typed as "DME."

What do you think?

Susan
-----------------------------------------------------------
Susan S. Kirschenbaum, Ph.D.
Code 2214, Building 1171/1
Naval Undersea Warfare Center Division
Newport, RI  02841
Tel: (401) 841-3354   Fax: (401) 841-4749
Kirsch at c223.npt.nuwc.navy.mil