HOME > Personal Names

Personal Names

GEDCOM 5.5 provides two alternative ways to represent a personal name, one that uses slashes to separate the surname from the other parts of the name, and one that uses a structure with Name prefix, Given name, Nickname, Surname prefix, Surname and Suffix. This page lists discussions and pages on the wiki that discuss requirements and solutions not handled by GEDCOM 5.5.

1. Most recent work

Personal Name Data Standard Currently there are no comprehensive data standards on PersonalNames that take into consideration Internationalization and the different naming customs of different cultures and languages. This draft proposed Personal Names Data Standard attempts to meet that goal. In addition, this hyperlink will contain separate draft documents on Background, Problems, User Requirements, Rationale, Implementaion Guide and Outstanding Issues. These documents attempt to aggregate and summarize the other papers and links below.

2. Previous discussions, pages and documents

3. Personal names in current genealogy programs and services

4. User Requirements

5. Discussion of the level of Rigour in handling Personal Names

6. External genealogy related resources

7. External resources about names in general



ACProctor 2012-01-09T04:19:55-08:00
Citation dependency
The issues raised at http://bettergedcom.wikispaces.com/Formatting+Templates+and+MetaData may have a bearing on this design Neil.

NeilJohnParker 2012-01-09T08:23:58-08:00
First a nit, your 5th line in <UIData> has an superfulous "/", i.e </elements>.

Does this template concept support multipe occurences, e.g. 4 authors,
Neil Parker, Louise Parker, William Smith and Frank Jones. Does it do so with out using comma separated lists, i.e. as separate lines? If so how? Could you provide a simpl example. Can and how do templates handle values that are cross references? How do templates handles "mongrel" templates i.e. a person has a combination of two standard templates for say a PersonName as in Canada and elsewhere where we have people and customs from all over the world.

ACProctor 2012-01-09T08:37:09-08:00
It could do Neil. This is not a complete design here. STEMMA suggested using a JSON-like syntax for item lists such as authors or page references. The separator is then irrelevant.

I would hope that the template itself does not make itself specific to any particular locale or culture. Ideally, its personal-name parameters should be typed as one of first-canonical-form, second-canonical-form, etc., and either have a choice of locale-dependent algorithms in the Text case, or call on the data provider in the BG case.

This scheme works well for simple citations, i.e. where there is only once source, and no author annotation. See discussion in STEMMA spec on simple-citations versus compound-citations for more complex cases.

ACProctor 2012-01-09T11:28:53-08:00
The issue of elided forms (e.g. for citations) and general issues of sorting and collation are raised here Neil: http://bettergedcom.wikispaces.com/message/view/Formatting+Templates+and+MetaData/48948369.

Apologies for this being a little disconnected in wiki terms.

ACProctor 2012-01-10T02:16:27-08:00
Bringing the aforementioned thread over to this page where it's more relevant:-

I don't have a good scheme for dealing with the other issues you raise but I wanted to find a way of dealing with elided forms and sorting together.
For instance, consider something like:
"General Sir Anthony Cecil Hogmanay Melchett VC DSO KCB"
...he of Blackadder fame :-)
We can break this down into name-parts like titles, givenname, middlenames, familyname, honaries, etc.
Although those terms are very Western, something more generic might allow us to specify sorting and different forms by the token groups.
For instance:
fore-titles = 1 2
given-name = 3
middle-names = 4 5
family-name = 6
post-titles = 7 8 9
Hence, different name forms might be
family-name, fore-name middle-initials
fore-name family-name
family-name, fore-initial
Similarly with a sort-order or collation-sequence.
If we can break apart a name then it is practical to have standard combinations for different "name locales" (i.e. the locale that the name structure is relevant to rather than specifically that of the user). This would simply the whole argument.

I know people will leap on this and cit is as too an approach too Western, thereby missing the reference to "generic". :-)

It still feels a little complex in my head but imagine that we have a series of "name schemes" - one for each cultural variation.

These name schemes would define the name-part categories, like the Western ones shown above. Using appropriate meta-data, we could help to present an appropriate form for entering such a name - ... shades of the same approach to citations visible here.

Hence, when entering a Western name, you might see fields for given-name, family-name, etc., as shown listed above, but when entering a name associated with a different scheme then the name-part fields would be labelled differently.

OK, so what would that give us? Well, it would allow the tokens in a name (i.e. basically the separate words) to be categorised according to a set of culturally significant categorised. By that, I mean the parts significant during sorting/collation and different representative forms.

We then have a small set of items (i.e. name-parts rather than mere tokens, where each name-part might encompass multiple tokens) and the name scheme can use them to define the sorting rules and name forms in a very compact way.

What do folks reckon? This could work - no question in my mind - but would it be too complex? Can we manage name-schemes in a similar way to citation-sources?