Introducing FamilySearch GEDCOM Version 7.0 a long-awaited upgrade

 

Some introductory comments

Before I get into the great news about the release of FamilySearch GEDCOM Versions 7.0 hereinafter “GEDCOM”, I need to give some personal and general history to put the new Version 7.0 into perspective. Also, I should mention right here at the beginning of this post the word GEDCOM is an acronym for GEnealogical Data Communication. GEDCOM is also the name of a standard programming specification usually referred to as the “GEDCOM Standard or GEDCOM” created by The Church of Jesus Christ of Latter-day Saints and FamilySearch as the specifications of a file standard used for exchanging genealogical data between different desktop genealogical family tree software and websites. The GEDCOM Standard Specifications are designed to be used by programmers when modifying their own programs and websites to share information between different genealogy software and websites.

Official Release Statement from FamilySearch received via email

FamilySearch International is pleased to announce the release of FamilySearch GEDCOM 7.0 (Genealogical Data Communications). The latest version allows zip packaging capabilities for photos and files with genealogical information, plus new tools, and a public GitHub repository for ongoing maintenance. Technical information, specifications, tools, and guides can be found at GEDCOM.io. 

At RootsTech 2020, FamilySearch launched an effort to create a new version of GEDCOM based on the 5.5.1 version that would include: 1) new expressivity, flexibility, and compatibility; 2) zip packaging of associated images and other files with the related GEDCOM file; and 3) public access using a GitHub repository. Many industry software providers and key influencers participated, and the initiative concluded May 15, 2021, with the completion of this comprehensive effort.

FamilySearch GEDCOM 7.0 is the outcome of those efforts and includes the following new enhancements:

• Zip packaging capabilities for photos and files have been added.

• Notes have been expanded for more versatile use and styling of text.

• Tools, sample files, sample code, and self-testing guides are included.

• The GEDCOM specification and any code available from FamilySearch based on the specification is subject to the terms and conditions of the Apache License, Version 2.0.

• Ambiguities in the GEDCOM Version 5.5.1 specification have been removed.

• A public GitHub repository generates maintenance requests and on-going discussions about future features.

Users of FamilySearch GEDCOM 7.0 will be able to import files from older GEDCOM versions. However, users of older versions of GEDCOM will not be able to import from FamilySearch GEDCOM 7.0.

Why am I involved with GEDCOM?

Beginning in 1982, I was the owner and operator of an Apple dealership in Mesa, Arizona. We sold a variety of computer models from different manufacturers, not just Apple. About that same time, I began my continuing interest in genealogical research. As a result of that interest, I became aware of the GEDCOM Standard shortly after Personal Ancestral File (PAF) 2.0 was released in April of 1986. At that time, the GEDCOM Standard had been available since 1984. Another version of GEDCOM for PAF 2.1 was released in February 1987. PAF 2.1 was also released for the Macintosh in 1987 with supported and early specification of GEDCOM 4.0. 

At the store, we soon realized that there was a need for help in transferring genealogy files between different computers. Due to our store’s combined expertise with the new home or personal computers and my interest in genealogy, my staff and I started learning how to use GEDCOM to transfer data between Apple computers and DOS computers such as the IBM PC and providing that expertise as a service to anyone who needed a file transfer. Because our store was only a few blocks away from the Mesa, Arizona Temple of The Church of Jesus Christ of Latter-day Saints and also the Mesa Family History Center, there was a significant demand for our transfer services through word-of-mouth referrals. 

As results of this perceived need for help with file transfers, on a trip to Salt Lake City in about 1987, I went to the Church Office Building and found the department that was working on the GEDCOM Standard and obtained a printed copy of the GEDCOM Standard Specifications. Using the information from the Specifications, we were able to more successfully transfer information between the different operating systems and software programs using floppy disks and began doing so for anyone who needed help. This continued for many years until I went back to practicing law about 1998. However, because I still owned both Apple and PC computers, I continued to transfer data for anyone who needed help until the technology obviated the need. Remarkably, it has only been very recently that the need to extract a GEDCOM file from a floppy disk became very rare even through floppy disk storage was discontinued years ago. Obviously, the transfer process moved from floppy disks to hard disks and ultimately, online. 

Because of all this early experience and continued interest in GEDCOM and transferring files between different operating systems and computers, over the years, I have been actively involved in promoting computer data standards. About two years ago, I began working with a FamilySearch Committee on drafting an updated GEDCOM Standard. 

That brings me to the present. The GEDCOM Standard Specifications were last updated in 1996 with the introduction of Version 5.5. Now, after a lot of work by a lot of people we have a NEW version: GEDCOM Version 7.0. 

