Email: Mail: [email protected] Family History Department GEDCOM Coordinator%3T Telephone: 50 East North Temple Street Salt Lake City. The GEDCOM specification was made purposefully flexible to support many ways of encoding data, particularly in. This chapter describes the specific tag, value, and pointer combinations used for exchanging lineage-linked genealogical information in the GEDCOM format.

Author: Nenris Dilrajas
Country: Qatar
Language: English (Spanish)
Genre: Politics
Published (Last): 23 September 2010
Pages: 342
PDF File Size: 4.85 Mb
ePub File Size: 9.8 Mb
ISBN: 715-4-24995-277-2
Downloads: 42937
Price: Free* [*Free Regsitration Required]
Uploader: Kazragul

The GEDCOM specification was made purposefully flexible to support many ways of encoding data, particularly in the area of sources. Please help improve this section by adding citations to reliable sources.

The GEDCOM Standard Release Table of Contents

It includes data formats that facilitate basing family trees on sources and records both physical artifacts and digital artifactssupport for sharing and linking data online, and an API.

However not all elements within these records are processed. A GEDCOM X file is xpecification bundle of digital genealogical resources, such as data that has been gathered through the genealogical research process about persons, relationships, sources, images, etc.

Fri, 15 Feb Genealogy articles needing expert attention Computer-related introductions in Computer file formats Genealogy and The Church of Jesus Christ of Latter-day Saints Genealogy software.

This site uses Akismet to reduce spam. GEDCOM does not explicitly support data representation of many types of close interpersonal relationshipssuch as same-sex marriagesdomestic partnershipscohabitationpolyamorypolygamy or incest.

The age of the individual at the time an event occurred, or the age listed in the specificagion. Wed, 24 Jan The GEDCOM X date format specifies a mechanism for representing dates, with specific attention given to the need to represent genealogical dates. Such relationships can only be represented using the generic ASSO tag used for any type of relationship.


First, newer versions of the standard allow data to be stored in Unicode or, more recently, UTF-8so text in any language can be stored. This data model is based on the nuclear family and the individual.

The GEDCOM specification

Support for Gedcom 5. A unique permanent record file number of an individual record stored in Ancestral File. Familypedia FamilySearch Rodovid Werelate.

For example, if an individual’s birth date was recorded as 10 January on the birth certificate, but 11 January on the death certificate, two BIRT records for that individual would be included, the first with the 10 January date and giving the birth certificate as the source, and the second specivication the 11 January date and giving the death certificate as the source.

Uniform use of Unicode would allow for the usage of international character sets. While GEDCOM X and several other specifications have been suggested as replacements, the current version remains the industry standard 20 years on.

GEDCOM X Specifications

Allen” Brigham Young University – Date: Webarchive template wayback links All articles with dead external links Articles with dead external links from August Articles with permanently dead external links All articles lacking reliable references Articles lacking reliable references from August Articles needing speciification attention with no reason or talk parameter Articles needing expert attention from February All articles needing expert attention Articles needing additional references from February All articles needing additional references All sppecification with unsourced statements Articles with unsourced statements from February Embedding multimedia directly in the GEDCOM file makes transmission of data easier, in that all of the information including the multimedia data is in one file, but the resulting file can be enormous.


Examples of this kind of metadata include:. Tue, 20 Feb Views Read Edit View history. The GEDCOM standard allows for specificattion specification of multiple opinions or conflicting data, simply by specifying multiple records of the same type.

This section does not cite any sources. Although it is event based, it is still a model built on assumed reality rather than evidence. For example, in the case that a person has had two relationships, both with unknown dates, but from descriptions it gfdcom known that the second one is indeed the second one.

This is designed to assist software with a financial commitment to GEDCOM and prevent it getting left behind as further standards evolve. Printing trees with PAF?

geedcom The data format for the resource. Please add a reason or a talk parameter to this template to explain the issue with the section.

The GEDCOM Standard Release 5.5

The following record types are parsed: Conflicting data may also specifidation the result of user errors. Linking multimedia keeps the size of the GEDCOM file under control, but then when transmitting the file, the multimedia objects must either be transmitted separately or archived together with the GEDCOM into one larger file. Tue, 11 Jul 89 The preferred record is usually listed first.

Genealogical data is represented using data types such as persons, relationships, and sources. Examples of this kind of metadata include: Household specificarion finder — Register: Identifiers for the resource.

Archived at the Wayback Machine.