GEDCOM/INDI-Tag

From GenWiki

Jump to: navigation, search

Contents


This page is an English extract of the German page GEDCOM/INDI-Tag [1], for full details see the German page.

Name and Meaning

Tag

INDI

Meaning

INDIVIDUAL

Usage

The individual record is a compilation of facts, known or discovered, about an individual. Sometimes these facts are from different sources. This form allows documentation of the source where each of the facts were discovered.

Formal Description of Permissible Values

Base: GEDCOM Standard Draft 5.5.1

An INDIVIDUAL RECORD is defined as follows:

INDIVIDUAL_RECORD:= 
n @XREF:INDI@ INDI {1:1} 
+1 RESN <RESTRICTION_NOTICE> {0:1} 
+1 <<PERSONAL_NAME_STRUCTURE>> {0:M} 
+1 SEX <SEX_VALUE> {0:1} 
+1 <<INDIVIDUAL_EVENT_STRUCTURE>> {0:M} 
+1 <<INDIVIDUAL_ATTRIBUTE_STRUCTURE>> {0:M} 
+1 <<LDS_INDIVIDUAL_ORDINANCE>> {0:M} 
+1 <<CHILD_TO_FAMILY_LINK>> {0:M} 
+1 <<SPOUSE_TO_FAMILY_LINK>> {0:M} 
+1 SUBM @<XREF:SUBM>@ {0:M} 
+1 <<ASSOCIATION_STRUCTURE>> {0:M} 
+1 ALIA @<XREF:INDI>@ {0:M} 
+1 ANCI @<XREF:SUBM>@ {0:M} 
+1 DESI @<XREF:SUBM>@ {0:M} 
+1 RFN <PERMANENT_RECORD_FILE_NUMBER> {0:1} 
+1 AFN <ANCESTRAL_FILE_NUMBER> {0:1} 
+1 REFN <USER_REFERENCE_NUMBER> {0:M} 
+2 TYPE <USER_REFERENCE_TYPE> {0:1} 
+1 RIN <AUTOMATED_RECORD_ID> {0:1} 
+1 <<CHANGE_DATE>> {0:1} 
+1 <<NOTE_STRUCTURE>> {0:M} 
+1 <<SOURCE_CITATION>> {0:M} 
+1 <<MULTIMEDIA_LINK>> {0:M}

The individual record is a collection of known or discovered facts of a person. Sometimes the facts arise from different sources. This form allows the documentation of the source, in which a fact was discovered.

The following elements thereof are described in other articles: ALIA, <<ASSOCIATION_STRUCTURE>>, <<CHILD_TO_FAMILY_LINK>>, <<PERSONAL_NAME_STRUCTURE>>, <<NOTE_STRUCTURE>>, <<MULTIMEDIA_LINK>>, RESN, SEX, <<SOURCE_CITATION>>, SUBM


In this articel are described: Individual events <<INDIVIDUAL_EVENT_STRUCTURE>> and individual attributes <<INDIVIDUAL_ATTRIBUTE_STRUCTURE>>.

Descriptions of Events to a Person

Events to a persone like e.g. birth, christening, death, burial will be described by the <<INDIVIDUAL_EVENT_STRUCTURE>>:

