RE: A little respect for "unvalidated"

Subject: RE: A little respect for "unvalidated"
From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
To: Dan Goldstein <DGoldstein -at- riverainmedical -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Mon, 21 Sep 2009 15:27:22 -0400

Dan Goldstein observed:

> In my line of work (medical devices), the meaning of "unvalidated" is
> crystal clear. If that's true only for one industry, then
> let's call it
> jargon and I'll stop hockin' the dictionaries' chainik.
> On the other hand, if its meaning is clear over a broad range of
> technical fields (your NIST example below) then it's an omission.

Ok, if a word is in frequent use in your industry, and isn't a stupidity (many words that occur on radio and TV are stupidities in the sense that somebody mis-heard or mispronounced something at some point and others have been slavishly mimicing ever since) then you use the word as found. People expect it and know what you mean when you use it. All together now: nook-you-lur!

But my question was aimed at the larger context of how we use the language in technical communication.

If I have a word that indicates a condition or state or attribute, and then I have reason to mention the "not" of that condition, and if "the not validated HSMs" is rather awkward-sounding and awkward to scan, then do some list members think I can/should use "unvalidated"? Or should I use "non-validated"? Or should I use some other prefix that eludes me just now? Or should I stick with "the not validated HSMs" regardless of how clunky?

Generalize to any other word-and-prefix combo you think would make a good example or a good point.

As for me, I just go with "unvalidated".

- Kevin

The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.


Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices.

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:

A little respect for "unvalidated": From: Dan Goldstein
RE: A little respect for "unvalidated": From: McLauchlan, Kevin
RE: A little respect for "unvalidated": From: Dan Goldstein

Previous by Author: RE: A little respect for "unvalidated"
Next by Author: RE: A little respect for "unvalidated"
Previous by Thread: RE: A little respect for "unvalidated"
Next by Thread: Re: A little respect for "unvalidated"

What this post helpful? Share it with friends and colleagues:

Sponsored Ads