Registered: March 13, 2007 | Posts: 2,759 |
| Posted: | | | | Quoting hal9g: Quote: If you were to honestly evaluate all of the "common name" arguments in these forums, it seems to me that it would be very easy to see why it is more complex to figure out last names than it is to recognize Mr., Mrs., Sir, Jr., Sr., Dr., von/del/de/di as part of a last name and the rest of the things that are clearly defined in the current Rules.
But then admitting that would defeat your argument. Full quote from the rules committee forum (since not everybody has access to it): Quote: Quoting hal9g:
Quote: This is just a big red herring. Prefixes and prepositions and articles can be easily identified and/or proven (documented). Whether an un-hyphenated name is a double barrelled last name, a maiden name/last name wheremaiden name is being used as a middle name or just a plain old middle name/last name, often cannot be proven. I doubt that! In my database there are "Del Close//", "Del//Anderson", "Del//Baker", "Del//Close", "Nino//Del Buono" and more names with "Del" as a preposition. I don't know if I have some "Del" middle name because the search function does not work well with middle names only. But how can you define whether "Del" is a given name or a preposition part of a last name?
Quote: AND, it doesn't really matter any way, does it? As long as the name only appears one way in the database and is properly linked to all of the "as credited" names for this person, it makes no difference whatsoever if their name is parsed correctly or not! It does matter to me. We have a cast and crew database where every person is described with a first name, midlle name, and last name field. I do not want them to be used as arbitrary person identification strings but exactly as what the field names suggest.
|
|