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.
uu=version number of the software product
vv=assigned product number
ww=assigned platform number
xx=assigned manufacturer number
yy=release month
zz=release year
This system is supposed to work for all of our products, not just
documentation. It's got glitches, such as differentiating between the
products and the documentation for products. Fixing that is on my list.
I prefer having meaning in the numbers. Even just putting in the release
date could be helpful somewhere down the line.
Chris Jackson
Stuart Conner <sconner -at- ndsuk -dot- com> wrote in message news:LYRIS-27054-25154-2000 -dot- 06 -dot- 15-07 -dot- 42 -dot- 47--crassick#bellsouth -dot- net -at- lists -dot- ray
comm.com...
> We use:
>
> <originating group code>.<document type code>.<optional field>.<sequential
> number>.<issue>
>
> This coding system gives some 'meaning' to the document code, which I
> personally think is a good thing (you can tell what type of document it
is,
> for example). Some others in the company feel that the document code
should
> just be a plain, unique number with no implied meaning. Anyone have any
> strong feelings on which system might be better?
>
> Stuart
