Skip to content

Where does a father's name go when the name has no family name? (Abiy Ahmed Ali, Ухнаагийн Хүрэлсүх, Бекмырза Чолпонбай уулу) #1253

Open
0 of 9 issues completed

Description

@derek73

Several naming conventions have no inherited family name. The word in the family slot is the father's name (Ethiopia, Mongolia, Kyrgyzstan, Kazakhstan), a chain of parents' names (bin/binti, S/O), or nothing at all (Burma). The parser has two places for such a word, the family field and the patronymic view (R9), and today it does each, depending on the shape:

Input today
Abiy Ahmed Ali middle Ahmed, family Ali
Ухнаагийн Хүрэлсүх given Ухнаагийн, family Хүрэлсүх (FAMILY_FIRST reads all 126 Khural members right)
Бекмырза Чолпонбай уулу family уулу
خالد بن سعد القحطاني patronymic بن سعد القحطاني, family name included
איתמר בן גביר patronymic בן גביר, an inherited surname

The shape question: can a convention say "this position is the father's name"? If it can, does that name fill family (where a caller sorting or matching looks for it), only the patronymic view, or both? The answer fixes what each sub-issue is asking for. For most of them, what's left after it is a pack's order or a marker list.

Sub-issues: #1203 (Ethiopia), #1231 (Burma, no family name at all), #1237 (Mongolia), #1187 (Kyrgyz uulu), #1188 (Kazakh -ұлы written joined), #1155 (a family name after a بن chain), #1210 (a בן surname in the view), #1165 (S/O, D/O, W/O).

What settles it: whether family means "the inherited name" or "the name a list sorts by". If it means the second, the patronymic view decides whether the same word appears in both. #1209 (in the ben/bin/בן umbrella) is the other side of #1210's word.

Activity

  1. self-assigned this
    on Nov 9, 2026
  2. added
    designChanges what the model can express (a shape decision)
    on Nov 9, 2026
  3. added
    patronymicsFather's names and the patronymic view (rules/R9)
    name-orderName order, family-first and two family names (rules/O)
    and removed on Nov 10, 2026
  4. derek73 commented on Nov 12, 2026

    @derek73
    OwnerAuthor

    Decided 2026-11-12. Two statements settle the shape; each sub-issue becomes a pack, a rule value or a vocabulary entry under them. No default reading changes and no field is added.

    1. family is the name a convention files a person under, not necessarily an inherited one. Where a convention has no inherited name, the word that stands in the surname slot in that convention's own records is the family: the Mongolian father's name (the passport's surname field), a Kyrgyz Father uulu, the last word of an Ethiopian or a Burmese name. This is what the parse does by position today, and it is what a caller sorting or matching reads the field for.
    2. The patronymic view keeps rules/R9's basis: it is filled only by a word or a rule that says patronymic, never by a position. It may overlap family or be a part of it. A father's name that nothing in the text marks (Ethiopia) fills no view.

    What follows for the sub-issues:

    Issue Outcome
    #1203 Ethiopia Stays positional, and the father's name fills no view. Accepted: the same person written with two words and with three has a different family.
    #1237 Mongolia A Mongolian pack with a family-first order, the father's name the family; a rule reading the genitive ending may fill the view.
    #1187 Kyrgyz The issue's proposal: with no surname, the father's name and its marker are the family and the patronymic view alike.
    #1188 Kazakh An ending rule fills the view, as the East Slavic one does; which choice turns it on is a value question.
    #1155 a family name after a بن chain The view may be a part of the family: it stops before a family name that follows the chain, where a closed signal marks one. Which signal is a value question.
    #1210 Hebrew בן Decided with #1257.
    #1231 Burma A pack: the last word is the family by position, the honorifics titles.
    #1165 S/O, W/O Out of this umbrella. The words after the marker are another person's name, which the model has no place for; it wants a decision of its own. Malaysian a/l and a/p, where the father's name is part of the legal name, read as bin does and are a vocabulary question.

    Matching across the two Ethiopian spellings (#1203) needs nothing new. Measured on master 2b39f23, 2026-11-12, Parser.matching().check:

    Pair default parser Parser(policy=Policy(middle_as_family=True))
    Abiy Ahmed Ali / Abiy Ahmed family conflict, no shared key family part-of-other, consistent, shared key ahmed;a
    Abiy Ahmed Ali / Abiy Ali consistent consistent (part-of-other)
    Abiy Ahmed / Abiy Ali conflict conflict
    Abiy Ahmed Ali / Abiy Bekele conflict conflict
    Abiy Ahmed Ali / Abiy Ahmed Bekele conflict conflict

    So a caller matching a list written under this convention builds the matcher from a parser that folds the middle names into the family, and keeps the default parser for the fields (rules/O3's switch costs 21.5 points of field agreement on ORCID's Ethiopian records, #1203). across-roles and other_readings do not reach the pair. The fold is right only for a list known to follow the convention: under it John Paul Smith and John Paul are consistent too.

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

designChanges what the model can express (a shape decision)name-orderName order, family-first and two family names (rules/O)patronymicsFather's names and the patronymic view (rules/R9)

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions