On Thu, 24 Jun 1999, Josh Arnold wrote:
> Faber Fedor wrote:
> > At 10:35 PM 6/24/99 -0400, Richard Rager wrote:>
%< cut >%
> > I think Richard has a point, namely, do we test for jargon?
> >
> > I can see why we should, but I don't see how. I, for one, would not trust
> > an admin who didn't know the difference between an MUA and and MAU.
>
> I don't see any point in testing for "jargon". We should simply use the
> appropriate acronyms in the tests and then the curricula can address it as
> needed.
I agree that it is probably not a good idea to ask questions like: "what
is MUA an abbreviation of? a) b) c) d)". However, I think Richard
brought up an important issue: which acronyms shall we use in the test
items? People unfamiliar with the acronyms probably will not understand
the question, so indirectly we test their knowledge of it. Now I don't
like to put that in the test objectives, but we have to decide on some
policy and maybe even make a list of acronyms we might use in the tests
(if any). Note that training organisations need to have a clue what
acronyms to explain, because nobody is going to know what is in the tests.
--
#>!$!%(@^%#%*(&(#@#*$^@^$##*#@&(%)@**$!(&!^(#((#&%!)%*@)(&$($$%(@#)&*!^$)^@*^@)
Tom "thriving on chaos" Peters
NL-1062 KD nr 149 tel. 31-204080204
Amsterdam e-mail [EMAIL PROTECTED]
________________________________________________________________________
This message was sent by the linux-cert-program mailing list. To unsubscribe:
echo unsubscribe | mail -s '' [EMAIL PROTECTED]
