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.
Rahel Bailie at r_bailie -at- trillium -dot- com wrote:
> When referring to a standard that has been a Bellcore standard, how have you
> been referring to it since Bellcore became Telcordia: Bellcore, Bellcore
> (now Telcordia), Telcordia, Telcordia (formerly Bellcore), or other? No
> matter how I write it, the phrasing seems awkward.
> Any succinct opinions are appreciated.
Here's a copy of a message in the archives from last October, posted by
shelly -dot- l -dot- hazard -at- exgate -dot- tek -dot- com -dot-
<<We have a LARGE series of documents that refer to Bellcore
Standard TR-303. Bellcore has changed its name to Telcordia Technologies
and has changed the standard to GR-303. Now, this is a Standard that is >>
I maintained our engineers' technical library for a couple of years and can
give you a little input on this subject.
The numbering scheme Bellcore uses actually has nothing to do with
Tellcordia - it is how Bellcore marks the 'evolution' of their standards.
If I recall correctly, it goes like this:
The first standard format is a TA (Technical Advisory, I think) - this then
becomes a TR (Technical Requirements) - the last stage is a GR (General
To my knowledge (though I haven't ordered anything recently), Tellcordia is
still sending out stuff with the name of Bellcore on it.
My recommendation would be to leave the docs alone unless you are revising
them for something else. Then, verify with your engineers that there isn't
a newer/later version of the standard and if so, which version of the
standard the product represents.
christi -at- sageinst -dot- com
240 Airport Blvd.
Freedom, CA 95019
You may be on the right track, but if you just sit there, you're bound to
get run over.