The official FamilySearch GEDCOM specification for exchanging genealogical data.

This repository is for the collaborative development of the FamilySearch GEDCOM specification. If you are looking for the specification itself, see https://gedcom.io.

If you are looking for FamilySearch's GEDCOM 5.5.1 Java parser, which previously had this same repository name, see https://github.com/familysearch/gedcom5-java

• changelog.md is a running log of major changes made to the specification.
• specification/ contains the FamilySearch GEDCOM specification:
  • specification/gedcom.md is the source document used to define the FamilySearch GEDCOM specification. It is written in pandoc-flavor markdown and is intended to be more easily written than read.
  • In a local check-out, this is also where the build scripts place rendered versions of gedcom.md; see releases for a pre-rendered copy of these.
• build/ contains files needed to render the specification
  • See build/README.md for more
• extracted-files/ contains digested information automatically extracted from the specification. All files in this directory are automatically generated by scripts in the build/ directory.
  • extracted-files/grammar.abnf contains all the character-level ABNF for parsing lines and datatypes.
  • extracted-files/grammar.gedstruct contains a custom structure organization metasyntax.
  • extracted-files/tags/ contains summary information for each https://gedcom.io/terms/-based URI defined in the specification.

• main contains the current release. Patch versions are generally pushed directly to main upon approval.

• next-minor contains a working draft of the next minor release. Changes from main have been discussed and approved by the working group supervising the next minor release, but have not been fully vetted and approved for inclusion in the standard and may change at any time without notice.

• next-major contains a working draft of the next major release. Changes from main have been discussed and approved by the working group supervising the next major release, but have not been fully vetted and approved for inclusion in the standard and may change at any time without notice.

• All other branches are for conversation drafts that may or may not be incorporated into a future version of the specification.