Skip to content

Should a parsed title say what kind it is, and a word its gender? (Dr. Mr. Sir John Smith reads three titles the same) #1461

Open

Description

@derek73

The question. The vocabulary records a title's kind (salutation, academic, religious, nobility, military, office, occupation, kinship) and, where a word gives a definitive clue, a gender (bint, Mrs, doña). Neither reaches a caller. Every title token reads the same:

>>> [t.reading.kind for t in parse("Dr. Mr. Sir John Smith").tokens[:3]]
['title', 'title', 'title']

A suffix token, by contrast, already splits four ways (generation, credential, honorific, post-nominal).

What it would allow. A caller could pick the salutation out of a title run to write Dear Mr. Smith, or drop the academic title and keep the courtesy one. CLDR's single title field does not model this.

The shape proposed. Reading gains one or two optional fields, filled only where the reading came from the vocabulary. A title read by its shape (Insp.) or added by a caller with the generic kind="title" has none, so an empty field means unknown, not "has none".

Open:

  1. Is there a caller for this? No report has asked for either. This issue exists so the RFC's open question has a home; it is not scheduled.
  2. One field or two: the vocabulary kind and the gender are separate facts and could land separately.
  3. One kind or a set: none of the 816 title words carried two title kinds on 2026-10-28 (the RFC's count, not re-taken).
  4. Whether a view should name the salutation alone, as generation and credentials split the suffix.
  5. Gender is recorded only on words that state it (decision 9). It must never be inferred from a given name, and the docs would have to say so.
  6. Each field is an ADDED_IN field on a pickled type.

Source: docs/design/vocabulary-model-rfc.md, phase 4's open questions and the Gender paragraph.

Activity

  1. self-assigned this
    on Nov 19, 2026
  2. added
    designChanges what the model can express (a shape decision)
    titlesTitles and honorifics (rules/H)
    tokensTokens, separators and punctuation (rules/T)
    on Nov 19, 2026
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)enhancementquestiontitlesTitles and honorifics (rules/H)tokensTokens, separators and punctuation (rules/T)

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions