Full Name
identity.person.full_nameComplete person name (first and last names, possibly including middle names). Locale-specific due to name order and formatting conventions (e.g., Western "FirstName LastName" vs East Asian "LastName FirstName").
Operations on this type: Hash or mask a column, Parse nested values
Try a value
Full Name's rule accepts it.
Reads it as John Smith
Also accepted by
- First Name
John Smith - Last Name
John Smith
Use it
finetype infer -i 'John Smith' --mode column
# → identity.person.full_nameSELECT ft_infer('John Smith');
-- → 'identity.person.full_name'CAST({col} AS VARCHAR)How finetype reads the samples
DuckDB 1.5.5 · finetype 0.6.66
| Value | As VARCHAR | first_name | last_name |
|---|---|---|---|
| John Smith | John Smith | John | Smith |
| María García | María García | María | García |
| Jacques Dubois | Jacques Dubois | Jacques | Dubois |
| 田中太郎 | 田中太郎 | 田中太郎 | 田中太郎 |
| محمد علي | محمد علي | محمد | علي |
| Smith, Mr. John | Smith, Mr. John | John | Smith |
| Dr. Jane Wilson | Dr. Jane Wilson | Jane | Wilson |
| BROWN, ALICE | BROWN, ALICE | ALICE | BROWN |
Pattern
Length 2 to 200 characters.
^[\p{L}\s'\-.,]+$| Value | Length | Shape |
|---|---|---|
| John Smith | 10 | not checked |
| María García | 12 | not checked |
| Jacques Dubois | 14 | not checked |
| 田中太郎 | 4 | not checked |
| محمد علي | 8 | not checked |
| Smith, Mr. John | 15 | not checked |
| Dr. Jane Wilson | 15 | not checked |
| BROWN, ALICE | 12 | not checked |
pattern uses syntax this checker does not support
Background
Origin
The vCard Format Specification, RFC 6350, was published in August 2011.[1] Its FN property holds the formatted text of the name of the object the vCard represents.[1] RFC 6350 requires at least one FN property in every vCard.[1] A separate, optional N property breaks the name into components: family names, given names, additional names, honorific prefixes and honorific suffixes.[1] That split is a useful picture of this type: a full name is the FN side, one display string, while first and last name columns are an attempt at the N side. (Meridian's view)
Use
The W3C's guide to personal names notes that in Japan, Korea and Hungary names are ordered family name followed by given name.[2] The same guide says Spanish-speaking people commonly have two family names.[2] In Icelandic names, the guide explains, the second part indicates the father's or sometimes the mother's name.[2]
The W3C guide advises that, where possible, it is simpler to use the full name as the user provides it.[2] Patrick McKenzie's essay Falsehoods Programmers Believe About Names lists the belief that people's names fit within a certain defined amount of space as a falsehood.[3] The same essay lists the belief that people's names are case insensitive as a falsehood.[3] Keep the original string untouched, treat any split into parts as a lossy derived column, and never normalise case on the stored value. (Meridian's view)
Where you'll meet it
The US Federal Election Commission's contributions by individuals file carries a NAME column, Contributor/Lender/Transfer Name, as a single field.[4] The FEC's file description gives that column the data type VARCHAR2 (200) and the example Abigail Adams.[4]
Sources
- [1]vCard Format Specificationstandard
- [2]Personal names around the worldsecondary source
- [3]Falsehoods Programmers Believe About Namessecondary source
- [4]Contributions by individuals file description | FECdataset
How it's detected
Locale-specific due to name order conventions. Simple decompose extracts first and last words; more sophisticated parsing requires NLP. Includes Unicode letter support for international names.
Schema
https://meridian.online/schemas/identity.person.full_name · Frictionless type string
finetype taxonomy identity.person.full_name -o json-schema