D
Search me! Even the encryption standards are outdated.Weird.
What's this "Commercial Product of the Shelves"?!!
I too used abbreviation with full name in brackets on first use when I was writing installation instructions and the like many years ago.When I was authoring technical documents to MoD requirements the first use of an abbreviation had to be put in full, with its abbreviation following in brackets, and then it was OK to use the abbreviation thereafter (personally I prefer to use the abbreviation from the start and spell it out first time in brackets).
I couldn't remember what I used to do, so I looked up some old journal papers that I was a co-author on. Probably I followed the house style as we seemed to write things out in full with the abbreviation following. Example from 1989: "...problems of electromagnetic compatibility (EMC) ... nuclear electromagnetic pulse (NEMP) and lightning (LEMP) events."personally I prefer to use the abbreviation from the start and spell it out first time in brackets
Reading that I think that the 'other' way is clearer. For "...problems of electromagnetic compatibility (EMC) ..." the reader has to go back and work out where the acronym begins - fairly obvious here but there will be edge cases. If you write "...problems of EMC (electromagnetic compatibility) ..." it's much more obvious what the acronym is for.I couldn't remember what I used to do, so I looked up some old journal papers that I was a co-author on. Probably I followed the house style as we seemed to write things out in full with the abbreviation following. Example from 1989: "...problems of electromagnetic compatibility (EMC) ... nuclear electromagnetic pulse (NEMP) and lightning (LEMP) events."
I'm not sure whether I'd follow the same style now.
Yes, it makes a whole lot more sense to me now, thanks to that link from a friend in Oxford. (discussion, not argument!)I'm pretty sure this came up in an argument a long time ago - but without the explanatory article. Thanks.
Problem with doing it "Light Emitting Diode (LED)" is that it breaks the rule about referring to something the same way throughout the document if you then use LED. And on the subject of consistency I've seen documents that can't make up their mind to e.g. refer to it as an LED, an indicator or a light, and then does it come on, illuminate or light.Nonetheless, the opposite is required style for defence documentation.
Problem or not, that's what they do. If you're going to be consistent and use "Light Emitting Diode" throughout, there's no need to introduce the abbreviation at all.Problem with doing it "Light Emitting Diode (LED)" is that it breaks the rule about referring to something the same way throughout the document if you then use LED.
Still not sure which way round I'd do this now. As the junior co-author on papers I followed what the lead author did. When I was lead author I followed the same style.I know I said I would rather use "LED (Light Emitting Diode)", but actually I would prefer to go straight in with "LED" and push explanations into the glossary (there has to be a glossary).
Sometimes it's worth putting any new or uncommon abbreviations in an introduction, and a glossary is definitely a must in documents that may not be read linearly.I think I'd prefer to have a belt-and-braces approach with abbreviations or acronyms. Whichever way (acronym first or explanation first), always include the explanation on first use and in the glossary (if there is one). Never repeat the explanation after first use.
I always read linearly, otherwise I'd be reading random words. (I do know what you mean)a glossary is definitely a must in documents that may not be read linearly
We all know nobody reads them.but actually I would prefer to go straight in with "LED" and push explanations into the glossary (there has to be a glossary).
If you mean the glossary - I only ever read the glossary when some eejit hasn't explained the acronym on first use.We all know nobody reads them.