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 vs. normalization From:"Mark Baker" <mbaker -at- ca -dot- stilo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 19 Sep 2003 11:48:45 -0400
Andrea Brundt wrote
> I'm intrigued, but I must admit I'm only familiar with the term
> "normalization" as it relates to relational databases. What is
> "normalized"
> content? Can you suggest some resources, or provide more information?
It is basically the same idea. Generically, to normalize something is to
make it obey a set of rules. In this case, as in the database case, it means
to make it obey a set of rules that eliminate duplication of information.
Documentation content is a little more complex than typical database data,
so a strict application of third normal form may not be applicable. However,
the basic principle is the same: it content is duplicated, move it to
another table. If you have multiple values of the same type, move them to
another table. If content is not an attribute of the key of the current
table, move it to another table.
In general this means that instead for managing modules that are fragments
of documents, you reorganize your content so that the content relating to
particular subjects is kept together. To create documents, you reassemble
modules the way a database report writer pulls together information from
different tables to create a report. You then assemble the modules to make
documents.
Because your content is organized by subject, it is much easier to validate
its accuracy and completeness and to ensure that changes in the world are
propagated to the affected content quickly and easily.
Normalizing content in the fashion does not require the use of a relational
database system, though it may be useful.
Not all content is worth normalizing. There is a role for the spreadsheet
approach as well as the database approach.
---
Mark Baker
Stilo Corporation
1900 City Park Drive, Suite 504 , Ottawa, Ontario, Canada, K1J 1A3
Phone: 613-745-4242, Fax: 613-745-5560
Email mbaker -at- ca -dot- stilo -dot- com
Web: http://www.stilo.com
This message, including any attachments, is for the sole use of the
intended recipient and may contain confidential and privileged
information. Any unauthorized review, use, disclosure, copying, or
distribution is strictly prohibited. If you are not the intended
recipient please contact the sender by reply email and destroy
all copies of the original message and any attachments.
NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
