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.
We (the Office of Quality) have just proposed a document numbering
system, and the response so far has been less than enthusiastic. It
seems like overkill to most of the developers and project managers.
"Call it whatever you like, and let VSS take care of the version
control."
/K@
----- Original Message -----
From: Stuart Conner <sconner -at- ndsuk -dot- com>
Sent: Thursday, June 15, 2000 6:16 AM
Subject: Re: Documentation Coding
> 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.
>
>
> Emily Clark wrote in message <54410 -at- techwr-l>...
> >
> >Hi!
> >
> >I am reorganizing the documentation coding system in my company.
We are
> >toying with many ideas and would welcome any suggestions for
this. How are
> >documents coded in other companies?
> >
> >
> >--
> >Emily Clark
> >Documentation Researcher
> >Texar.com
> >
> >
> >
>
>
