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: Definitions: publications vs. documentation From:"Oja, W. Kelly" <w -dot- kelly -dot- oja -at- verizon -dot- com> To:TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 9 Sep 2003 07:40:44 -0500
I would define publication as a document that is sent out to a number of
people. I may be trying to simplify it too much, but I see a publication
as something that is mass-produced for a small to large audience. I
would define documentation as putting pen to paper, the recording of
ideas, events, procedures, anything and everything in the development
process of the product and/or the finalized document.
I fear that this may lead to a debate along the lines of "You say
tah-may-toe and I say tuh=mah-toe." But I believe documentation can be a
final copy, but when teamed with publication, it is a precursor.
W. Kelly Oja
Verizon Airfone
Verizon Airfone JetConnect (SM) now with email
Inflight e-mail, Instant Messaging, and more...
