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: Information -- a working definition? From:Milan Davidović <milan -dot- lists -at- gmail -dot- com> To:Damien Braniff <Damien -dot- Braniff -at- asg -dot- com> Date:Thu, 17 Jun 2010 08:25:25 -0400
On Thu, Jun 17, 2010 at 4:44 AM, Damien Braniff <Damien -dot- Braniff -at- asg -dot- com> wrote:
> But why information? Why not knowledge, after all we now have "knowledge managers"?
On this occasion, I believe it's because that's the word from the
original question in the discussion "Resolved: Technical communicators
can create information" (from which this thread appears to be spun off
of).
But we could ask (as yet another tangent) when, if ever, is it
appropriate to speak of something as being information but not
knowledge, or vice versa.
Gain access to everything you need to create and publish documentation,
manuals, and other information through multiple channels. Choose
authoring (and import) as well as virtually any output you may need. http://www.doctohelp.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
