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: Mapping, take II From:Gwen Thomas <gthomas -at- PAYSYS -dot- COM> Date:Tue, 29 Jun 1999 15:23:42 -0500
Mark Baker wrote (in what I hope he will turn into a formal White Paper:
"Effective single sourcing depends on keeping and managing all the
interesting relationships in your information set in order to give yourself
many options for creating different syntheses of information for different
Darn, I wish I'd said that.
And earlier, Mark wrote:
"The best way to manage relationships is to manage those
properties which form the basis of relationships, making the relationship
explicit is less effective because it does not hold out the possibility of
discovering new relationships based on the properties of other objects."
I follow (and wholeheartedly agree with) the first part. Then I'm not sure I follow. I usually tried to find implicit links and, if I was building a database, use the related data (or a surrogate) as primary/foreign keys. What do mean by "making the relationship explicit" - are you referring to dropping hypertext links into language strings? Do you mean that by using something which can be arbiitrary (as a hyperlink can sometimes be) that we've now made an implicit relationship explicit?
Knowledge Management Consultant
CIBER Information Services