FAQ


What about FHISO?

We like FHISO, and we're trying to do what we can to support their vision. We're looking forward to seeing what comes of their good efforts. See Whence FHISO.

Is GEDCOM X backwards-compatible? Can GEDCOM X be read by consumers of legacy GEDCOM?

No, a new parser is needed. But there is a lossless conversion from legacy GEDCOM to GEDCOM X. And there are open source libraries available for working with GEDCOM X to help ease the pain of migration.

Does GEDCOM X define a file format so I can save my data on my computer and work with it using my favorite applications?

Yes. And it's designed to address the major issues with legacy GEDCOM such as the lack of a well-defined source model, insufficient support for the proof standard, and no way to enclose multimedia files (e.g. images, audio, video, etc.).

See file-format-specification.

How do I contribute? What if GEDCOM X is missing something?

We'd love to have you participate! Have you checked out the community documentation?

What licenses govern GEDCOM X?

Code is opened under an Apache II license. Other content is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

What's the governance model for GEDCOM X?

The project is being managed in an open source manner with requirements and contributions being provided by the community. The licenses are open and the process is transparent, and feedback is readily invited. FamilySearch is the current admin for the project.

What's up with the name "GEDCOM X"?

Well...

edit this page