RE: Naming NAME fields

Subject: RE: Naming NAME fields
From: "Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 8 Nov 2006 13:35:00 -0500

Hi Kevin,

You're assuming that:
* The NAME fields are being used in a product for sale.
* At least some of the users aren't familiar with "First Name" and "Last
* All of the users are familiar with "Given Name" and "Family Name."
(I'll bet my own kids wouldn't know which of their names is a "Given

Based on Lisa's initial query, I wouldn't make these assumptions. My
only "contention," as you call it, is that our knowledge of our users
should inform these decisions.

What we know about our users varies widely among the Whirlers. But Lisa
wrote: "This question assumes that the writer knows his/her audience..."
So there's your starting point.



> -----Original Message-----
> From: Kevin
> Sent: Wednesday, November 08, 2006 1:17 PM
> To: Dan Goldstein; techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: RE: Naming NAME fields
> >
> > Only if you check whether _your_ users more easily identify
> > "Given Name and Family Name" than "First Name and Last
> > Name." Otherwise, it's just Design By Assumption.
> >
> Yes... and the assumption is that "First Name" and "Last Name"
> are _absolutely_ wrong for a couple of billion people on this
> planet, significant numbers of whom have emigrated to your
> country and to other countries where you might be selling
> your product...
> ... I admit that you could be perfectly correct in your
> contention, but I'd like to examine your reasoning, please.

This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.


WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!

Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

RE: Naming NAME fields: From: mlist

Previous by Author: RE: Naming NAME fields
Next by Author: RE: What tech writers "do"
Previous by Thread: RE: Naming NAME fields
Next by Thread: RE: Naming NAME fields

What this post helpful? Share it with friends and colleagues:

Sponsored Ads