Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time
97 lines (74 sloc) 4.91 KB

GEDCOM X Event Types


This document enumerates a set of event types to be used for genealogical data exchange, and requests discussion and suggestions for improvements.

The current state of this document is as a "stable draft", and as such, the document may be subject to limited changes, BUT NOT backwards-incompatible changes, according to the discussion and suggestions for improvement.

Copyright Notice

Copyright Intellectual Reserve, Inc.


This document is distributed under a Creative Commons Attribution-ShareAlike license. For details, see:


The GEDCOM X Event Types spec specifies a set of enumerated values that identify common event types that are relevant to genealogical research. An "event" is an occurrence that happened at a specific time or period of time, often at a specific place or set of places. Genealogically relevant events are often described by referencing the persons that played a role in that event. Hence, events often refer to persons and might infer relationships, but events are described independently of those persons and relationships. The spec includes notational conventions, event types, and the URI reference used to identify event types.

1. Introduction

An enumeration of types of events provides the means for descriptions of historical events to be semantically processed by applications, rather than being only interpreted by people. This specification provides such an enumeration by identifying specific event types and defining the semantic significance of each type.

1.1 Identifier and Version

The identifier for this specification is:

For convenience, this specification may be referred to as "GEDCOM X Event Types 1.0". This specification uses "GEDCOM X Event Types" internally.

1.2 Notational Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC2119, as scoped to those conformance targets.

1.2.1 The URI Reference

The Uniform Resource Identifier ("URI") is used to identify event types. The URI is specified by RFC 3986. This specification uses the term "URI" to refer to both a "URI" and a "URI Reference" as defined by RFC 3986.

2. Event Types

The following event types are specified:

URI description An adoption event. An adult christening event. An annulment event of a marriage. A baptism event. A bar mitzvah event. A bat mitzvah event. A birth event. A an official blessing event, such as at the hands of a clergy member or at another religious rite. A burial event. A census event. A christening event at birth. Note: use AdultChristening for a christening event as an adult. A circumcision event. A confirmation event (or other rite of initiation) in a church or religion. A cremation event after death. A death event. A divorce event. A divorce filing event. A education or an educational achievement event (e.g. diploma, graduation, scholarship, etc.). An engagement to be married event. An emigration event. An excommunication event from a church. A first communion event. A funeral event. An immigration event. A land transaction event. A marriage event. A military award event. A military discharge event. A mission event. An event of a move (i.e. change of residence) from a location. An event of a move (i.e. change of residence) to a location. A naturalization event (i.e. acquisition of citizenship and nationality). An ordination event. A retirement event.