"How do people's names differ around the world, and what are the implications of those differences on the design of forms, databases, ontologies, etc. for the Web?"
This has basically convinced me that you should only ever have a single (long) "Name" text input.
Except as pointed out that's generally not sufficient for Japanese since given their kanji based name you'll have no idea how to pronounce or sort it without them also telling you in a separate field how it's pronounced.
There's also the issue of interacting with other systems. You may want just one field but some credit card processor might want 2 etc....
This is always a difficult task to tackle, especially when dealing with data sources like Active Directory that want a surname and given name, which may not always be the case for everyone.
Admittedly the best answer is to get a "Family Name" and a "Nick Name" (not to be confused with a user name). The big problem is convincing the management they don't need to collect first name, last name, greeting...etc
5 comments
[ 4.5 ms ] story [ 18.0 ms ] threadThis has basically convinced me that you should only ever have a single (long) "Name" text input.
See also: http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b...
There's also the issue of interacting with other systems. You may want just one field but some credit card processor might want 2 etc....
Admittedly the best answer is to get a "Family Name" and a "Nick Name" (not to be confused with a user name). The big problem is convincing the management they don't need to collect first name, last name, greeting...etc
I think the problem is drawing the distinction between the questions "what is your canonical identity?" and "how should we address you?"