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.
<techwrl-list-only -at- doitall -dot- com> wrote:
> What I am asking is: what do I call data properties within an object in a
> situation like this? Properties? Fields? Values? Variables? Attributes?
This sounds like the *least* of your problems with this document :-)
My 2 cents:
Do - Choose a term and stick with it. Try to minimize the amount of
conditional text you have to maintain.
Don't - build an elaborate web of conditional terms, just because you can.
Here are two factors to decide how to choose a term:
1. Who is your biggest expected market? (Use their term).
2. Who would be most offended by seeing the wrong term? (Use their term).
For example, you rarely see manuals localized to US vs. UK English, because
it's not worth the expense, and the Brits seem to have gradually become
resigned to reading US English everywhere :-)
