- From: Mark Davis ☕ <mark@macchiato.com>
- Date: Wed, 3 Aug 2011 17:23:53 -0700
- To: ishida@w3.org
- Cc: www-international@w3.org
- Message-ID: <CAJ2xs_FEqKoRXqq3o--AYkLomLZJZq15aOFUKZ-ZfhQqeuqNfg@mail.gmail.com>
> http://www.w3.org/International/questions/qa-personal-names The overview of personal names is very useful. However, I think there are some problems with the guidance given in the section "implications for field design". Look at this from a functional approach. A particular system may need to do some of the following tasks: 1. Have a short, personal name, eg "Welcome back, Mark" 2. Have a relatively unique, informal name, eg "Mark Davis commented on your post". 3. Have a name to use in UIs that have "Sort by: Family Name" (meaning: or best equivalent) 4. Have a name to use in UIs that have "Sort by: Given Name" (meaning: or best equivalent) 5. Have a name for more formal contexts, such as a postal mailing, eg "Dr. Mark Davis" 6. Etc. I think having more such tasks listed in the document would help to motivate (and test) the recommendations give in the section "implications for field design". In particular, I think systems are often driven to asking for "Family Name" and "Given Name" because they can (or think they can) generate each of the forms needed for at least the tasks #1-#4. There is some tension, because you don't want to have a UI that asks for 8 different forms of a person's name; people find that onerous!
Received on Thursday, 4 August 2011 00:24:21 UTC