Lists Home |
Date Index |
- From: "Steven R. Newcomb" <email@example.com>
- To: firstname.lastname@example.org
- Date: Thu, 2 Apr 1998 15:20:21 -0500
[Paul Prescod <email@example.com>:]
> That's right. That's why people get so confused about them. The word
> inheritance is inherently misleading when applied to architectural
Paul is absolutely right, but I'm still not going to take his advice.
For several months last year, I deliberately stopped using the
word "inherit", as in "inheriting architecture", "inherited-from
architecture", etc. Instead, I very carefully used the words
"derived" for the inheriting architecture and "enabling" for the
inherited architecture. This is the vocabulary used in the standard.
Ultimately, however, I reluctantly gave up on precision vocabulary
because nobody understood what I was talking about, except for people
whom I had no need to reach because they already understood the
concepts. In almost all rhetorical situations, I have to use
vocabulary that may be, strictly speaking, misleading, and yet
provides some glimmer of understanding to the HyTime-inexperienced.
I'm back to "inherited" and "inheriting", and I never even try to use
"enabling" and "derived" any more. I'm open to other suggestions,
though. Got any?
Steven R. Newcomb, President, TechnoTeacher, Inc.
firstname.lastname@example.org http://www.techno.com ftp.techno.com
voice: +1 972 231 4098 (at ISOGEN: +1 214 953 0004 x137)
fax +1 972 994 0087 (at ISOGEN: +1 214 953 3152)
3615 Tanner Lane
Richardson, Texas 75082-2618 USA
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)