Filename extension | .ged |
---|---|
Developed by | LDS FHD |
Initial release | 1984; 35 years ago |
Latest release | GEDCOM 5.5 Standard + Two Errata Sheet (10 January 1996; 23 years ago) |
Type of format | Genealogy data exchange |
Standard | De facto[1] |
Website | familysearch.org/developers/docs/gedcom/ |
sample.ged |
Meaning | |
---|---|
Red | Old Standard/Draft; not supported |
Yellow | Old Standard; still supported |
Green | Current Standard |
Blue | Future Draft |
GEDCOM Version | Release Date | Notes |
---|---|---|
1.0[22] | 1984[23] | - |
2.0[22] | Dec 1985[24] | PAF 2.0 |
2.1 | Feb 1987[24] | GEDCOM for PAF 2.1 |
2.3 Draft | 7 August 1985[25] | with PAF2.0 GEDCOM implementation conventions |
2.4 Draft | 13 December 1985[25] | with PAF2.0 GEDCOM implementation conventions |
3.0 Standard[22] | 9 October 1987[26] | PAF 2.0 and 2.1 implementation of 3.0 |
4.0 Standard | August 1989 | PAF 2.1 - 2.31 |
4.1 Draft[27] | - | - |
4.2 Draft[28] | 25 January 1990[29] | - |
5.0 Draft[22] | 31 December 1991[25] | lineage-linked structures were introduced.[30] |
5.1 Draft | 18 September 1992[24] | - |
5.2 Draft | 22 January 1992[31] | - |
5.3 Draft | 4 November 1993[32] | Unicode standard (ISO/IEC 10646) was introduced as an additional character set. |
5.4 Draft | 21 August 1995[33] | - |
5.5 Standard | 11 December 1995[34] | PAF 3, 4 and 5 |
5.5 Standard | 2 January 1996[35][36] | PAF 3, 4 and 5 / 5.5 Standard[37] |
GEDCOM (Future Direction) Draft[30][38] | 1 May 1998[39][40] | 'it used an entirely new data model'[41] |
5.5.1 Draft[42][43] | 2 October 1999[14] | Used by FamilySearch.org[18]UTF-8 added as an approved character encoding. |
5.6 Private Draft | -[44] | 'Jed Allen sent those two files to a few people only for sort of 'private comments'[45] |
6.0 XML Draft | 28 December 2001[46] | Was not a complete specification, and not recommended to begin to software implementations. |