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.
Shawn Connelly described his revised document numbering system:
" BTW, my part number scheme is: x.x.1414.02.01.00
x.x - Software revision associated with this document
1414 - Year and month of document release
02 - Major release
01 - Minor release
00 - Document type identifier (i.e. 00 - English NA version, other values
will indicate localization or other special releases) - I haven't decided
yet but if I use hexadecimal for this value, I can allow for 255 variations
of a document type.
This documentation department is new (just me now) and I want a scheme that
won't need to be revised by allowing for all those unknown unknowns. Love
to hear your opinions about this document numbering scheme. "
I'd go with the 2-letter alphabetical code for the document type. People
will remember the most common ones, and I don't think you'll have 255
document types. ( And if I remember my math for permutations and
combinations, a 2-letter code will provide approx 26X25/2, or 325 possible
Margaret Cekis, Johns Creek GA
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l