43 | | '''Note:''' |
44 | | |
45 | | Any of these mandatory name fields may be empty in a particular record except ''first_name''. A name field value starting with a question mark '''?''' indicates that this part of the name is uncertain or unknown. |
46 | | |
47 | | 'first', 'middle' and 'last' refer rather to the usual writing order of a person's full name than to the meaning of the name parts. |
48 | | |
49 | | There is no need to split the full name into segments if that is not customary in the person's country of origin - in such case ''first_name'' should represent the person's full name. |
50 | | |
51 | | In case there are multiple local languages to represent the person's name, the ''local_name'' should be in the language/script that is most likely readable by that person and/or their relatives. |
52 | | |
53 | | An application may define additional name fields to represent e.g. titles, nicknames or pseudonyms, however, these additional fields must not be used to repeat or replace any of the mandatory fields. |
| 43 | * Any of these mandatory name fields may be empty in a particular record except ''first_name''. |
| 44 | * A name field value starting with a question mark '''?''' indicates that this part of the name is uncertain or unknown. |
| 45 | * 'first', 'middle' and 'last' refer rather to the usual writing order of a person's full name than to the meaning of the name parts. |
| 46 | * There is no need to split the full name into segments if that is not customary in the person's country of origin - in such case ''first_name'' should represent the person's full name. |
| 47 | * In case there are multiple local languages, the ''local_name'' should be in the language/script that is most likely readable by that person and/or their relatives. |
| 48 | * An application may define additional name fields to represent e.g. titles, nicknames or pseudonyms, however, these additional fields must not be used to repeat or replace any of the mandatory fields. |