INDIVIDUAL_EVENT_STRUCTURE:= 
[ 
n [ BIRT | CHR ] [Y|<NULL>] {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
+1 FAMC @<XREF:FAM>@ {0:1} 
| 
n DEAT [Y|<NULL>] {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
| 
n [ BURI | CREM ] {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
| 
n ADOP {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
+1 FAMC @<XREF:FAM>@ {0:1} 
+2 ADOP <ADOPTED_BY_WHICH_PARENT> {0:1} 
| 
n [ BAPM | BARM | BASM | BLES ] {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
| 
n [ CHRA | CONF | FCOM | ORDN ] {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
| 
n [ NATU | EMIG | IMMI ] {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
| 
n [ CENS | PROB | WILL] {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
| 
n [ GRAD | RETI ] {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
| 
n EVEN {1:1} 
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1} 
]

NOTE: The {0:1} definition in above listing should not mislead to believe in a personal record these events may appear only once. The INDIVIDUAL_EVENT_STRUCTURE may appear {0:M} times in individual record. Therefor each listed tag may occur as often as needed.

Also be noted: Only the tags BIRT, CHR and DEAT may be supplemented by a "Y" in the line, to make the statement that a person is born, christened ( baptized ) or died. For all other tags no additional text may follow in the same line. Additional information have to be transferred by subsequent lines.

Descriptions of Attributes of a Person

Attributes of a person are e.g. occupation, residency, etc, and will be described by the <<INDIVIDUAL_ATTRIBUTE_STRUCTURE>>:

INDIVIDUAL_ATTRIBUTE_STRUCTURE:=
[
n CAST <CASTE_NAME> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n DSCR <PHYSICAL_DESCRIPTION> {1:1}
+1 [CONC | CONT ] <PHYSICAL_DESCRIPTION> {0:M}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n EDUC <SCHOLASTIC_ACHIEVEMENT> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n IDNO <NATIONAL_ID_NUMBER> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n NATI <NATIONAL_OR_TRIBAL_ORIGIN> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n NCHI <COUNT_OF_CHILDREN>14 {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n NMR <COUNT_OF_MARRIAGES> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n OCCU <OCCUPATION> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n PROP <POSSESSIONS> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n RELI <RELIGIOUS_AFFILIATION> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n RESI /* Wohnort */ {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n SSN <SOCIAL_SECURITY_NUMBER> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n TITL <NOBILITY_TYPE_TITLE> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>>* {0:1}
|
n FACT <ATTRIBUTE_DESCRIPTOR> {1:1}
+1 <<INDIVIDUAL_EVENT_DETAIL>> {0:1}
]

Details to Events and Attributes of a Person

The continuing lines of an event or attribute of a persons are set up as follows:

INDIVIDUAL_EVENT_DETAIL:= 
n <<EVENT_DETAIL>> {1:1} 
n AGE <AGE_AT_EVENT> {0:1}

The substructure of the individual events is almost the same as in the family records. Only instead of HUSB and WIFE that could arise in addition in the family records, the person's age at the time of the event (AGE) can be added.

This structure may be used in the individual record at each event. Identical with the definition of family events are these details:

EVENT_DETAIL:= 
n TYPE <EVENT_OR_FACT_CLASSIFICATION> {0:1} 
n DATE <DATE_VALUE> {0:1} 
n <<PLACE_STRUCTURE>> {0:1} 
n <<ADDRESS_STRUCTURE>> {0:1} 
n AGNC <RESPONSIBLE_AGENCY> {0:1} 
n RELI <RELIGIOUS_AFFILIATION> {0:1} 
n CAUS <CAUSE_OF_EVENT> {0:1} 
n RESN <RESTRICTION_NOTICE> {0:1} 
n <<NOTE_STRUCTURE>> {0:M} 
n <<SOURCE_CITATION>> {0:M} 
n <<MULTIMEDIA_LINK>> {0:M}

Except NOTE, SOUR and OBJE all other tags or structures may occur only once at a maximum.

Agreements for INDI

The agreements for INDI are derived from the discussion on the Gedcom-L. They were decided by a vote of the program authors of the list.

E1 Events in Individual Records

All tags explicitly defined in the GEDCOM standard for events may be used. In the line of the tag, no further content is allowed. Exception are the tags BIRT, CHR and DEAT where Y may follow as information that this event has occurred.

E2 Line content after EVEN

Due to contradictory statements of the GEDCOM standard about a line content after the EVEN tag in individual records, it is agreed, that in addition to E1 also in individual records a text may follow after the tag EVEN. So EVEN is here treated the same as in the family record.

E3 Attributes in Individual Records

All tags explicitly defined in the GEDCOM standard for attributes may be used. For all of these tags a text may be added on the same line. This is also agreed here for the tag RESI, although this is not explicitely mentioned in the GEDCOM standard.

E4 Dealing with TYPE

All tags for events and attributes can be described by a subordinate TYPE tag. A description with TYPE for the tags EVEN, FACT and IDNO must be exported.

E5 Alternatives for Events and Attributes

Events often can be represented in GEDCOM by an explicit tag or by the tag EVEN, in combination with TYPE. For this purpose, it is agreed:

  • It is recommended to export the events in the structure corresponding to the exporting program.
  • It is permitted to replace an explicit event tag by a EVEN.TYPE representation with a corresponding plaintext after TYPE. This can occur for export especially for programs, which can not handle the explicit tags.
  • For programs that internally represent only one of these alternatives for events, it is recommended to convert incoming information in their own representation of events. In cases where this is not possible, the transfer into a comment is recommended.

Analog it is agreed for attributes:

  • It is recommended to export the attributes in the structure corresponding to the exporting program.
  • It is permitted to replace an explicit attribute tag by a FACT.TYPE representation with a corresponding plaintext after TYPE. This can occur for export especially for programs, which can not handle the explicit tags.
  • For programs that internally represent only one of these alternatives for attributes, it is recommended to convert incoming information in their own representation of attributes. In cases where this is not possible, the transfer into a comment is recommended.
Personal tools
GenWiki-internal
In other languages