TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Knowledge versus Information From:Tim Altom <taltom -at- IQUEST -dot- NET> Date:Thu, 23 Apr 1998 14:29:58 -0400
>So, you are saying that the distinction between information and
>knowledge is information, but not knowledge?
No, I'm not. I'm saying that the distinction is an interesting parlor game,
but little more. From the user's viewpoint, whatever is needed at a specific
moment is "information" but only because someone before me used
"information" in this context to mean "anything that reduces uncertainty".
We could apply a wholly new name if we wished, but that's a little extreme
(infopoint? knowledgenubbin?). Regardless of the noun, we shouldn't be so
taken with subdividing concepts that we forget that we're doing it as an
interesting diversion and lose track of how users apply the concepts.
>Office:mike -dot- huber -at- software -dot- rockwell -dot- com
>Home:nax -at- execpc -dot- com
Simply Written, Inc.
Creators of the Clustar Method for task-based documentation