My Family Tree GEDCOM 5.5.1 Extensions
Total Page:16
File Type:pdf, Size:1020Kb
My Family Tree™ GEDCOM Extensions Document version 3.1 Date 16 Jan 2021 My Family Tree version(s) 10.8.0.0 This document provides details of all GEDCOM extensions used in GEDCOM files produced by the version(s) of My Family Tree specified above. Conditions of use © Chronoplex Software 2017-2021. This document and the information contained within is made available for private use by end users of My Family Tree for the sole purpose of interpreting the form of GEDCOM extensions in GEDCOM files produced by My Family Tree. All other rights, including, but not limited to, redistribution, reproduction, modification, and public review, are reserved. Disclaimer The information in this document is provided "as is" without warranty of any kind. Chronoplex Software does not accept any responsibility or liability arising from the use of this document. 1 My Family Tree GEDCOM files GEDCOM files produced by My Family Tree are LINEAGE-LINKED GEDCOM 5.5.1 files which use Unicode (UTF-8) encoding with a byte order mark. In the interests of interoperability, files deviate from the GEDCOM 5.5.1 specification in the following cases: 1. <MULTIMEDIA_FILE_REFERENCE> ignores the 30-character limit and uses up to 246-characters before the value is split over multiple lines. This ensures maximum compatibility with other applications. 2. <MULTIMEDIA_FORMAT> is extended to permit any valid file format. 3. <SEX_VALUE> is extended to permit ‘X’ for ‘other’. The term ‘other’ is to be used to describe the biological sex of a person whose biological sex is not exclusively ‘male’ or ‘female’ e.g. intersex. 4. <PEDIGREE_LINKAGE_TYPE> is extended to permit ‘guardian’, ‘step’, and ‘other’. This ensures maximum compatibility with other applications. 5. The INDI.EVEN and FAM.EVEN generic events use an <EVENT_DESCRIPTOR> line value. 6. The INDI.RESI and FAM.RESI residence attributes use an <ATTRIBUTE_DESCRIPTOR> line value. 7. <PLACE_LATITUDE> uses a compass direction N or S and a number 0 to 90. <PLACE_LONGITUDE> uses a compass direction E or W and a number 0 and 180 inclusive. This is in line with the examples in the specification. The numerical part of the coordinate is given to 6 decimal places which is equivalent to ~1 m distance on the ground and more than enough for genealogical purposes. The GEDCOM 5.5.1 specification erroneously limits these fields to size {5:8}, the correct sizes are {2:10} and {2:11} respectively. Some of these behaviours can be adjusted by manually editing the user.config in the local application data. The following settings are provided: Setting Default GedcomExport_UseXSexValue True GedcomExport_UseNonStandardPedigreeLinkageTypes True GedcomExport_UseLongLineValuesForMultimediaFileReference True GedcomExport_UseFileExtensionsForMultimediaFormat True GedcomExport_UseEvenLineValue True GedcomExport_UseResiLineValue True 2 Record Structures of Lineage-Linked Form which have been extended Extensions to existing structures are shown in highlight mode. HEADER:= n HEAD ⋮ _TITL <TEXT> {0:1} ⋮ RECORD:= [ n <<FAM_RECORD>> {1:1} | n <<INDIVIDUAL_RECORD>> {1:1} | n <<MULTIMEDIA_RECORD>> {1:1} | n <<NOTE_RECORD>> {1:1} | n <<REPOSITORY_RECORD>> {1:1} | n <<SOURCE_RECORD>> {1:1} | n <<SUBMITTER_RECORD>> {1:1} | n <<TASK_RECORD>> {1:1} ] FAM_RECORD:= n @<XREF:FAM>@ FAM {1:1} ⋮ +1 _PRIVATE <PRIVATE_FLAG> {0:1} +1 _READONLY <READONLY_FLAG> {0:1} +1 _MSTAT <RELATIONSHIP_STATUS> {0:1} ⋮ 3 INDIVIDUAL_RECORD:= n @<XREF:INDI>@ INDI {1:1} ⋮ +1 _UID <UID> {0:1} +1 _PRIVATE <PRIVATE_FLAG> {0:1} +1 _READONLY <READONLY_FLAG> {0:1} +1 SEX <SEX_VALUE> {0:1} +1 <<A_DNA_STRUCTURE>> {0:M} +1 <<M_DNA_STRUCTURE>> {0:M} +1 <<Y_DNA_STRUCTURE>> {0:M} +1 _IEOT Y {0:1} +1 _PHOTO @<XREF:OBJE>@ {0:1} +2 _FACE <CROP_REGION> {0:1} +1 _CREST @<XREF:OBJE>@ {0:1} ⋮ MULTIMEDIA_RECORD:= n @<XREF:OBJE>@ OBJE {1:1} ⋮ +1 _PRIVATE <PRIVATE_FLAG> {0:1} +1 _READONLY <READONLY_FLAG> {0:1} +1 FILE <MULTIMEDIA_FILE_REFERENCE> {1:1} +2 _FDTE <FILE_DATE > {0:1} +2 _FRTG <FILE_RATING> {0:1} +2 _FPLC <FILE_PLACE> {0:1} +2 FORM <MULTIMEDIA_FORMAT> {1:1} ⋮ Pointers to multimedia records are always used, rather than inline multimedia links. NOTE_RECORD:= n @<XREF:NOTE>@ NOTE {1:1} ⋮ +1 _NCHT Y {0:1} ⋮ REPOSITORY _RECORD:= n @<XREF:REPO>@ REPO {1:1} ⋮ +1 _UID <UID> {0:1} ⋮ SOURCE_RECORD:= n @<XREF:SOUR>@ SOUR {1:1} ⋮ +1 _UID <UID> {0:1} ⋮ 4 Record Structures of Lineage-Linked Form which are new TASK_RECORD:= n @<XREF:TASK>@ _TASK {1:1} +1 _TTIL <TASK_TITLE> {0:1} +1 _TDSC <TASK_DESCRIPTION> {0:1} +1 _TCOM <TASK_COMMENTS> {0:1} +1 _TRST <TASK_RESULTS> {0:1} +1 _TLOC <TASK_LOCATION> {0:1} +1 _TSDT <TASK_START_DATE> {0:1} +1 _TRDT <TASK_REVIEW_DATE> {0:1} +1 _TCDT <TASK_COMPLETED_DATE> {0:1} +1 _TSTS <TASK_STATUS> {0:1} +1 _TPTY <TASK_PRIORITY> {0:1} +1 _TTPE <TASK_TYPE> {0:1} +1 _TCAT <TASK_CATEGORY> {0:1} +1 SOUR @<XREF:SOUR>@ {0:1} +1 REPO @<XREF:REPO>@ {0:1} +1 INDI @<XREF:INDI>@ {0:M} + <<CHANGE_DATE>> {0:1} Tasks may include a single cross-reference to a source and/or repository, and one or more cross-references to any individuals relating to the task. 5 Substructures of Lineage-Linked Form which have been extended Extensions to existing structures are shown in highlight mode. PERSONAL_NAME_STRUCTURE:= n NAME <NAME_PERSONAL> {1:1} ⋮ +1 _FIRN <NAME_PIECE_FIRSTNAME> {0:1} +1 _MIDN <NAME_PIECE_MIDDLENAME> {0:1} +1 _PATN <NAME_PIECE_PATRONYMIC> {0:1} +1 _MATN <NAME_PIECE_MATRONYMIC> {0:1} +1 _RUFNAME <NAME_PIECE_CALLNAME> {0:1} +1 _PRIVATE <PRIVATE_FLAG> {0:1} +1 _READONLY <READONLY_FLAG> {0:1} ⋮ GEDCOM 5.5.1 does not make any distinction between a person’s first names, middle names, patronymic names, matronymic names, or call names, and instead combines them in the NAME tag value or the GIVN tag value. However separate identification of each of these name parts is essential if genealogy applications are to correctly display a person’s name according to cultural rules associated with that name. Additional tags are therefore provided to ensure that all parts of a person’s name can be correctly interpreted. Use of the _FIRN and _MIDN tags is restricted to the case when the GIVN tag value cannot be split at the first white space character to obtain the first name(s) and middle name(s). This avoids unnecessary duplication of information, whilst ensuring complete compatibility with GEDCOM readers which do not support these tags. The _MIDN tag is only used with the _FIRN tag, in other words, a middle name is not permitted without a first name. The combined _FIRN and _MIDN tag values must equal the GIVN tag value i.e. <NAME_PIECE_GIVEN> = [ <NAME_PIECE_FIRSTNAME> | <NAME_PIECE_FIRSTNAME> <NAME_PIECE_MIDDLENAME> ] Any other use of the _FIRN and _MIDN tags is not supported. 6 EVENT_DETAIL:= ⋮ n _RELTYPE <RELATIONSHIP_TYPE> {0:1} n _PRIVATE <PRIVATE_FLAG> {0:1} n _READONLY <READONLY_FLAG> {0:1} n _DESC <TEXT> {0:1} ⋮ n <<EVENT_WITNESS_STRUCTURE>> {0:M} ⋮ n DATE <DATE_VALUE> {0:1} n _DATI <DATE_TIME_INFO> {0:1} ⋮ The _RELTYPE tag is used only with MARR events which include a user defined type. It is used to flag whether the MARR.TYPE line value is a type of other marriage or a type of other relationship. The _DESC tag is used to preserve information stored on an EVEN or RESI tag value in versions of GEDCOM which do not support this. Events may contain references to individuals who witnessed the event in some capacity using the EVENT_WITNESS_STRUCTURE. The _DATI tag is used to store the data required to completely reconstruct the date and time information associated with an event. It is always included in addition to the standard DATE tag. My Family Tree permits date information to be stored in many different calendars and therefore not all dates can be validly expressed using the standard DATE_VALUE. An associated DATE_TIME_INFO value is used to store all the information required to represent the date. If a _DATI tag and value is present, the corresponding DATE tag and value is ignored. The DATE tag value will store a valid GEDCOM representation of the date, where that is possible. 7 Substructures of Lineage-Linked Form which are new M_DNA_STRUCTURE:= n _MTDNA {1:1} +1 _MDSC <DNA_TEST_DESCRIPTION> {0:1} +1 _MNAM <DNA_TEST_NAME_OF_PERSON> {0:1} +1 _MHAP <M_DNA_HAPLOGROUP> {0:1} +1 _MREF <M_DNA_REFERENCE_SAMPLE> {0:1} +1 _MSEQ <DNA_FULL_SEQUENCE> {0:1} +1 <<M_DNA_SNP_STRUCTURE>> {0:M} +1 <<NOTE_STRUCTURE>> {0:M} The results of a mitochondrial DNA test. M_DNA_SNP_ STRUCTURE:= n _MSNP {1:1} +1 _MDIF <M_DNA_DIFFERENCE> {1:1} A difference between a person’s mitochondrial DNA full sequence compared to a reference mitochondrial DNA sequence. Y_DNA_STRUCTURE:= n _YTDNA {1:1} +1 _YDSC <DNA_TEST_DESCRIPTION> {0:1} +1 _YNAM <DNA_TEST_NAME_OF_PERSON> {0:1} +1 _YHAP <Y_DNA_HAPLOGROUP> {0:1} +1 <<Y_DNA_STR_STRUCTURE>> {0:M} +1 <<Y_DNA_SNP_STRUCTURE >> {0:M} +1 <<NOTE_STRUCTURE>> {0:M} The results of a Y-chromosome DNA test. Y_DNA_STR_ STRUCTURE:= n _YSTR {1:1} +1 _YMRK <STR_MARKER> {1:1} +1 _YRPT < STR_REPEAT> {1:1} A short tandem repeat (STR) is a section of DNA which repeats several times in a row on a DNA strand. The STRs present and the number of times they repeat is used distinguish one DNA sample from another. Y_DNA_SNP_ STRUCTURE:= n _YSNP {1:1} +1 _YRSID <SNP_RSID> {1:1} +1 _YPOS <SNP_POSITION> {1:1} +1 _YGEN <SNP_GENOTYPE> {1:1} A single nucleotide polymorphism (SNP) DNA sequence variation occurring when a single nucleotide adenine (A), thymine (T), cytosine (C), or guanine (G) in the genome (or other shared sequence) differs between members of a species or paired chromosomes in a person. 8 A_DNA_STRUCTURE:= n _ATDNA {1:1} +1 _ADSC <DNA_TEST_DESCRIPTION> {0:1} +1 _ANAM <DNA_TEST_NAME_OF_PERSON> {0:1} +1 <<A_DNA_STR_STRUCTURE>> {0:M} +1 <<A_DNA_SNP_STRUCTURE >> {0:M} +1 <<NOTE_STRUCTURE>> {0:M} The results of an autosomal DNA test. A_DNA_STR_ STRUCTURE:= n _ASTR {1:1} +1 _AMRK <STR_MARKER> {1:1} +1 _ARPT < STR_REPEAT> {1:1} A short tandem repeat (STR) is a section of DNA which repeats several times in a row on a DNA strand. The STRs present and the number of times they repeat is used distinguish one DNA sample from another.