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: Queries on Single Sourcing From:"Dave Whelan" <dwhelan -at- auracom -dot- com> To:<techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 13 Feb 2004 17:01:30 -0400
The difference between single sourcing and current practice is similar
to that between structured and straight-line code in a software
program. In the old days, programs used straight-line coding in that
everything that had to be done had its own unique lines of code. Wheb
structured programming was introduced, common lines of code could be
written once and then could be referred to by any part of a program
that needed them. So with single sourced information: common
information can be developed once and then referred by any information
product. The information content might be identical but presented in
different ways, or similar with variations dictated by the calling
document. There are still reasons to employ straight-line code but
most code is now structured to allow for software reuse and for many
other advantages. The same advantages apply even more to information
products and, IMHO, we are bound to follow this single-sourcing trend.
Regards,
Dave Whelan,
Lunenburg, NS.
