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: Single Sourcing From:Kathy Stanzler <KatheS -at- HEALTHCARE-AUTOMATION -dot- COM> Date:Wed, 9 Jun 1999 12:15:39 -0400
Mark Baker said, "If you set up your source so that the content is held
in an
abstract form..." Could you explain that in more detail?
I understand the concept of single sourcing in the abstract; what I
don't understand is how it works "in real life." For example, if you are
using a database as your information repository, what does each database
record consist of? Text? XML elements? What is the structure of the
database? How do you retrieve the database information, process it, and
pass it along to the output?
Kathy Stanzler
Technical Writer
kstanzler -at- healthcare-automation -dot- com
