Fascinating discussion, and threads like this are why this is the only mailing list that always triggers my "important" flag :)
My problem with names isn't the number of fields needed to present them (I liberally use JSON1), but the operations that are possible on them, and the UI needed to enter this data. I want to know, given a world where people have nicknames, no last names, gender fluidity, customizable pronouns, honorifics, super short and super long names, non-latin characters etc - How do I create an email greeting - How do I create an address label - How should I sort a list of names - How should I show a logged in user - How do you let the user fill in their name I'm thinking that maybe the name filling in would just take the full name as they want to write it, and if their name has non-latin charset characters, it opens another field where they can enter their "western name". Then there's the matter of honorific, which is a searchable dropdown (all languages combined I think) that lets you add custom honorifics if needed. While they are filling in the fields, there's a preview section that shows derived data, like email:"Dear [honorific] [lastname]", profile:"[fullname]" etc, where the user can pick if they'd rather be addressed with "Hi [firstname]", "To: [alias]" etc. Depending on the application, it could even show the name in various declensions (e.g. in slavic languages), or custom pronouns. It's complex, but it could be a nice UI component to open source, and it would result in an object with the various derivations of the name that you'd store schemaless. However, it could be that people will feel threatened or reduced to a number with that sort of interface. I have no idea how to fix that. Wout. Wout. On Wed, Nov 13, 2019 at 4:28 AM Richard Damon <rich...@damon-family.org> wrote: > On 11/12/19 2:42 PM, Michael Tiernan wrote: > > On 11/10/19 1:21 AM, Gary R. Schmidt wrote: > >> So what happens when someone from a family who only uses first- and > >> last-names moves to Kansas? > >> > >> Do they have to make up a middle-name so that he idiots can fill out > >> the forms? > > > > I am most definitely not going to take one side or the other. My only > > suggestion is for anyone to see the depth and complexity of the > > problem, get involved in genealogy. You'll want to scream very > > quickly. :) > > Yep, I AM involved in genealogy, and there you not only want to just > record the person's name, but you have a real reason to want to group > people by 'last name' as that is one hint that they might be related, > but there are all sorts of rules in different cultures about family > names (can't really call them 'last names' as they aren't always last, > and 'Surnames' aren't accurate either) > > -- > Richard Damon > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
