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 Document Numbering/Configuration From:"Mark L. Levinson" <nosnivel -at- NETVISION -dot- NET -dot- IL> Date:Sat, 24 Oct 1998 14:30:57 +0200
I got into a document-numbering tangle a while ago at the
software company where I worked, and the advice that I finally
got-- good advice, I think, and maybe it came from this list--
was Keep It Short and Simple. Don't try to cram every item
of relevant information into the document number. If you do,
then you will be the only person who understands the number.
At worst, incorrect numbers will be assigned when you're away.
Even at best, anyone else trying to extract information from the
number will need to contact you or to consult a table. So
you're better off assigning simple numbers and using a separate
table to map them to other significant information in the first
place.
--------------------------------------------------------------
Mark L. Levinson - Herzlia, Israel - nosnivel -at- netvision -dot- net -dot- il
--------------------------------------------------------------
A Hard Day's Night. ... They could have stopped after the
opening chord and still had a hit. - Nick Andrews, Sydney
--------------------------------------------------------------