First, if you are wondering what all this means, here is my short description of the GEDCOM Standard

As my history above illustrates, different genealogy programs or websites have different file formats for storing data. If you are using one genealogy software program or website and you want to share your information (data) with someone who is using a different software program or website, you have a challenge. Unless you want to print out your data and let the other person manually enter the information into their own software program or website, you need a way to electronically transfer the data. The GEDCOM Standard was developed to help solve that problem. If the software program you are using supports the GEDCOM Standard, you can create a GEDCOM file and if the other person also has a software program that supports the GEDCOM Standard, they can upload the file data into their own software program or file. The key here is that most of the genealogy programs or websites available today support the GEDCOM Standard and can exchange data. Unless you are a computer programmer, what you need to know is that by downloading a GEDCOM file, anyone with a GEDCOM compatible software program or website can upload your information. 

Why did we wait so long to come up with a new version?

I don’t really know all of the answers to this question, but I do know that computer technology had to finally have the capacity and ease of use to transfer files containing media components such as photos and digitized documents, before it was practical to update the GEDCOM Standard. I also know that because of the internet, programmers were more focuses on making connections directly between websites than in upgrading the GEDCOM Standard which had been serviceable for many years. 

Why is GEDCOM referred to as a GEDCOM Standard?

In order to communicate between different websites and software programs it was first necessary to establish a common set of software programming standards that could be adopted by all the different software programs and websites. The GEDCOM Standard is a cooperative effort by developers and programmers to establish this common way of organizing the data for genealogy software that allows their data to be consistent with the GEDCOM Standard Specifications. 

What does this mean to the average user of genealogy software or websites?

With the introduction of GEDCOM Version 7.0 release candidate, the standard will now support the inclusion of media using a NEW utility called GEDZip. Previously, the older versions of the GEDCOM Standard did not have the ability to include, maintain, store, and share media files. With addition of the GEDZip utility, you can now link media from the Internet as well as from local files and include them with your GEDCOM Standard data files. What most users need to know is that more of their data will be able to be transferred from program to program and website to website, including their document images, photos, and other media items. 

Other valuable new features

In addition, there have been other standards added to the original 5.5 version of GEDCOM to include the new features. Some of these features are technical in nature. Here is a short explanation, in somewhat technical terms of the new features. 

New features add new semantic power to GEDCOM, allowing GEDCOM Version 7.0 release candidate to represent concepts Version 5.5 could not represent. All dates now have date phrases, including date ranges and periods. Identifier RIN, RFN, and AFN have been combined into a new EXID, which can now also be used to link to external databases and websites. All text payloads may contain line breaks. LANG payloads are now language tags. Many other positive changes can be reviewed in the ChangeLog in the main public repository.

Why am I involved in all this?

You may wonder why a retired trial attorney and business owner, who has a limited knowledge of programming, is involved and has been involved in the development of the GEDCOM Standard. That is a pretty good question, and my answer is partially why I included a short history about my involvement with GEDCOM. In addition to my legal background, I also have a B.S. Degree in Spanish and an M.A. Degree in Linguistics. I am also a professional photographer. I have been involved in genealogical research for more than 40 years. My role in the development was to provide information about historical use of the program and also to address issues concerning the concepts and impact of the program’s concepts on the genealogical community. I was a member of the final Steering Committee preparing for the release of the update. 

What does the average genealogy computer user need to do now?

Not much if anything. I you have ever used a genealogy program before and created a GEDCOM file, one of the committee members, Luther A. Tychonievich, an Assistant Professor in Computer Science at the University of Virginia, has written a GEDCOM Translate program that will update the existing Version 5.5 GEDCOM files to the new version 7.0 release candidate.

In the future, you may sooner or later run into the need to create a GEDCOM file and it is possible that the program you are backing up will use GEDCOM Version 7.0. That will not make any visible difference to you when you follow the instructions from your genealogy program to create the GEDCOM file. Existing GEDCOM Files will also be able to be updated. 

That is enough for now. Look for more announcements, online support, classes, and presentations about GEDCOM Version 7.0 and GEDZip soon. I will be writing a lot more about GEDCOM Version 7.0 with GEDZip in the very near future.

FamilySearch GEDCOM 7.0 is copyrighted.

© 1987, 1989, 1992, 1993, 1995, 1999, 2019, and 2021 by Intellectual Reserve, Inc. All rights reserved. A service provided by The Church of Jesus Christ of Latter-day Saints.

General information can be found at GEDCOM.info.

Helpful Sources

General Info: GEDCOM.info

Technical Specs, Tools and Guides: GEDCOM.io
Community:  GEDCOM General Google Group and GitHub Public GEDCOM Repository

Email: GEDCOM@FamilySearch.org