Import by Ref:Why/Why not

[Katav <katav -at- YAHOO -dot- COM>]

Both the FrameUsers and TECHWR-L lists have parallel threads.

There are good reasons to import by reference and good reasons to copy
in.
If you have a dynamic manual and **no** need to maintain "as it was"
documentation, import by reference is the better option.
This method uses "replacement" graphics (and text as well) so each
time the file is opened, the current "same name" data are imported.
If you have a dynamic manual AND an archival requirement, file
management (read "configuration management") is required and must be
STRICTLY ENFORCED; no one except the CM is allowed to check in new
files. As files are updated, the CM needs to transfer all old files to
a new location (while maintaining the same directory structure.)  The
old files should be compacted - even with current HD pricing, HDs do
have a finite amount of space.
If the manual is a "one-time" job or if archiving is the primary
concern, it pays to copy in files. If changes are made, a new manual
is issued.
In all cases, the key is to carefully plan and maintain naming
conventions and directory structures. The former allows easy file
management and creation of xrefs/hrefs to non-existent (albeit
planned) files; the latter allows files to be moved round PROVIDING
all inter-directory (folder) references are "relative" (vs. absolute).




==
Katav ( katav -at- yahoo -dot- com )
''Despise not any person and do not deem anything unworthy
of consideration, for there is no person without his hour,
and no thing without its place'' {Ben Azzai [Avot 4:2]}

_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com


 From ??? -at- ??? Sun Jan 00 00:00:00 0000=