RE: Re (2): Component instead of Configuration/Baseline/Component

   From: Edgar@EdgarSchwarz.de [mailto:Edgar@EdgarSchwarz.de]

   Yesterday a posting told me that 15 is already availabe.
   (For some time already it seems if I look at the DELTA-V page).

Actually, I got the "dates" a bit wrong when I updated
the deltav page (those dates are entered by hand to the html
page)... but after I noticed it, I figured it was
close enough (at least the month was right).

   The introductory part on baselines is much clearer now.

Good!

   Nevertheless I still would like to drop 'configuration' which
   only appears in this context and replace it by 'component'.
   As Geoff seems to be neutral on this topic, I really would
   like to see at least one or two other opinions.

Yes, I am neutral.  I believe Jim Amsden was the only one who
responded so far (and he wanted to keep it "configuration",
because "component" is so overused as a term).

Just to expand a bit on my "neutrality", on one hand, the
term "configuration" emphasizes the fact that it is "a set
of things", but on the other hand, the term "component"
emphasizes the fact that this is something you can plug
in and plug out, which is exactly what you do when you
create and select different baselines for a baselined collection.

So on a purely technical basis, I probably prefer the term
"component", but on an inertial basis (i.e. we've been calling it a
configuration for a while now, and people seem OK with it), I prefer
the term "configuration".  So, either way is fine with me (:-).

Cheers,
Geoff

Received on Thursday, 26 April 2001 12:58:53 UTC