diff --git a/_pages/changelog.md b/_pages/changelog.md
index daa3c3c..0ec29eb 100644
--- a/_pages/changelog.md
+++ b/_pages/changelog.md
@@ -4,6 +4,25 @@ permalink: /changelog/
 sidebar:
 nav: "changelog"
 ---
+# Version 7.0.15
+
+- Clarified that `FORM`.`MEDI` describe the original medium, not the derived medium, when used with derived files.
+
+- Clarified the meaning of the `WWW` structure, which previously only mentioned its payload datatype.
+
+- Clarified `PLAC` to both define "jurisdiction" and document its meaning in the absence of a `PLAC`.`FORM`.
+
+- Clarified what the term "principal date" means in different contexts in the definition of `g7:DATE`.
+
+- Updated `NICK` to no longer suggest that some names are "improper" and to document the diversity of views in what a "nickname" is.
+
+- Removed confusing reference to superstructures in the meaning of a documented extension tag.
+
+- Added ABNF for more datatypes and updated DIGIT's capitalization for compatibility with more ABNF toolchains.
+
+- Various typo corrections.
+
+
 # Version 7.0.14
 
 - Recommend that `NO XYZ` only be used where `XYZ` is permitted (its meaning is undefined elsewhere).
@@ -14,7 +33,7 @@ nav: "changelog"
 
 - Refactor the enumeration tags `CENS`, `EVEN`, `FACT`, `NCHI`, and `RESI` to have different URIs, removing a previous parsing ambiguity. This changes neither the set of tags permitted in any enumeration set nor those tags' meaning, only how they are specified to better support automated tooling.
 
-- Deprecate extension-defined substructures using `stdTag` in a way incompatible with any standard definition of that tag. The now-deprecated use was common in 5.5.1 and is permitted in 7.0, but can prevent extension structures from being adopted as-is as new standard structures in future versions of the specification.
+- Deprecate the ability to use extension-defined substructures `stdTag` in a way incompatible with any standard definition of that tag. The now-deprecated use was common in 5.5.1 and is permitted in 7.0, but can prevent extension structures from being adopted as-is as new standard structures in future versions of the specification.
 
 - Clarify that the "applies to" and "status" columns of `g7:enumset-ord-STAT` are recommendations, not restrictions.
 
@@ -100,7 +119,7 @@ nav: "changelog"
 
 - Changes anticipating a coming extension registry:
 
-    - Add URIs for sets of enumeration values. This has changes some fragment identifiers in the HTML version of the spec and could cause hotlinks to the specific sections discussing enumeration sets to change.
+    - Add URIs for sets of enumeration values. This changed some fragment identifiers in the HTML version of the spec and could cause hotlinks to the specific sections discussing enumeration sets to change.
 
     - Many updates to the YAML format served at <https://gedcom.io/terms/v7/record-INDI> and at the other URIs in the specification.
 
@@ -166,7 +185,7 @@ nav: "changelog"
         - `mul` can be used if there is no single primary language, but is unlikely to provide practical functionality beyond `und`.
         - `zxx` can be used for ASCII art and other non-language text, and can improve accessibility for screen readers.
 
-- Clarify that empty *payloads* are encoded as missing `LineVal`s and empty `LineVal`s are not been permitted; this has been true since 7.0.0 but was easily overlooked in the previous text.
+- Clarify that empty *payloads* are encoded as missing `LineVal`s and empty `LineVal`s are not permitted; this has been true since 7.0.0 but was easily overlooked in the previous text.
 
 - Note cases where the same couple might be the partners in multiple `FAM` records.
 
@@ -247,7 +266,7 @@ nav: "changelog"
 
 # Version 7.0.0
 
-As a major release and the first update to the specification in 20 years, there a many changes in this version.
+As a major release and the first update to the specification in 20 years, there are many changes in this version.
 
 This version is the first version to use [semantic versioning](https://semver.org/).
 7 was chosen as the new major version number because 1 through 6 were each used previously, some for released standards and others for abandoned drafts.
@@ -329,7 +348,7 @@ Earlier versions of GEDCOM predated language tags, media types, and Unicode beca
 
 ## New Extensibility
 
-- Every standard tag now has a single "default" meaning, even if it also has additional meanings in other contexts. Tags conforming to this default meaning can now be used by extensions as substructures of structures with extention tags.
+- Every standard tag now has a single "default" meaning, even if it also has additional meanings in other contexts. Tags conforming to this default meaning can now be used by extensions as substructures of structures with extension tags.
 
 - Extension tags remain in a backwards-compatible way, but should additionally be paired with a URI to avoid name collisions and provide documentation.
 
@@ -353,7 +372,7 @@ Earlier versions of GEDCOM predated language tags, media types, and Unicode beca
 
 - Age phrases are now only phrases, not long-hand terms for specific age ranges
 
-- Previously registered values (APPROVED_SYSTEM_ID, RECEIVING_SYSTEM_NAME, etc) are kept as-is if present; new ones are URIs instead of having a separate registration process
+- Previously registered values (APPROVED_SYSTEM_ID, RECEIVING_SYSTEM_NAME, etc.) are kept as-is if present; new ones are URIs instead of having a separate registration process
 
 - `RESI` may have a payload, just as all other attributes may
 
@@ -371,7 +390,7 @@ Various ambiguities were identified in version 5.5.1: some due to poor wording,
 
 - Dual-year dates were used with widely different semantics and have been replaced by more flexibility in date phrases.
 
-- `SEX` is now unambiguously biological sex at birth; all other related concepts (gender identity, sexual preference, sex reassignment, etc) are time-varying attributes and to be stored in an individual attribute instead
+- `SEX` is now unambiguously biological sex at birth; all other related concepts (gender identity, sexual preference, sex reassignment, etc.) are time-varying attributes and to be stored in an individual attribute instead
 
     Note that new tags were not introduced for gender-related attributes. It is not yet clear what the correct set of attribute types should be given the evolving and regionally-specific understanding of these concepts. The generic `FACT` is recommended for these concepts instead. 
 
diff --git a/_pages/tag-def/ABBR.md b/_pages/tag-def/ABBR.md
index 67397ee..1fb9e92 100644
--- a/_pages/tag-def/ABBR.md
+++ b/_pages/tag-def/ABBR.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/record-SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ADDR.md b/_pages/tag-def/ADDR.md
index ddd0249..598ffce 100644
--- a/_pages/tag-def/ADDR.md
+++ b/_pages/tag-def/ADDR.md
@@ -119,6 +119,8 @@ superstructures:
   "https://gedcom.io/terms/v7/WILL": "{0:1}"
   "https://gedcom.io/terms/v7/record-REPO": "{0:1}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ADOP-FAMC.md b/_pages/tag-def/ADOP-FAMC.md
index dfe62c8..3aa51aa 100644
--- a/_pages/tag-def/ADOP-FAMC.md
+++ b/_pages/tag-def/ADOP-FAMC.md
@@ -38,6 +38,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/ADOP": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ADOP.md b/_pages/tag-def/ADOP.md
index 50df17d..6999772 100644
--- a/_pages/tag-def/ADOP.md
+++ b/_pages/tag-def/ADOP.md
@@ -58,6 +58,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ADR1.md b/_pages/tag-def/ADR1.md
index ecded3c..7c2f45a 100644
--- a/_pages/tag-def/ADR1.md
+++ b/_pages/tag-def/ADR1.md
@@ -40,6 +40,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/ADDR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ADR2.md b/_pages/tag-def/ADR2.md
index 7c32cab..061d9d8 100644
--- a/_pages/tag-def/ADR2.md
+++ b/_pages/tag-def/ADR2.md
@@ -40,6 +40,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/ADDR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ADR3.md b/_pages/tag-def/ADR3.md
index e121d87..ecbdc77 100644
--- a/_pages/tag-def/ADR3.md
+++ b/_pages/tag-def/ADR3.md
@@ -40,6 +40,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/ADDR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/AGE.md b/_pages/tag-def/AGE.md
index 9d16201..94aee7f 100644
--- a/_pages/tag-def/AGE.md
+++ b/_pages/tag-def/AGE.md
@@ -70,6 +70,8 @@ superstructures:
   "https://gedcom.io/terms/v7/SSN": "{0:1}"
   "https://gedcom.io/terms/v7/WIFE": "{1:1}"
   "https://gedcom.io/terms/v7/WILL": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/AGNC.md b/_pages/tag-def/AGNC.md
index 5ff6767..6ad88d2 100644
--- a/_pages/tag-def/AGNC.md
+++ b/_pages/tag-def/AGNC.md
@@ -84,6 +84,8 @@ superstructures:
   "https://gedcom.io/terms/v7/RETI": "{0:1}"
   "https://gedcom.io/terms/v7/SSN": "{0:1}"
   "https://gedcom.io/terms/v7/WILL": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ALIA.md b/_pages/tag-def/ALIA.md
index 92fc5f9..209d796 100644
--- a/_pages/tag-def/ALIA.md
+++ b/_pages/tag-def/ALIA.md
@@ -45,6 +45,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ANCI.md b/_pages/tag-def/ANCI.md
index 01c03bb..c3e1317 100644
--- a/_pages/tag-def/ANCI.md
+++ b/_pages/tag-def/ANCI.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ANUL.md b/_pages/tag-def/ANUL.md
index 64372b8..9b6b009 100644
--- a/_pages/tag-def/ANUL.md
+++ b/_pages/tag-def/ANUL.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ASSO.md b/_pages/tag-def/ASSO.md
index 97f6385..bd8e16f 100644
--- a/_pages/tag-def/ASSO.md
+++ b/_pages/tag-def/ASSO.md
@@ -113,6 +113,8 @@ superstructures:
   "https://gedcom.io/terms/v7/WILL": "{0:M}"
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/AUTH.md b/_pages/tag-def/AUTH.md
index a09a09a..80d64d4 100644
--- a/_pages/tag-def/AUTH.md
+++ b/_pages/tag-def/AUTH.md
@@ -33,6 +33,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/record-SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/BAPL.md b/_pages/tag-def/BAPL.md
index 88a652e..cd06751 100644
--- a/_pages/tag-def/BAPL.md
+++ b/_pages/tag-def/BAPL.md
@@ -40,6 +40,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/BAPM.md b/_pages/tag-def/BAPM.md
index 970783d..a357b54 100644
--- a/_pages/tag-def/BAPM.md
+++ b/_pages/tag-def/BAPM.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/BARM.md b/_pages/tag-def/BARM.md
index f059b65..9471e83 100644
--- a/_pages/tag-def/BARM.md
+++ b/_pages/tag-def/BARM.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/BASM.md b/_pages/tag-def/BASM.md
index b661a8c..7b48246 100644
--- a/_pages/tag-def/BASM.md
+++ b/_pages/tag-def/BASM.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/BIRT.md b/_pages/tag-def/BIRT.md
index 2d8db8b..c4cfa96 100644
--- a/_pages/tag-def/BIRT.md
+++ b/_pages/tag-def/BIRT.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/BLES.md b/_pages/tag-def/BLES.md
index 9abcac1..5dbfba5 100644
--- a/_pages/tag-def/BLES.md
+++ b/_pages/tag-def/BLES.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/BURI.md b/_pages/tag-def/BURI.md
index deab965..25b4168 100644
--- a/_pages/tag-def/BURI.md
+++ b/_pages/tag-def/BURI.md
@@ -64,6 +64,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CALN.md b/_pages/tag-def/CALN.md
index bb8753f..fc4e80f 100644
--- a/_pages/tag-def/CALN.md
+++ b/_pages/tag-def/CALN.md
@@ -33,6 +33,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/REPO": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CAST.md b/_pages/tag-def/CAST.md
index 5c2f6a6..2f94d3c 100644
--- a/_pages/tag-def/CAST.md
+++ b/_pages/tag-def/CAST.md
@@ -57,6 +57,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CAUS.md b/_pages/tag-def/CAUS.md
index 11593ed..574d498 100644
--- a/_pages/tag-def/CAUS.md
+++ b/_pages/tag-def/CAUS.md
@@ -82,6 +82,8 @@ superstructures:
   "https://gedcom.io/terms/v7/RETI": "{0:1}"
   "https://gedcom.io/terms/v7/SSN": "{0:1}"
   "https://gedcom.io/terms/v7/WILL": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CHAN.md b/_pages/tag-def/CHAN.md
index 143d04e..93a673f 100644
--- a/_pages/tag-def/CHAN.md
+++ b/_pages/tag-def/CHAN.md
@@ -48,6 +48,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-SNOTE": "{0:1}"
   "https://gedcom.io/terms/v7/record-SOUR": "{0:1}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CHIL.md b/_pages/tag-def/CHIL.md
index 0a3f3ca..bfd4ab2 100644
--- a/_pages/tag-def/CHIL.md
+++ b/_pages/tag-def/CHIL.md
@@ -32,6 +32,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CHR.md b/_pages/tag-def/CHR.md
index 34b8c8c..17fbce7 100644
--- a/_pages/tag-def/CHR.md
+++ b/_pages/tag-def/CHR.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CHRA.md b/_pages/tag-def/CHRA.md
index faac74d..7a43761 100644
--- a/_pages/tag-def/CHRA.md
+++ b/_pages/tag-def/CHRA.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CITY.md b/_pages/tag-def/CITY.md
index b1cadba..5614872 100644
--- a/_pages/tag-def/CITY.md
+++ b/_pages/tag-def/CITY.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/ADDR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CONF.md b/_pages/tag-def/CONF.md
index 9fe3203..ad11572 100644
--- a/_pages/tag-def/CONF.md
+++ b/_pages/tag-def/CONF.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CONL.md b/_pages/tag-def/CONL.md
index 4bb6601..188e63b 100644
--- a/_pages/tag-def/CONL.md
+++ b/_pages/tag-def/CONL.md
@@ -40,6 +40,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CONT.md b/_pages/tag-def/CONT.md
index 19f2581..c01d803 100644
--- a/_pages/tag-def/CONT.md
+++ b/_pages/tag-def/CONT.md
@@ -31,6 +31,8 @@ payload: null
 substructures: {}
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/COPR.md b/_pages/tag-def/COPR.md
index df6cd17..def2a56 100644
--- a/_pages/tag-def/COPR.md
+++ b/_pages/tag-def/COPR.md
@@ -32,6 +32,8 @@ substructures: {}
 superstructures:
   "https://gedcom.io/terms/v7/HEAD": "{0:1}"
   "https://gedcom.io/terms/v7/HEAD-SOUR-DATA": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CORP.md b/_pages/tag-def/CORP.md
index 4dbbc1c..d5c84d9 100644
--- a/_pages/tag-def/CORP.md
+++ b/_pages/tag-def/CORP.md
@@ -36,6 +36,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD-SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CREA.md b/_pages/tag-def/CREA.md
index 66001cc..9810d83 100644
--- a/_pages/tag-def/CREA.md
+++ b/_pages/tag-def/CREA.md
@@ -41,6 +41,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-SNOTE": "{0:1}"
   "https://gedcom.io/terms/v7/record-SOUR": "{0:1}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CREM.md b/_pages/tag-def/CREM.md
index b2f01c2..25e9825 100644
--- a/_pages/tag-def/CREM.md
+++ b/_pages/tag-def/CREM.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CROP.md b/_pages/tag-def/CROP.md
index 307a9be..d730c7e 100644
--- a/_pages/tag-def/CROP.md
+++ b/_pages/tag-def/CROP.md
@@ -55,6 +55,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/OBJE": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/CTRY.md b/_pages/tag-def/CTRY.md
index 4e0afe3..34423dd 100644
--- a/_pages/tag-def/CTRY.md
+++ b/_pages/tag-def/CTRY.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/ADDR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DATA-EVEN-DATE.md b/_pages/tag-def/DATA-EVEN-DATE.md
index 8731951..b838968 100644
--- a/_pages/tag-def/DATA-EVEN-DATE.md
+++ b/_pages/tag-def/DATA-EVEN-DATE.md
@@ -32,6 +32,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/DATA-EVEN": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DATA-EVEN.md b/_pages/tag-def/DATA-EVEN.md
index ec769a3..29e2d21 100644
--- a/_pages/tag-def/DATA-EVEN.md
+++ b/_pages/tag-def/DATA-EVEN.md
@@ -38,6 +38,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/DATA": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DATA.md b/_pages/tag-def/DATA.md
index ff5c998..7693cee 100644
--- a/_pages/tag-def/DATA.md
+++ b/_pages/tag-def/DATA.md
@@ -36,6 +36,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DATE-exact.md b/_pages/tag-def/DATE-exact.md
index 6263374..c83544d 100644
--- a/_pages/tag-def/DATE-exact.md
+++ b/_pages/tag-def/DATE-exact.md
@@ -35,6 +35,8 @@ superstructures:
   "https://gedcom.io/terms/v7/CREA": "{1:1}"
   "https://gedcom.io/terms/v7/HEAD-SOUR-DATA": "{0:1}"
   "https://gedcom.io/terms/v7/ord-STAT": "{1:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DATE.md b/_pages/tag-def/DATE.md
index 4858610..55dfe86 100644
--- a/_pages/tag-def/DATE.md
+++ b/_pages/tag-def/DATE.md
@@ -24,6 +24,19 @@ specification:
     The principal date of the subject of the superstructure. The payload is a
     `DateValue`.
     
+    When the superstructure is an event, the principal date indicates when the
+    event took place.
+    
+    When the superstructure is an attribute, the principal date indicates when the
+    attribute was observed, asserted, or applied. A date period might put bounds on
+    the attributes applicability, but other date forms assume that the attribute
+    may have also applied on other dates too.
+    
+    When the superstructure is a `https://gedcom.io/terms/v7/SOUR-DATA`, the
+    principal date indicates when the data was entered into the source; or, for a
+    source like a website that changes over time, a date on which the source
+    contained the data.
+    
     See `DATE_VALUE` for more details.
   - |
     A date, optionally with a time and/or a phrase. If there is a `TIME`, it
@@ -104,6 +117,8 @@ superstructures:
   "https://gedcom.io/terms/v7/SOUR-DATA": "{0:1}"
   "https://gedcom.io/terms/v7/SSN": "{0:1}"
   "https://gedcom.io/terms/v7/WILL": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DEAT.md b/_pages/tag-def/DEAT.md
index f8e990b..69e529d 100644
--- a/_pages/tag-def/DEAT.md
+++ b/_pages/tag-def/DEAT.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DESI.md b/_pages/tag-def/DESI.md
index e52a9e0..da98cf4 100644
--- a/_pages/tag-def/DESI.md
+++ b/_pages/tag-def/DESI.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DEST.md b/_pages/tag-def/DEST.md
index 145ebd9..eab8cfe 100644
--- a/_pages/tag-def/DEST.md
+++ b/_pages/tag-def/DEST.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DIV.md b/_pages/tag-def/DIV.md
index ed6a4dc..4cc9371 100644
--- a/_pages/tag-def/DIV.md
+++ b/_pages/tag-def/DIV.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DIVF.md b/_pages/tag-def/DIVF.md
index 7deaf1a..5ac297c 100644
--- a/_pages/tag-def/DIVF.md
+++ b/_pages/tag-def/DIVF.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/DSCR.md b/_pages/tag-def/DSCR.md
index 6f2c157..caa9c28 100644
--- a/_pages/tag-def/DSCR.md
+++ b/_pages/tag-def/DSCR.md
@@ -55,6 +55,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/EDUC.md b/_pages/tag-def/EDUC.md
index 9e9968e..b6be04e 100644
--- a/_pages/tag-def/EDUC.md
+++ b/_pages/tag-def/EDUC.md
@@ -55,6 +55,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/EMAIL.md b/_pages/tag-def/EMAIL.md
index 6b3bd34..4f53784 100644
--- a/_pages/tag-def/EMAIL.md
+++ b/_pages/tag-def/EMAIL.md
@@ -96,6 +96,8 @@ superstructures:
   "https://gedcom.io/terms/v7/WILL": "{0:M}"
   "https://gedcom.io/terms/v7/record-REPO": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/EMIG.md b/_pages/tag-def/EMIG.md
index dfe306e..d230d1c 100644
--- a/_pages/tag-def/EMIG.md
+++ b/_pages/tag-def/EMIG.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ENDL.md b/_pages/tag-def/ENDL.md
index cb20f35..773bbf4 100644
--- a/_pages/tag-def/ENDL.md
+++ b/_pages/tag-def/ENDL.md
@@ -41,6 +41,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ENGA.md b/_pages/tag-def/ENGA.md
index c001508..d9dacc9 100644
--- a/_pages/tag-def/ENGA.md
+++ b/_pages/tag-def/ENGA.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/EXID-TYPE.md b/_pages/tag-def/EXID-TYPE.md
index fe88a73..843df12 100644
--- a/_pages/tag-def/EXID-TYPE.md
+++ b/_pages/tag-def/EXID-TYPE.md
@@ -55,6 +55,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/EXID": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/EXID.md b/_pages/tag-def/EXID.md
index 15c8672..dd5c55d 100644
--- a/_pages/tag-def/EXID.md
+++ b/_pages/tag-def/EXID.md
@@ -51,6 +51,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}"
   "https://gedcom.io/terms/v7/record-SOUR": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAM-CENS.md b/_pages/tag-def/FAM-CENS.md
index 5742483..cdb95c9 100644
--- a/_pages/tag-def/FAM-CENS.md
+++ b/_pages/tag-def/FAM-CENS.md
@@ -54,6 +54,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAM-EVEN.md b/_pages/tag-def/FAM-EVEN.md
index fc2631d..ce137a3 100644
--- a/_pages/tag-def/FAM-EVEN.md
+++ b/_pages/tag-def/FAM-EVEN.md
@@ -51,6 +51,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAM-FACT.md b/_pages/tag-def/FAM-FACT.md
index 1b7899a..8a4db39 100644
--- a/_pages/tag-def/FAM-FACT.md
+++ b/_pages/tag-def/FAM-FACT.md
@@ -51,6 +51,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAM-HUSB.md b/_pages/tag-def/FAM-HUSB.md
index 939766d..2c9b6d6 100644
--- a/_pages/tag-def/FAM-HUSB.md
+++ b/_pages/tag-def/FAM-HUSB.md
@@ -31,6 +31,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAM-NCHI.md b/_pages/tag-def/FAM-NCHI.md
index 2b3b916..be67576 100644
--- a/_pages/tag-def/FAM-NCHI.md
+++ b/_pages/tag-def/FAM-NCHI.md
@@ -53,6 +53,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAM-RESI.md b/_pages/tag-def/FAM-RESI.md
index 26caa87..8ed988b 100644
--- a/_pages/tag-def/FAM-RESI.md
+++ b/_pages/tag-def/FAM-RESI.md
@@ -57,6 +57,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAM-WIFE.md b/_pages/tag-def/FAM-WIFE.md
index e704a92..05507c6 100644
--- a/_pages/tag-def/FAM-WIFE.md
+++ b/_pages/tag-def/FAM-WIFE.md
@@ -31,6 +31,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAMC-ADOP.md b/_pages/tag-def/FAMC-ADOP.md
index a04bdc4..7e21a26 100644
--- a/_pages/tag-def/FAMC-ADOP.md
+++ b/_pages/tag-def/FAMC-ADOP.md
@@ -34,6 +34,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/ADOP-FAMC": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAMC-STAT.md b/_pages/tag-def/FAMC-STAT.md
index def4311..5e3b5fa 100644
--- a/_pages/tag-def/FAMC-STAT.md
+++ b/_pages/tag-def/FAMC-STAT.md
@@ -35,6 +35,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/INDI-FAMC": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAMC.md b/_pages/tag-def/FAMC.md
index 8ae0271..ae64f46 100644
--- a/_pages/tag-def/FAMC.md
+++ b/_pages/tag-def/FAMC.md
@@ -32,6 +32,8 @@ superstructures:
   "https://gedcom.io/terms/v7/BIRT": "{0:1}"
   "https://gedcom.io/terms/v7/CHR": "{0:1}"
   "https://gedcom.io/terms/v7/SLGC": "{1:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAMS.md b/_pages/tag-def/FAMS.md
index cd8c71b..4d43d83 100644
--- a/_pages/tag-def/FAMS.md
+++ b/_pages/tag-def/FAMS.md
@@ -33,6 +33,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FAX.md b/_pages/tag-def/FAX.md
index cf67acf..9c7ac3f 100644
--- a/_pages/tag-def/FAX.md
+++ b/_pages/tag-def/FAX.md
@@ -84,6 +84,8 @@ superstructures:
   "https://gedcom.io/terms/v7/WILL": "{0:M}"
   "https://gedcom.io/terms/v7/record-REPO": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FCOM.md b/_pages/tag-def/FCOM.md
index aa2492d..2b95e57 100644
--- a/_pages/tag-def/FCOM.md
+++ b/_pages/tag-def/FCOM.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FILE-TRAN.md b/_pages/tag-def/FILE-TRAN.md
index ce4a9a4..1e0e493 100644
--- a/_pages/tag-def/FILE-TRAN.md
+++ b/_pages/tag-def/FILE-TRAN.md
@@ -75,6 +75,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/FILE": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FILE.md b/_pages/tag-def/FILE.md
index 1c0731d..db3b273 100644
--- a/_pages/tag-def/FILE.md
+++ b/_pages/tag-def/FILE.md
@@ -34,6 +34,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-OBJE": "{1:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/FORM.md b/_pages/tag-def/FORM.md
index ed84511..a343311 100644
--- a/_pages/tag-def/FORM.md
+++ b/_pages/tag-def/FORM.md
@@ -32,6 +32,8 @@ substructures:
 superstructures:
   "https://gedcom.io/terms/v7/FILE": "{1:1}"
   "https://gedcom.io/terms/v7/FILE-TRAN": "{1:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/GEDC-VERS.md b/_pages/tag-def/GEDC-VERS.md
index 33a33c0..eaa414b 100644
--- a/_pages/tag-def/GEDC-VERS.md
+++ b/_pages/tag-def/GEDC-VERS.md
@@ -34,6 +34,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/GEDC": "{1:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/GEDC.md b/_pages/tag-def/GEDC.md
index 8b4ac8c..b8e8969 100644
--- a/_pages/tag-def/GEDC.md
+++ b/_pages/tag-def/GEDC.md
@@ -35,6 +35,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD": "{1:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/GIVN.md b/_pages/tag-def/GIVN.md
index e14d839..f351ba4 100644
--- a/_pages/tag-def/GIVN.md
+++ b/_pages/tag-def/GIVN.md
@@ -31,6 +31,8 @@ substructures: {}
 superstructures:
   "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}"
   "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/GRAD.md b/_pages/tag-def/GRAD.md
index 5d9c10b..7f756a6 100644
--- a/_pages/tag-def/GRAD.md
+++ b/_pages/tag-def/GRAD.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/HEAD-DATE.md b/_pages/tag-def/HEAD-DATE.md
index 8e4799a..605039e 100644
--- a/_pages/tag-def/HEAD-DATE.md
+++ b/_pages/tag-def/HEAD-DATE.md
@@ -31,6 +31,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/HEAD-LANG.md b/_pages/tag-def/HEAD-LANG.md
index 85cca8f..a900725 100644
--- a/_pages/tag-def/HEAD-LANG.md
+++ b/_pages/tag-def/HEAD-LANG.md
@@ -54,6 +54,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/HEAD-PLAC-FORM.md b/_pages/tag-def/HEAD-PLAC-FORM.md
index 7bb7789..04f4259 100644
--- a/_pages/tag-def/HEAD-PLAC-FORM.md
+++ b/_pages/tag-def/HEAD-PLAC-FORM.md
@@ -30,6 +30,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD-PLAC": "{1:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/HEAD-PLAC.md b/_pages/tag-def/HEAD-PLAC.md
index 7e29ed4..94b21ee 100644
--- a/_pages/tag-def/HEAD-PLAC.md
+++ b/_pages/tag-def/HEAD-PLAC.md
@@ -32,6 +32,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/HEAD-SOUR-DATA.md b/_pages/tag-def/HEAD-SOUR-DATA.md
index e70512f..cf92d92 100644
--- a/_pages/tag-def/HEAD-SOUR-DATA.md
+++ b/_pages/tag-def/HEAD-SOUR-DATA.md
@@ -34,6 +34,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD-SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/HEAD-SOUR.md b/_pages/tag-def/HEAD-SOUR.md
index 32c2311..c7c8ba8 100644
--- a/_pages/tag-def/HEAD-SOUR.md
+++ b/_pages/tag-def/HEAD-SOUR.md
@@ -37,6 +37,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/HEAD.md b/_pages/tag-def/HEAD.md
index 8a6d7d7..cd2f5a6 100644
--- a/_pages/tag-def/HEAD.md
+++ b/_pages/tag-def/HEAD.md
@@ -54,6 +54,8 @@ substructures:
   "https://gedcom.io/terms/v7/SUBM": "{0:1}"
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/HEIGHT.md b/_pages/tag-def/HEIGHT.md
index 27e1566..c572859 100644
--- a/_pages/tag-def/HEIGHT.md
+++ b/_pages/tag-def/HEIGHT.md
@@ -48,6 +48,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/CROP": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/HUSB.md b/_pages/tag-def/HUSB.md
index 88e9014..f5fb5f3 100644
--- a/_pages/tag-def/HUSB.md
+++ b/_pages/tag-def/HUSB.md
@@ -46,6 +46,8 @@ superstructures:
   "https://gedcom.io/terms/v7/MARL": "{0:1}"
   "https://gedcom.io/terms/v7/MARR": "{0:1}"
   "https://gedcom.io/terms/v7/MARS": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/IDNO.md b/_pages/tag-def/IDNO.md
index d055e94..a237b6d 100644
--- a/_pages/tag-def/IDNO.md
+++ b/_pages/tag-def/IDNO.md
@@ -57,6 +57,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/IMMI.md b/_pages/tag-def/IMMI.md
index 799624b..8e6894e 100644
--- a/_pages/tag-def/IMMI.md
+++ b/_pages/tag-def/IMMI.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INDI-CENS.md b/_pages/tag-def/INDI-CENS.md
index 5b5cd9f..bb8ae6e 100644
--- a/_pages/tag-def/INDI-CENS.md
+++ b/_pages/tag-def/INDI-CENS.md
@@ -53,6 +53,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INDI-EVEN.md b/_pages/tag-def/INDI-EVEN.md
index 54d6a46..2b5f3e2 100644
--- a/_pages/tag-def/INDI-EVEN.md
+++ b/_pages/tag-def/INDI-EVEN.md
@@ -71,6 +71,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INDI-FACT.md b/_pages/tag-def/INDI-FACT.md
index a347e3e..0f3a2e7 100644
--- a/_pages/tag-def/INDI-FACT.md
+++ b/_pages/tag-def/INDI-FACT.md
@@ -68,6 +68,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INDI-FAMC.md b/_pages/tag-def/INDI-FAMC.md
index dd258ef..a65deb0 100644
--- a/_pages/tag-def/INDI-FAMC.md
+++ b/_pages/tag-def/INDI-FAMC.md
@@ -36,6 +36,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INDI-NAME.md b/_pages/tag-def/INDI-NAME.md
index f4a40de..1cb4132 100644
--- a/_pages/tag-def/INDI-NAME.md
+++ b/_pages/tag-def/INDI-NAME.md
@@ -71,6 +71,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INDI-NCHI.md b/_pages/tag-def/INDI-NCHI.md
index 460ea60..2393ac5 100644
--- a/_pages/tag-def/INDI-NCHI.md
+++ b/_pages/tag-def/INDI-NCHI.md
@@ -53,6 +53,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INDI-RELI.md b/_pages/tag-def/INDI-RELI.md
index a282fa6..21c3d04 100644
--- a/_pages/tag-def/INDI-RELI.md
+++ b/_pages/tag-def/INDI-RELI.md
@@ -50,6 +50,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INDI-RESI.md b/_pages/tag-def/INDI-RESI.md
index c492c62..692b261 100644
--- a/_pages/tag-def/INDI-RESI.md
+++ b/_pages/tag-def/INDI-RESI.md
@@ -76,6 +76,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INDI-TITL.md b/_pages/tag-def/INDI-TITL.md
index db6ce23..86d9858 100644
--- a/_pages/tag-def/INDI-TITL.md
+++ b/_pages/tag-def/INDI-TITL.md
@@ -50,6 +50,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/INIL.md b/_pages/tag-def/INIL.md
index e71a89c..7303b2f 100644
--- a/_pages/tag-def/INIL.md
+++ b/_pages/tag-def/INIL.md
@@ -44,6 +44,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/LANG.md b/_pages/tag-def/LANG.md
index 8b53dc8..2c322be 100644
--- a/_pages/tag-def/LANG.md
+++ b/_pages/tag-def/LANG.md
@@ -89,6 +89,8 @@ superstructures:
   "https://gedcom.io/terms/v7/PLAC-TRAN": "{1:1}"
   "https://gedcom.io/terms/v7/TEXT": "{0:1}"
   "https://gedcom.io/terms/v7/record-SNOTE": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/LATI.md b/_pages/tag-def/LATI.md
index 55c048e..fb1f5ab 100644
--- a/_pages/tag-def/LATI.md
+++ b/_pages/tag-def/LATI.md
@@ -41,6 +41,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/MAP": "{1:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/LEFT.md b/_pages/tag-def/LEFT.md
index 56f2e61..8675ce3 100644
--- a/_pages/tag-def/LEFT.md
+++ b/_pages/tag-def/LEFT.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/CROP": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/LONG.md b/_pages/tag-def/LONG.md
index 86f3d3f..09a5dcf 100644
--- a/_pages/tag-def/LONG.md
+++ b/_pages/tag-def/LONG.md
@@ -41,6 +41,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/MAP": "{1:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/MAP.md b/_pages/tag-def/MAP.md
index 633428e..be96dc8 100644
--- a/_pages/tag-def/MAP.md
+++ b/_pages/tag-def/MAP.md
@@ -39,6 +39,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/PLAC": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/MARB.md b/_pages/tag-def/MARB.md
index ca342a8..126f70e 100644
--- a/_pages/tag-def/MARB.md
+++ b/_pages/tag-def/MARB.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/MARC.md b/_pages/tag-def/MARC.md
index 29858f6..989e871 100644
--- a/_pages/tag-def/MARC.md
+++ b/_pages/tag-def/MARC.md
@@ -59,6 +59,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/MARL.md b/_pages/tag-def/MARL.md
index d07f44d..01500d7 100644
--- a/_pages/tag-def/MARL.md
+++ b/_pages/tag-def/MARL.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/MARR.md b/_pages/tag-def/MARR.md
index d872bfe..43eb3af 100644
--- a/_pages/tag-def/MARR.md
+++ b/_pages/tag-def/MARR.md
@@ -58,6 +58,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/MARS.md b/_pages/tag-def/MARS.md
index ac2c826..ee5e912 100644
--- a/_pages/tag-def/MARS.md
+++ b/_pages/tag-def/MARS.md
@@ -59,6 +59,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/MEDI.md b/_pages/tag-def/MEDI.md
index 299d7e7..c97b565 100644
--- a/_pages/tag-def/MEDI.md
+++ b/_pages/tag-def/MEDI.md
@@ -36,6 +36,16 @@ specification:
     rather than `BOOK` or `NEWSPAPER`.
     
     </div>
+    
+    When `MEDI` is a substructure of a `https://gedcom.io/terms/v7/FORM`, it is
+    recommended that its payload describes the medium from which it was derived.
+    
+    <div class="example">
+    
+    Consider a digital photo in a multimedia record; for this asset, the
+    `FORM`.`MEDI` is recommended to be `PHOTO` rather than `ELECTRONIC`.
+    
+    </div>
 
 label: 'Medium'
 
@@ -49,6 +59,8 @@ substructures:
 superstructures:
   "https://gedcom.io/terms/v7/CALN": "{0:1}"
   "https://gedcom.io/terms/v7/FORM": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/MIME.md b/_pages/tag-def/MIME.md
index 91fd4b0..92f64c4 100644
--- a/_pages/tag-def/MIME.md
+++ b/_pages/tag-def/MIME.md
@@ -89,6 +89,8 @@ superstructures:
   "https://gedcom.io/terms/v7/NOTE-TRAN": "{0:1}"
   "https://gedcom.io/terms/v7/TEXT": "{0:1}"
   "https://gedcom.io/terms/v7/record-SNOTE": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NAME-TRAN.md b/_pages/tag-def/NAME-TRAN.md
index 5a68894..929968f 100644
--- a/_pages/tag-def/NAME-TRAN.md
+++ b/_pages/tag-def/NAME-TRAN.md
@@ -73,6 +73,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NAME-TYPE.md b/_pages/tag-def/NAME-TYPE.md
index 283f204..39b5f9a 100644
--- a/_pages/tag-def/NAME-TYPE.md
+++ b/_pages/tag-def/NAME-TYPE.md
@@ -34,6 +34,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/INDI-NAME": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NAME.md b/_pages/tag-def/NAME.md
index 5c2c993..f45ec03 100644
--- a/_pages/tag-def/NAME.md
+++ b/_pages/tag-def/NAME.md
@@ -32,6 +32,8 @@ superstructures:
   "https://gedcom.io/terms/v7/HEAD-SOUR": "{0:1}"
   "https://gedcom.io/terms/v7/record-REPO": "{1:1}"
   "https://gedcom.io/terms/v7/record-SUBM": "{1:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NATI.md b/_pages/tag-def/NATI.md
index 8a757ff..e316e4c 100644
--- a/_pages/tag-def/NATI.md
+++ b/_pages/tag-def/NATI.md
@@ -56,6 +56,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NATU.md b/_pages/tag-def/NATU.md
index 38b708f..9228e3d 100644
--- a/_pages/tag-def/NATU.md
+++ b/_pages/tag-def/NATU.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NICK.md b/_pages/tag-def/NICK.md
index 3f31c69..b9f6971 100644
--- a/_pages/tag-def/NICK.md
+++ b/_pages/tag-def/NICK.md
@@ -20,8 +20,22 @@ standard tag: NICK
 
 specification:
   - Nickname
-  - A descriptive or familiar name that is used instead of, or in addition to,
-    one’s proper name.
+  - |
+    A descriptive or familiar name that is used instead of, or in addition to,
+    one’s official or legal name.
+    
+    <div class="note">
+    
+    The label "nickname" and description text of this structure were introduced
+    with version 5.5 in 1996, but are understood differently by different users.
+    Some use `NICK` only for names that would be inappropriate in formal settings.
+    Some use it for pseudonyms regardless of where they are used. Some use it for
+    any variant of a name that is not the one used on legal documents. Because all
+    of these uses, and likely others as well, are common in existing data, no
+    further clarification of the meaning of the `NICK` structure is possible
+    without contradicting some existing data.
+    
+    </div>
 
 label: 'Nickname'
 
@@ -32,6 +46,8 @@ substructures: {}
 superstructures:
   "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}"
   "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NMR.md b/_pages/tag-def/NMR.md
index d21da8a..2c3ad14 100644
--- a/_pages/tag-def/NMR.md
+++ b/_pages/tag-def/NMR.md
@@ -56,6 +56,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NO-DATE.md b/_pages/tag-def/NO-DATE.md
index ca2ae5e..4a8658f 100644
--- a/_pages/tag-def/NO-DATE.md
+++ b/_pages/tag-def/NO-DATE.md
@@ -32,6 +32,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/NO": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NO.md b/_pages/tag-def/NO.md
index 1975655..c790097 100644
--- a/_pages/tag-def/NO.md
+++ b/_pages/tag-def/NO.md
@@ -67,6 +67,8 @@ substructures:
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NOTE-TRAN.md b/_pages/tag-def/NOTE-TRAN.md
index ec86a10..03cf4a5 100644
--- a/_pages/tag-def/NOTE-TRAN.md
+++ b/_pages/tag-def/NOTE-TRAN.md
@@ -79,6 +79,8 @@ substructures:
 superstructures:
   "https://gedcom.io/terms/v7/NOTE": "{0:M}"
   "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NOTE.md b/_pages/tag-def/NOTE.md
index b118689..d56b403 100644
--- a/_pages/tag-def/NOTE.md
+++ b/_pages/tag-def/NOTE.md
@@ -113,6 +113,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-REPO": "{0:M}"
   "https://gedcom.io/terms/v7/record-SOUR": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NPFX.md b/_pages/tag-def/NPFX.md
index f5442be..c65b71f 100644
--- a/_pages/tag-def/NPFX.md
+++ b/_pages/tag-def/NPFX.md
@@ -31,6 +31,8 @@ substructures: {}
 superstructures:
   "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}"
   "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/NSFX.md b/_pages/tag-def/NSFX.md
index e236484..77b6a91 100644
--- a/_pages/tag-def/NSFX.md
+++ b/_pages/tag-def/NSFX.md
@@ -32,6 +32,8 @@ substructures: {}
 superstructures:
   "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}"
   "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/OBJE.md b/_pages/tag-def/OBJE.md
index 4ed3f55..072f7b9 100644
--- a/_pages/tag-def/OBJE.md
+++ b/_pages/tag-def/OBJE.md
@@ -95,6 +95,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
   "https://gedcom.io/terms/v7/record-SOUR": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/OCCU.md b/_pages/tag-def/OCCU.md
index ede5e92..6e4082e 100644
--- a/_pages/tag-def/OCCU.md
+++ b/_pages/tag-def/OCCU.md
@@ -55,6 +55,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ORDN.md b/_pages/tag-def/ORDN.md
index acd0f11..0e815ad 100644
--- a/_pages/tag-def/ORDN.md
+++ b/_pages/tag-def/ORDN.md
@@ -56,6 +56,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PAGE.md b/_pages/tag-def/PAGE.md
index f231b05..6d1db82 100644
--- a/_pages/tag-def/PAGE.md
+++ b/_pages/tag-def/PAGE.md
@@ -62,6 +62,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PEDI.md b/_pages/tag-def/PEDI.md
index d9db4cb..60caed7 100644
--- a/_pages/tag-def/PEDI.md
+++ b/_pages/tag-def/PEDI.md
@@ -35,6 +35,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/INDI-FAMC": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PHON.md b/_pages/tag-def/PHON.md
index dff42c2..9313e05 100644
--- a/_pages/tag-def/PHON.md
+++ b/_pages/tag-def/PHON.md
@@ -92,6 +92,8 @@ superstructures:
   "https://gedcom.io/terms/v7/WILL": "{0:M}"
   "https://gedcom.io/terms/v7/record-REPO": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PHRASE.md b/_pages/tag-def/PHRASE.md
index 489d95c..fcb39f0 100644
--- a/_pages/tag-def/PHRASE.md
+++ b/_pages/tag-def/PHRASE.md
@@ -121,6 +121,8 @@ superstructures:
   "https://gedcom.io/terms/v7/ROLE": "{0:1}"
   "https://gedcom.io/terms/v7/SDATE": "{0:1}"
   "https://gedcom.io/terms/v7/SOUR-EVEN": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PLAC-FORM.md b/_pages/tag-def/PLAC-FORM.md
index 7cf76da..080fcdd 100644
--- a/_pages/tag-def/PLAC-FORM.md
+++ b/_pages/tag-def/PLAC-FORM.md
@@ -44,6 +44,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/PLAC": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PLAC-TRAN.md b/_pages/tag-def/PLAC-TRAN.md
index b51dc1e..1df507d 100644
--- a/_pages/tag-def/PLAC-TRAN.md
+++ b/_pages/tag-def/PLAC-TRAN.md
@@ -68,6 +68,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/PLAC": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PLAC.md b/_pages/tag-def/PLAC.md
index e033701..9d06732 100644
--- a/_pages/tag-def/PLAC.md
+++ b/_pages/tag-def/PLAC.md
@@ -23,9 +23,11 @@ specification:
   - |
     The principal place in which the superstructure's subject occurred, represented
     as a [List] of jurisdictional entities in a sequence from the lowest to the
-    highest jurisdiction. As with other lists, the jurisdictions are separated by
-    commas. Any jurisdiction's name that is missing is still accounted for by an
-    empty string in the list.
+    highest jurisdiction, where "jurisdiction" includes units in a political,
+    ecclesiastical, and geographical hierarchies and may include units of any size,
+    such as a continent, "at sea", or a specific building, farm, or cemetery. As
+    with other lists, the jurisdictions are separated by commas. Any jurisdiction's
+    name that is missing is still accounted for by an empty string in the list.
     
     The type of each jurisdiction is given in the `PLAC`.`FORM` substructure, if
     present, or in the `HEAD`.`PLAC`.`FORM` structure. If neither is present, the
@@ -45,8 +47,12 @@ specification:
     - The payload contains a comma-separated list of region names, ordered from
       smallest to largest. The specific meaning of each element is given by the
       `FORM` substructure, or in the `HEAD`.`PLAC`.`FORM` if there is no `FORM`
-      substructure. Elements should be left blank if they are unknown, do not apply
-      to the location, or are too specific for the region in question.
+      substructure. If neither `FORM` exists, the meaning of the elements are not
+      defined in this specification beyond being names of jurisdictions of some
+      kind, ordered from smallest to largest.
+    
+      Elements should be left blank if they are unknown, do not apply to the
+      location, or are too specific for the region in question.
     
       <div class="example">
         A record describing births throughout Oneida county could be recorded as
@@ -147,6 +153,8 @@ superstructures:
   "https://gedcom.io/terms/v7/SLGS": "{0:1}"
   "https://gedcom.io/terms/v7/SSN": "{0:1}"
   "https://gedcom.io/terms/v7/WILL": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/POST.md b/_pages/tag-def/POST.md
index a40234b..0502a47 100644
--- a/_pages/tag-def/POST.md
+++ b/_pages/tag-def/POST.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/ADDR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PROB.md b/_pages/tag-def/PROB.md
index 98030fa..695a39a 100644
--- a/_pages/tag-def/PROB.md
+++ b/_pages/tag-def/PROB.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PROP.md b/_pages/tag-def/PROP.md
index 084c285..88b7a59 100644
--- a/_pages/tag-def/PROP.md
+++ b/_pages/tag-def/PROP.md
@@ -55,6 +55,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/PUBL.md b/_pages/tag-def/PUBL.md
index 3015738..a4730b1 100644
--- a/_pages/tag-def/PUBL.md
+++ b/_pages/tag-def/PUBL.md
@@ -38,6 +38,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/record-SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/QUAY.md b/_pages/tag-def/QUAY.md
index b4d2b20..df8dffd 100644
--- a/_pages/tag-def/QUAY.md
+++ b/_pages/tag-def/QUAY.md
@@ -36,6 +36,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/REFN.md b/_pages/tag-def/REFN.md
index 4783a54..a46f8d8 100644
--- a/_pages/tag-def/REFN.md
+++ b/_pages/tag-def/REFN.md
@@ -45,6 +45,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}"
   "https://gedcom.io/terms/v7/record-SOUR": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/RELI.md b/_pages/tag-def/RELI.md
index ed38fe5..e7c0c39 100644
--- a/_pages/tag-def/RELI.md
+++ b/_pages/tag-def/RELI.md
@@ -87,6 +87,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/REPO.md b/_pages/tag-def/REPO.md
index 5fc414b..7e0965c 100644
--- a/_pages/tag-def/REPO.md
+++ b/_pages/tag-def/REPO.md
@@ -39,6 +39,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-SOUR": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/RESN.md b/_pages/tag-def/RESN.md
index 7a7d7ee..c8b3de4 100644
--- a/_pages/tag-def/RESN.md
+++ b/_pages/tag-def/RESN.md
@@ -97,6 +97,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:1}"
   "https://gedcom.io/terms/v7/record-INDI": "{0:1}"
   "https://gedcom.io/terms/v7/record-OBJE": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/RETI.md b/_pages/tag-def/RETI.md
index 0331087..1af5f0d 100644
--- a/_pages/tag-def/RETI.md
+++ b/_pages/tag-def/RETI.md
@@ -57,6 +57,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ROLE.md b/_pages/tag-def/ROLE.md
index c559754..fe1b7b9 100644
--- a/_pages/tag-def/ROLE.md
+++ b/_pages/tag-def/ROLE.md
@@ -68,6 +68,8 @@ substructures:
 superstructures:
   "https://gedcom.io/terms/v7/ASSO": "{1:1}"
   "https://gedcom.io/terms/v7/SOUR-EVEN": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SCHMA.md b/_pages/tag-def/SCHMA.md
index 455624d..5e2a965 100644
--- a/_pages/tag-def/SCHMA.md
+++ b/_pages/tag-def/SCHMA.md
@@ -32,6 +32,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SDATE.md b/_pages/tag-def/SDATE.md
index c4a2f3b..fcab2c2 100644
--- a/_pages/tag-def/SDATE.md
+++ b/_pages/tag-def/SDATE.md
@@ -98,6 +98,8 @@ superstructures:
   "https://gedcom.io/terms/v7/RETI": "{0:1}"
   "https://gedcom.io/terms/v7/SSN": "{0:1}"
   "https://gedcom.io/terms/v7/WILL": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SEX.md b/_pages/tag-def/SEX.md
index 5d559b9..a3c0197 100644
--- a/_pages/tag-def/SEX.md
+++ b/_pages/tag-def/SEX.md
@@ -33,6 +33,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SLGC.md b/_pages/tag-def/SLGC.md
index 2d37730..aa0ce16 100644
--- a/_pages/tag-def/SLGC.md
+++ b/_pages/tag-def/SLGC.md
@@ -41,6 +41,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SLGS.md b/_pages/tag-def/SLGS.md
index 5f638eb..129a40f 100644
--- a/_pages/tag-def/SLGS.md
+++ b/_pages/tag-def/SLGS.md
@@ -44,6 +44,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SNOTE.md b/_pages/tag-def/SNOTE.md
index c521221..af70f31 100644
--- a/_pages/tag-def/SNOTE.md
+++ b/_pages/tag-def/SNOTE.md
@@ -104,6 +104,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-REPO": "{0:M}"
   "https://gedcom.io/terms/v7/record-SOUR": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SOUR-DATA.md b/_pages/tag-def/SOUR-DATA.md
index bd4d181..f06c0e0 100644
--- a/_pages/tag-def/SOUR-DATA.md
+++ b/_pages/tag-def/SOUR-DATA.md
@@ -32,6 +32,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SOUR-EVEN.md b/_pages/tag-def/SOUR-EVEN.md
index b047d82..02b6bd5 100644
--- a/_pages/tag-def/SOUR-EVEN.md
+++ b/_pages/tag-def/SOUR-EVEN.md
@@ -38,6 +38,8 @@ substructures:
 
 superstructures:
   "https://gedcom.io/terms/v7/SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SOUR.md b/_pages/tag-def/SOUR.md
index c9c439f..eb3d1f8 100644
--- a/_pages/tag-def/SOUR.md
+++ b/_pages/tag-def/SOUR.md
@@ -123,6 +123,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
   "https://gedcom.io/terms/v7/record-OBJE": "{0:M}"
   "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SPFX.md b/_pages/tag-def/SPFX.md
index 7687f12..416fe5e 100644
--- a/_pages/tag-def/SPFX.md
+++ b/_pages/tag-def/SPFX.md
@@ -31,6 +31,8 @@ substructures: {}
 superstructures:
   "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}"
   "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SSN.md b/_pages/tag-def/SSN.md
index 94024a5..cb4bd2e 100644
--- a/_pages/tag-def/SSN.md
+++ b/_pages/tag-def/SSN.md
@@ -56,6 +56,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/STAE.md b/_pages/tag-def/STAE.md
index 22b2166..c0648a0 100644
--- a/_pages/tag-def/STAE.md
+++ b/_pages/tag-def/STAE.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/ADDR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SUBM-LANG.md b/_pages/tag-def/SUBM-LANG.md
index 64c619e..fdd2fa1 100644
--- a/_pages/tag-def/SUBM-LANG.md
+++ b/_pages/tag-def/SUBM-LANG.md
@@ -34,6 +34,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SUBM.md b/_pages/tag-def/SUBM.md
index e140abd..a76da75 100644
--- a/_pages/tag-def/SUBM.md
+++ b/_pages/tag-def/SUBM.md
@@ -33,6 +33,8 @@ superstructures:
   "https://gedcom.io/terms/v7/HEAD": "{0:1}"
   "https://gedcom.io/terms/v7/record-FAM": "{0:M}"
   "https://gedcom.io/terms/v7/record-INDI": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/SURN.md b/_pages/tag-def/SURN.md
index d660c66..371891c 100644
--- a/_pages/tag-def/SURN.md
+++ b/_pages/tag-def/SURN.md
@@ -31,6 +31,8 @@ substructures: {}
 superstructures:
   "https://gedcom.io/terms/v7/INDI-NAME": "{0:M}"
   "https://gedcom.io/terms/v7/NAME-TRAN": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/TAG.md b/_pages/tag-def/TAG.md
index 9018cd8..580ef32 100644
--- a/_pages/tag-def/TAG.md
+++ b/_pages/tag-def/TAG.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/SCHMA": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/TEMP.md b/_pages/tag-def/TEMP.md
index 7cab882..63d05c4 100644
--- a/_pages/tag-def/TEMP.md
+++ b/_pages/tag-def/TEMP.md
@@ -38,6 +38,8 @@ superstructures:
   "https://gedcom.io/terms/v7/INIL": "{0:1}"
   "https://gedcom.io/terms/v7/SLGC": "{0:1}"
   "https://gedcom.io/terms/v7/SLGS": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/TEXT.md b/_pages/tag-def/TEXT.md
index 89c9f51..ab7524f 100644
--- a/_pages/tag-def/TEXT.md
+++ b/_pages/tag-def/TEXT.md
@@ -37,6 +37,8 @@ substructures:
 superstructures:
   "https://gedcom.io/terms/v7/SOUR-DATA": "{0:M}"
   "https://gedcom.io/terms/v7/record-SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/TIME.md b/_pages/tag-def/TIME.md
index 2ecdaf8..18792d5 100644
--- a/_pages/tag-def/TIME.md
+++ b/_pages/tag-def/TIME.md
@@ -33,6 +33,8 @@ superstructures:
   "https://gedcom.io/terms/v7/DATE-exact": "{0:1}"
   "https://gedcom.io/terms/v7/HEAD-DATE": "{0:1}"
   "https://gedcom.io/terms/v7/SDATE": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/TITL.md b/_pages/tag-def/TITL.md
index db91e7e..77b722d 100644
--- a/_pages/tag-def/TITL.md
+++ b/_pages/tag-def/TITL.md
@@ -64,6 +64,8 @@ superstructures:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/TOP.md b/_pages/tag-def/TOP.md
index e00a380..e21c524 100644
--- a/_pages/tag-def/TOP.md
+++ b/_pages/tag-def/TOP.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/CROP": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/TRLR.md b/_pages/tag-def/TRLR.md
index 9d30b02..c933ef7 100644
--- a/_pages/tag-def/TRLR.md
+++ b/_pages/tag-def/TRLR.md
@@ -30,6 +30,8 @@ payload: null
 substructures: {}
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/TYPE.md b/_pages/tag-def/TYPE.md
index 85201dd..6551503 100644
--- a/_pages/tag-def/TYPE.md
+++ b/_pages/tag-def/TYPE.md
@@ -118,6 +118,8 @@ superstructures:
   "https://gedcom.io/terms/v7/RETI": "{0:1}"
   "https://gedcom.io/terms/v7/SSN": "{0:1}"
   "https://gedcom.io/terms/v7/WILL": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/UID.md b/_pages/tag-def/UID.md
index ad4a331..d5ebd71 100644
--- a/_pages/tag-def/UID.md
+++ b/_pages/tag-def/UID.md
@@ -118,6 +118,8 @@ superstructures:
   "https://gedcom.io/terms/v7/record-SNOTE": "{0:M}"
   "https://gedcom.io/terms/v7/record-SOUR": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/VERS.md b/_pages/tag-def/VERS.md
index b8a1030..d653bba 100644
--- a/_pages/tag-def/VERS.md
+++ b/_pages/tag-def/VERS.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/HEAD-SOUR": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/WIDTH.md b/_pages/tag-def/WIDTH.md
index a0d3cc8..e838df0 100644
--- a/_pages/tag-def/WIDTH.md
+++ b/_pages/tag-def/WIDTH.md
@@ -31,6 +31,8 @@ substructures: {}
 
 superstructures:
   "https://gedcom.io/terms/v7/CROP": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/WIFE.md b/_pages/tag-def/WIFE.md
index c650712..827adaa 100644
--- a/_pages/tag-def/WIFE.md
+++ b/_pages/tag-def/WIFE.md
@@ -46,6 +46,8 @@ superstructures:
   "https://gedcom.io/terms/v7/MARL": "{0:1}"
   "https://gedcom.io/terms/v7/MARR": "{0:1}"
   "https://gedcom.io/terms/v7/MARS": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/WILL.md b/_pages/tag-def/WILL.md
index c82fff7..115d903 100644
--- a/_pages/tag-def/WILL.md
+++ b/_pages/tag-def/WILL.md
@@ -58,6 +58,8 @@ superstructures:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/WWW.md b/_pages/tag-def/WWW.md
index 8719ec0..106397c 100644
--- a/_pages/tag-def/WWW.md
+++ b/_pages/tag-def/WWW.md
@@ -21,8 +21,18 @@ standard tag: WWW
 specification:
   - Web address
   - |
-    A URL or other locator for a World Wide Web page, as defined by any relevant
-    standard such as [whatwg/url], [RFC 3986], [RFC 3987], and so forth.
+    A URL or other locator for a World Wide Web page of the subject of the
+    superstructure, as defined by any relevant standard such as [whatwg/url],
+    [RFC 3986], [RFC 3987], and so forth.
+    
+    Like other substructures, the `WWW` structure provides details about the
+    subject of its superstructure. For example, a `MARR`.`WWW` is a world wide web
+    page of the marriage event, not the personal website of the couple or an entry
+    in an online database serving as a source documenting the marriage. However,
+    the meaning of `WWW` was only implicit when it was introduced in version 5.5.1
+    and many files were created that use `WWW` to store a more tangentially-related
+    web address, so applications are recommended to interpret the `WWW` structure's
+    meaning cautiously.
     
     If an invalid or no longer existing web address is present upon import, it
     should be preserved as-is on export.
@@ -88,6 +98,8 @@ superstructures:
   "https://gedcom.io/terms/v7/WILL": "{0:M}"
   "https://gedcom.io/terms/v7/record-REPO": "{0:M}"
   "https://gedcom.io/terms/v7/record-SUBM": "{0:M}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/cal-FRENCH_R.md b/_pages/tag-def/cal-FRENCH_R.md
index 8a29e8f..65a170b 100644
--- a/_pages/tag-def/cal-FRENCH_R.md
+++ b/_pages/tag-def/cal-FRENCH_R.md
@@ -65,6 +65,8 @@ months:
   - "https://gedcom.io/terms/v7/month-COMP"
 
 epochs: []
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/cal-GREGORIAN.md b/_pages/tag-def/cal-GREGORIAN.md
index b9544a8..1e94f32 100644
--- a/_pages/tag-def/cal-GREGORIAN.md
+++ b/_pages/tag-def/cal-GREGORIAN.md
@@ -65,6 +65,8 @@ months:
 
 epochs:
   - BCE
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/cal-HEBREW.md b/_pages/tag-def/cal-HEBREW.md
index 721d3c6..1f2c834 100644
--- a/_pages/tag-def/cal-HEBREW.md
+++ b/_pages/tag-def/cal-HEBREW.md
@@ -26,20 +26,20 @@ specification:
     (1 Tishrei 1) primarily overlapped with Gregorian 7 September 3761 BCE and
     Julian 7 October 3761 BCE (starting at sunset on the 6th day of those months).
     
-    | Code  | Name                                                                    |
-    | :---- | :---------------------------------------------------------------------- |
-    | `TSH` | Tishrei (תִּשְׁרֵי)                                                     |
-    | `CSH` | Marcheshvan (מַרְחֶשְׁוָן) or Cheshvan (חֶשְׁוָן)                       |
-    | `KSL` | Kislev (כִּסְלֵו)                                                       |
+    | Code  | Name                                                                  |
+    | :---- | :-------------------------------------------------------------------- |
+    | `TSH` | Tishrei (תִּשְׁרֵי)                                                        |
+    | `CSH` | Marcheshvan (מַרְחֶשְׁוָן) or Cheshvan (חֶשְׁוָן)                               |
+    | `KSL` | Kislev (כִּסְלֵו)                                                         |
     | `TVT` | Tevet (טֵבֵת)                                                           |
-    | `SHV` | Shevat (שְׁבָט)                                                         |
-    | `ADR` | Adar I, Adar Rishon, First Adar, or Adar Aleph (אדר א׳)                 |
+    | `SHV` | Shevat (שְׁבָט)                                                          |
+    | `ADR` | Adar I, Adar Rishon, First Adar, or Adar Aleph (אדר א׳)               |
     | `ADS` | Adar (אֲדָר); or Adar II, Adar Sheni, Second Adar, or Adar Bet (אדר ב׳) |
     | `NSN` | Nisan (נִיסָן)                                                          |
     | `IYR` | Iyar (אִייָר)                                                           |
     | `SVN` | Sivan (סִיוָן)                                                          |
-    | `TMZ` | Tammuz (תַּמּוּז)                                                       |
-    | `AAV` | Av (אָב)                                                                |
+    | `TMZ` | Tammuz (תַּמּוּז)                                                         |
+    | `AAV` | Av (אָב)                                                               |
     | `ELL` | Elul (אֱלוּל)                                                           |
     
     To keep the lunar-based months synchronized with the solar-based years, some
@@ -72,6 +72,8 @@ months:
   - "https://gedcom.io/terms/v7/month-ELL"
 
 epochs: []
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/cal-JULIAN.md b/_pages/tag-def/cal-JULIAN.md
index 2348817..64a1b74 100644
--- a/_pages/tag-def/cal-JULIAN.md
+++ b/_pages/tag-def/cal-JULIAN.md
@@ -53,6 +53,8 @@ months:
 
 epochs:
   - BCE
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-0.md b/_pages/tag-def/enum-0.md
index 64c84d5..5e39b2c 100644
--- a/_pages/tag-def/enum-0.md
+++ b/_pages/tag-def/enum-0.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-QUAY"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-1.md b/_pages/tag-def/enum-1.md
index 66bcaa7..fbb40a7 100644
--- a/_pages/tag-def/enum-1.md
+++ b/_pages/tag-def/enum-1.md
@@ -24,6 +24,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-QUAY"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-2.md b/_pages/tag-def/enum-2.md
index a61cfa9..80d8dcf 100644
--- a/_pages/tag-def/enum-2.md
+++ b/_pages/tag-def/enum-2.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-QUAY"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-3.md b/_pages/tag-def/enum-3.md
index 27b2dbe..f2c4a98 100644
--- a/_pages/tag-def/enum-3.md
+++ b/_pages/tag-def/enum-3.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-QUAY"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-ADOP-HUSB.md b/_pages/tag-def/enum-ADOP-HUSB.md
index 8e6f47c..ac49d8a 100644
--- a/_pages/tag-def/enum-ADOP-HUSB.md
+++ b/_pages/tag-def/enum-ADOP-HUSB.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ADOP"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-ADOP-WIFE.md b/_pages/tag-def/enum-ADOP-WIFE.md
index 5be3d9c..ba0b51b 100644
--- a/_pages/tag-def/enum-ADOP-WIFE.md
+++ b/_pages/tag-def/enum-ADOP-WIFE.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ADOP"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-ADOPTED.md b/_pages/tag-def/enum-ADOPTED.md
index 0480ea1..6c0f1da 100644
--- a/_pages/tag-def/enum-ADOPTED.md
+++ b/_pages/tag-def/enum-ADOPTED.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-PEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-AKA.md b/_pages/tag-def/enum-AKA.md
index d5d820d..f3ec594 100644
--- a/_pages/tag-def/enum-AKA.md
+++ b/_pages/tag-def/enum-AKA.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-NAME-TYPE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-AUDIO.md b/_pages/tag-def/enum-AUDIO.md
index f3554d9..9d33859 100644
--- a/_pages/tag-def/enum-AUDIO.md
+++ b/_pages/tag-def/enum-AUDIO.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-BIC.md b/_pages/tag-def/enum-BIC.md
index 117c4fa..63b43e0 100644
--- a/_pages/tag-def/enum-BIC.md
+++ b/_pages/tag-def/enum-BIC.md
@@ -25,6 +25,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-BIRTH.md b/_pages/tag-def/enum-BIRTH.md
index 3349a01..fc5d897 100644
--- a/_pages/tag-def/enum-BIRTH.md
+++ b/_pages/tag-def/enum-BIRTH.md
@@ -24,6 +24,8 @@ specification:
 value of:
   - "https://gedcom.io/terms/v7/enumset-NAME-TYPE"
   - "https://gedcom.io/terms/v7/enumset-PEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-BOOK.md b/_pages/tag-def/enum-BOOK.md
index 5ab905a..31f32c2 100644
--- a/_pages/tag-def/enum-BOOK.md
+++ b/_pages/tag-def/enum-BOOK.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-BOTH.md b/_pages/tag-def/enum-BOTH.md
index 1292c10..ca9da80 100644
--- a/_pages/tag-def/enum-BOTH.md
+++ b/_pages/tag-def/enum-BOTH.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ADOP"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-CANCELED.md b/_pages/tag-def/enum-CANCELED.md
index 6b710f8..bec0ce2 100644
--- a/_pages/tag-def/enum-CANCELED.md
+++ b/_pages/tag-def/enum-CANCELED.md
@@ -25,6 +25,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-CARD.md b/_pages/tag-def/enum-CARD.md
index d804a05..2405019 100644
--- a/_pages/tag-def/enum-CARD.md
+++ b/_pages/tag-def/enum-CARD.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-CENS.md b/_pages/tag-def/enum-CENS.md
index fd51c46..91b23e7 100644
--- a/_pages/tag-def/enum-CENS.md
+++ b/_pages/tag-def/enum-CENS.md
@@ -25,6 +25,8 @@ specification:
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVEN"
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-CHALLENGED.md b/_pages/tag-def/enum-CHALLENGED.md
index 8d6b29d..802d63f 100644
--- a/_pages/tag-def/enum-CHALLENGED.md
+++ b/_pages/tag-def/enum-CHALLENGED.md
@@ -24,6 +24,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-FAMC-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-CHIL.md b/_pages/tag-def/enum-CHIL.md
index 9b29fa8..d557218 100644
--- a/_pages/tag-def/enum-CHIL.md
+++ b/_pages/tag-def/enum-CHIL.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-CHILD.md b/_pages/tag-def/enum-CHILD.md
index aa3d6bc..b086dd9 100644
--- a/_pages/tag-def/enum-CHILD.md
+++ b/_pages/tag-def/enum-CHILD.md
@@ -26,6 +26,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-CLERGY.md b/_pages/tag-def/enum-CLERGY.md
index 6cb6d9c..24a3eff 100644
--- a/_pages/tag-def/enum-CLERGY.md
+++ b/_pages/tag-def/enum-CLERGY.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-COMPLETED.md b/_pages/tag-def/enum-COMPLETED.md
index 488d122..eb725ac 100644
--- a/_pages/tag-def/enum-COMPLETED.md
+++ b/_pages/tag-def/enum-COMPLETED.md
@@ -26,6 +26,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-CONFIDENTIAL.md b/_pages/tag-def/enum-CONFIDENTIAL.md
index 398939a..eed6d4b 100644
--- a/_pages/tag-def/enum-CONFIDENTIAL.md
+++ b/_pages/tag-def/enum-CONFIDENTIAL.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-RESN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-DISPROVEN.md b/_pages/tag-def/enum-DISPROVEN.md
index 5e2230c..8d2406c 100644
--- a/_pages/tag-def/enum-DISPROVEN.md
+++ b/_pages/tag-def/enum-DISPROVEN.md
@@ -24,6 +24,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-FAMC-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-DNS.md b/_pages/tag-def/enum-DNS.md
index c8178b4..a3d5220 100644
--- a/_pages/tag-def/enum-DNS.md
+++ b/_pages/tag-def/enum-DNS.md
@@ -25,6 +25,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-DNS_CAN.md b/_pages/tag-def/enum-DNS_CAN.md
index 3d7f818..f479705 100644
--- a/_pages/tag-def/enum-DNS_CAN.md
+++ b/_pages/tag-def/enum-DNS_CAN.md
@@ -25,6 +25,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-ELECTRONIC.md b/_pages/tag-def/enum-ELECTRONIC.md
index 09a5580..67de625 100644
--- a/_pages/tag-def/enum-ELECTRONIC.md
+++ b/_pages/tag-def/enum-ELECTRONIC.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-EVEN.md b/_pages/tag-def/enum-EVEN.md
index f421f5e..08682ec 100644
--- a/_pages/tag-def/enum-EVEN.md
+++ b/_pages/tag-def/enum-EVEN.md
@@ -24,6 +24,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-EXCLUDED.md b/_pages/tag-def/enum-EXCLUDED.md
index d45319b..6afbbb8 100644
--- a/_pages/tag-def/enum-EXCLUDED.md
+++ b/_pages/tag-def/enum-EXCLUDED.md
@@ -26,6 +26,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-F.md b/_pages/tag-def/enum-F.md
index 14b5cc3..b1cb36c 100644
--- a/_pages/tag-def/enum-F.md
+++ b/_pages/tag-def/enum-F.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-SEX"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-FACT.md b/_pages/tag-def/enum-FACT.md
index 12e7ad4..9a197b5 100644
--- a/_pages/tag-def/enum-FACT.md
+++ b/_pages/tag-def/enum-FACT.md
@@ -24,6 +24,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-FATH.md b/_pages/tag-def/enum-FATH.md
index f79acfc..a10c40e 100644
--- a/_pages/tag-def/enum-FATH.md
+++ b/_pages/tag-def/enum-FATH.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-FICHE.md b/_pages/tag-def/enum-FICHE.md
index 1029c28..5a1cfd1 100644
--- a/_pages/tag-def/enum-FICHE.md
+++ b/_pages/tag-def/enum-FICHE.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-FILM.md b/_pages/tag-def/enum-FILM.md
index bce15a7..c2da35e 100644
--- a/_pages/tag-def/enum-FILM.md
+++ b/_pages/tag-def/enum-FILM.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-FOSTER.md b/_pages/tag-def/enum-FOSTER.md
index dda210c..4f8c955 100644
--- a/_pages/tag-def/enum-FOSTER.md
+++ b/_pages/tag-def/enum-FOSTER.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-PEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-FRIEND.md b/_pages/tag-def/enum-FRIEND.md
index 82cb097..b66c55f 100644
--- a/_pages/tag-def/enum-FRIEND.md
+++ b/_pages/tag-def/enum-FRIEND.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-GODP.md b/_pages/tag-def/enum-GODP.md
index df29e77..55b04d7 100644
--- a/_pages/tag-def/enum-GODP.md
+++ b/_pages/tag-def/enum-GODP.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-HUSB.md b/_pages/tag-def/enum-HUSB.md
index 7dc05bb..33430f3 100644
--- a/_pages/tag-def/enum-HUSB.md
+++ b/_pages/tag-def/enum-HUSB.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-IMMIGRANT.md b/_pages/tag-def/enum-IMMIGRANT.md
index d1f54ad..574b458 100644
--- a/_pages/tag-def/enum-IMMIGRANT.md
+++ b/_pages/tag-def/enum-IMMIGRANT.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-NAME-TYPE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-INFANT.md b/_pages/tag-def/enum-INFANT.md
index 542f038..392f6b1 100644
--- a/_pages/tag-def/enum-INFANT.md
+++ b/_pages/tag-def/enum-INFANT.md
@@ -25,6 +25,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-LOCKED.md b/_pages/tag-def/enum-LOCKED.md
index 6d4a0a9..69d17e2 100644
--- a/_pages/tag-def/enum-LOCKED.md
+++ b/_pages/tag-def/enum-LOCKED.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-RESN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-M.md b/_pages/tag-def/enum-M.md
index d21a792..2d34b1f 100644
--- a/_pages/tag-def/enum-M.md
+++ b/_pages/tag-def/enum-M.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-SEX"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-MAGAZINE.md b/_pages/tag-def/enum-MAGAZINE.md
index 6aa98f0..a2a7cfc 100644
--- a/_pages/tag-def/enum-MAGAZINE.md
+++ b/_pages/tag-def/enum-MAGAZINE.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-MAIDEN.md b/_pages/tag-def/enum-MAIDEN.md
index 27d5b17..bfa946e 100644
--- a/_pages/tag-def/enum-MAIDEN.md
+++ b/_pages/tag-def/enum-MAIDEN.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-NAME-TYPE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-MANUSCRIPT.md b/_pages/tag-def/enum-MANUSCRIPT.md
index 16eb241..9257e26 100644
--- a/_pages/tag-def/enum-MANUSCRIPT.md
+++ b/_pages/tag-def/enum-MANUSCRIPT.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-MAP.md b/_pages/tag-def/enum-MAP.md
index 45f0ea4..6b99a63 100644
--- a/_pages/tag-def/enum-MAP.md
+++ b/_pages/tag-def/enum-MAP.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-MARRIED.md b/_pages/tag-def/enum-MARRIED.md
index b3a3026..57767e5 100644
--- a/_pages/tag-def/enum-MARRIED.md
+++ b/_pages/tag-def/enum-MARRIED.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-NAME-TYPE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-MOTH.md b/_pages/tag-def/enum-MOTH.md
index 5b9ccf0..c3014b5 100644
--- a/_pages/tag-def/enum-MOTH.md
+++ b/_pages/tag-def/enum-MOTH.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-MULTIPLE.md b/_pages/tag-def/enum-MULTIPLE.md
index a903c59..bf5d036 100644
--- a/_pages/tag-def/enum-MULTIPLE.md
+++ b/_pages/tag-def/enum-MULTIPLE.md
@@ -24,6 +24,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-NCHI.md b/_pages/tag-def/enum-NCHI.md
index d851159..134e8f7 100644
--- a/_pages/tag-def/enum-NCHI.md
+++ b/_pages/tag-def/enum-NCHI.md
@@ -24,6 +24,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-NEWSPAPER.md b/_pages/tag-def/enum-NEWSPAPER.md
index 621e452..bc0bb7e 100644
--- a/_pages/tag-def/enum-NEWSPAPER.md
+++ b/_pages/tag-def/enum-NEWSPAPER.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-NGHBR.md b/_pages/tag-def/enum-NGHBR.md
index 07acac5..eb01341 100644
--- a/_pages/tag-def/enum-NGHBR.md
+++ b/_pages/tag-def/enum-NGHBR.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-OFFICIATOR.md b/_pages/tag-def/enum-OFFICIATOR.md
index b212600..d4d238f 100644
--- a/_pages/tag-def/enum-OFFICIATOR.md
+++ b/_pages/tag-def/enum-OFFICIATOR.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-OTHER.md b/_pages/tag-def/enum-OTHER.md
index 5453169..0d3185c 100644
--- a/_pages/tag-def/enum-OTHER.md
+++ b/_pages/tag-def/enum-OTHER.md
@@ -26,6 +26,8 @@ value of:
   - "https://gedcom.io/terms/v7/enumset-NAME-TYPE"
   - "https://gedcom.io/terms/v7/enumset-PEDI"
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-PARENT.md b/_pages/tag-def/enum-PARENT.md
index 79842b2..1f1e3ce 100644
--- a/_pages/tag-def/enum-PARENT.md
+++ b/_pages/tag-def/enum-PARENT.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-PHOTO.md b/_pages/tag-def/enum-PHOTO.md
index 3958810..b70c23d 100644
--- a/_pages/tag-def/enum-PHOTO.md
+++ b/_pages/tag-def/enum-PHOTO.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-PRE_1970.md b/_pages/tag-def/enum-PRE_1970.md
index fb63112..cefd70d 100644
--- a/_pages/tag-def/enum-PRE_1970.md
+++ b/_pages/tag-def/enum-PRE_1970.md
@@ -26,6 +26,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-PRIVACY.md b/_pages/tag-def/enum-PRIVACY.md
index 559118c..2448a94 100644
--- a/_pages/tag-def/enum-PRIVACY.md
+++ b/_pages/tag-def/enum-PRIVACY.md
@@ -26,6 +26,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-RESN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-PROFESSIONAL.md b/_pages/tag-def/enum-PROFESSIONAL.md
index cbbc957..451c2c7 100644
--- a/_pages/tag-def/enum-PROFESSIONAL.md
+++ b/_pages/tag-def/enum-PROFESSIONAL.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-NAME-TYPE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-PROVEN.md b/_pages/tag-def/enum-PROVEN.md
index 4bcbc7c..5212274 100644
--- a/_pages/tag-def/enum-PROVEN.md
+++ b/_pages/tag-def/enum-PROVEN.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-FAMC-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-RESI.md b/_pages/tag-def/enum-RESI.md
index 68cabdc..b444b08 100644
--- a/_pages/tag-def/enum-RESI.md
+++ b/_pages/tag-def/enum-RESI.md
@@ -24,6 +24,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-EVENATTR"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-SEALING.md b/_pages/tag-def/enum-SEALING.md
index 9aca898..d63e461 100644
--- a/_pages/tag-def/enum-SEALING.md
+++ b/_pages/tag-def/enum-SEALING.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-PEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-SPOU.md b/_pages/tag-def/enum-SPOU.md
index 7d5f4ce..08964db 100644
--- a/_pages/tag-def/enum-SPOU.md
+++ b/_pages/tag-def/enum-SPOU.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-STILLBORN.md b/_pages/tag-def/enum-STILLBORN.md
index 24f9d76..7125c37 100644
--- a/_pages/tag-def/enum-STILLBORN.md
+++ b/_pages/tag-def/enum-STILLBORN.md
@@ -25,6 +25,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-SUBMITTED.md b/_pages/tag-def/enum-SUBMITTED.md
index f0f4da4..70b0082 100644
--- a/_pages/tag-def/enum-SUBMITTED.md
+++ b/_pages/tag-def/enum-SUBMITTED.md
@@ -26,6 +26,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-TOMBSTONE.md b/_pages/tag-def/enum-TOMBSTONE.md
index 84b561b..4c2c9ec 100644
--- a/_pages/tag-def/enum-TOMBSTONE.md
+++ b/_pages/tag-def/enum-TOMBSTONE.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-U.md b/_pages/tag-def/enum-U.md
index 3a27b40..14d39f9 100644
--- a/_pages/tag-def/enum-U.md
+++ b/_pages/tag-def/enum-U.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-SEX"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-UNCLEARED.md b/_pages/tag-def/enum-UNCLEARED.md
index 1f0561d..280e59a 100644
--- a/_pages/tag-def/enum-UNCLEARED.md
+++ b/_pages/tag-def/enum-UNCLEARED.md
@@ -26,6 +26,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ord-STAT"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-VIDEO.md b/_pages/tag-def/enum-VIDEO.md
index efbcf5e..612f597 100644
--- a/_pages/tag-def/enum-VIDEO.md
+++ b/_pages/tag-def/enum-VIDEO.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-MEDI"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-WIFE.md b/_pages/tag-def/enum-WIFE.md
index fbdee06..83f6cca 100644
--- a/_pages/tag-def/enum-WIFE.md
+++ b/_pages/tag-def/enum-WIFE.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-WITN.md b/_pages/tag-def/enum-WITN.md
index c9c4261..c16a043 100644
--- a/_pages/tag-def/enum-WITN.md
+++ b/_pages/tag-def/enum-WITN.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-ROLE"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enum-X.md b/_pages/tag-def/enum-X.md
index d1dc079..d78b9bb 100644
--- a/_pages/tag-def/enum-X.md
+++ b/_pages/tag-def/enum-X.md
@@ -23,6 +23,8 @@ specification:
 
 value of:
   - "https://gedcom.io/terms/v7/enumset-SEX"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-ADOP.md b/_pages/tag-def/enumset-ADOP.md
index 162ac8a..9972c8d 100644
--- a/_pages/tag-def/enumset-ADOP.md
+++ b/_pages/tag-def/enumset-ADOP.md
@@ -20,6 +20,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-ADOP-HUSB"
   - "https://gedcom.io/terms/v7/enum-ADOP-WIFE"
   - "https://gedcom.io/terms/v7/enum-BOTH"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-EVEN.md b/_pages/tag-def/enumset-EVEN.md
index 9638eaf..ba346f8 100644
--- a/_pages/tag-def/enumset-EVEN.md
+++ b/_pages/tag-def/enumset-EVEN.md
@@ -48,6 +48,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/MARL"
   - "https://gedcom.io/terms/v7/MARR"
   - "https://gedcom.io/terms/v7/MARS"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-EVENATTR.md b/_pages/tag-def/enumset-EVENATTR.md
index 5866a26..5692b79 100644
--- a/_pages/tag-def/enumset-EVENATTR.md
+++ b/_pages/tag-def/enumset-EVENATTR.md
@@ -63,6 +63,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/RELI"
   - "https://gedcom.io/terms/v7/SSN"
   - "https://gedcom.io/terms/v7/TITL"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-FAMC-STAT.md b/_pages/tag-def/enumset-FAMC-STAT.md
index c363494..4ee49b0 100644
--- a/_pages/tag-def/enumset-FAMC-STAT.md
+++ b/_pages/tag-def/enumset-FAMC-STAT.md
@@ -20,6 +20,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-CHALLENGED"
   - "https://gedcom.io/terms/v7/enum-DISPROVEN"
   - "https://gedcom.io/terms/v7/enum-PROVEN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-MEDI.md b/_pages/tag-def/enumset-MEDI.md
index c2c06b5..a45536b 100644
--- a/_pages/tag-def/enumset-MEDI.md
+++ b/_pages/tag-def/enumset-MEDI.md
@@ -31,6 +31,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-TOMBSTONE"
   - "https://gedcom.io/terms/v7/enum-VIDEO"
   - "https://gedcom.io/terms/v7/enum-OTHER"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-NAME-TYPE.md b/_pages/tag-def/enumset-NAME-TYPE.md
index acb5c92..d77fde0 100644
--- a/_pages/tag-def/enumset-NAME-TYPE.md
+++ b/_pages/tag-def/enumset-NAME-TYPE.md
@@ -24,6 +24,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-MARRIED"
   - "https://gedcom.io/terms/v7/enum-PROFESSIONAL"
   - "https://gedcom.io/terms/v7/enum-OTHER"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-PEDI.md b/_pages/tag-def/enumset-PEDI.md
index 4d3c4fb..0dcd04a 100644
--- a/_pages/tag-def/enumset-PEDI.md
+++ b/_pages/tag-def/enumset-PEDI.md
@@ -22,6 +22,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-FOSTER"
   - "https://gedcom.io/terms/v7/enum-SEALING"
   - "https://gedcom.io/terms/v7/enum-OTHER"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-QUAY.md b/_pages/tag-def/enumset-QUAY.md
index 0857544..bf72dcc 100644
--- a/_pages/tag-def/enumset-QUAY.md
+++ b/_pages/tag-def/enumset-QUAY.md
@@ -21,6 +21,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-1"
   - "https://gedcom.io/terms/v7/enum-2"
   - "https://gedcom.io/terms/v7/enum-3"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-RESN.md b/_pages/tag-def/enumset-RESN.md
index 636689c..718bec0 100644
--- a/_pages/tag-def/enumset-RESN.md
+++ b/_pages/tag-def/enumset-RESN.md
@@ -20,6 +20,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-CONFIDENTIAL"
   - "https://gedcom.io/terms/v7/enum-LOCKED"
   - "https://gedcom.io/terms/v7/enum-PRIVACY"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-ROLE.md b/_pages/tag-def/enumset-ROLE.md
index 28b0615..45adf6d 100644
--- a/_pages/tag-def/enumset-ROLE.md
+++ b/_pages/tag-def/enumset-ROLE.md
@@ -32,6 +32,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-WIFE"
   - "https://gedcom.io/terms/v7/enum-WITN"
   - "https://gedcom.io/terms/v7/enum-OTHER"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-SEX.md b/_pages/tag-def/enumset-SEX.md
index f6bfe90..af8eb30 100644
--- a/_pages/tag-def/enumset-SEX.md
+++ b/_pages/tag-def/enumset-SEX.md
@@ -21,6 +21,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-F"
   - "https://gedcom.io/terms/v7/enum-X"
   - "https://gedcom.io/terms/v7/enum-U"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/enumset-ord-STAT.md b/_pages/tag-def/enumset-ord-STAT.md
index 7a9fb54..e8f81c1 100644
--- a/_pages/tag-def/enumset-ord-STAT.md
+++ b/_pages/tag-def/enumset-ord-STAT.md
@@ -29,6 +29,8 @@ enumeration values:
   - "https://gedcom.io/terms/v7/enum-STILLBORN"
   - "https://gedcom.io/terms/v7/enum-SUBMITTED"
   - "https://gedcom.io/terms/v7/enum-UNCLEARED"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-AAV.md b/_pages/tag-def/month-AAV.md
index 468b51f..cae2521 100644
--- a/_pages/tag-def/month-AAV.md
+++ b/_pages/tag-def/month-AAV.md
@@ -25,6 +25,8 @@ label: 'Av'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-ADR.md b/_pages/tag-def/month-ADR.md
index 21a8146..d92155f 100644
--- a/_pages/tag-def/month-ADR.md
+++ b/_pages/tag-def/month-ADR.md
@@ -25,6 +25,8 @@ label: 'Adar I'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-ADS.md b/_pages/tag-def/month-ADS.md
index 0ee5604..0fd4c46 100644
--- a/_pages/tag-def/month-ADS.md
+++ b/_pages/tag-def/month-ADS.md
@@ -25,6 +25,8 @@ label: 'Adar'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-APR.md b/_pages/tag-def/month-APR.md
index 3a2346b..3d29c64 100644
--- a/_pages/tag-def/month-APR.md
+++ b/_pages/tag-def/month-APR.md
@@ -26,6 +26,8 @@ label: 'April'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-AUG.md b/_pages/tag-def/month-AUG.md
index 8ffaedc..3636395 100644
--- a/_pages/tag-def/month-AUG.md
+++ b/_pages/tag-def/month-AUG.md
@@ -26,6 +26,8 @@ label: 'August'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-BRUM.md b/_pages/tag-def/month-BRUM.md
index ebe052d..423e6e7 100644
--- a/_pages/tag-def/month-BRUM.md
+++ b/_pages/tag-def/month-BRUM.md
@@ -25,6 +25,8 @@ label: 'Brumaire'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-COMP.md b/_pages/tag-def/month-COMP.md
index e4f25f1..6c1b086 100644
--- a/_pages/tag-def/month-COMP.md
+++ b/_pages/tag-def/month-COMP.md
@@ -25,6 +25,8 @@ label: 'Jour Complémentaires'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-CSH.md b/_pages/tag-def/month-CSH.md
index 3bd1020..c3ba010 100644
--- a/_pages/tag-def/month-CSH.md
+++ b/_pages/tag-def/month-CSH.md
@@ -25,6 +25,8 @@ label: 'Marcheshvan'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-DEC.md b/_pages/tag-def/month-DEC.md
index 2eb7088..8ad7744 100644
--- a/_pages/tag-def/month-DEC.md
+++ b/_pages/tag-def/month-DEC.md
@@ -26,6 +26,8 @@ label: 'December'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-ELL.md b/_pages/tag-def/month-ELL.md
index 93b8b7a..827fd6d 100644
--- a/_pages/tag-def/month-ELL.md
+++ b/_pages/tag-def/month-ELL.md
@@ -25,6 +25,8 @@ label: 'Elul'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-FEB.md b/_pages/tag-def/month-FEB.md
index b5bdad7..fa70894 100644
--- a/_pages/tag-def/month-FEB.md
+++ b/_pages/tag-def/month-FEB.md
@@ -26,6 +26,8 @@ label: 'February'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-FLOR.md b/_pages/tag-def/month-FLOR.md
index bb45c93..141c4ba 100644
--- a/_pages/tag-def/month-FLOR.md
+++ b/_pages/tag-def/month-FLOR.md
@@ -25,6 +25,8 @@ label: 'Floréal'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-FRIM.md b/_pages/tag-def/month-FRIM.md
index 9fdec63..ac407d9 100644
--- a/_pages/tag-def/month-FRIM.md
+++ b/_pages/tag-def/month-FRIM.md
@@ -25,6 +25,8 @@ label: 'Frimaire'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-FRUC.md b/_pages/tag-def/month-FRUC.md
index 281a18d..db1211b 100644
--- a/_pages/tag-def/month-FRUC.md
+++ b/_pages/tag-def/month-FRUC.md
@@ -25,6 +25,8 @@ label: 'Fructidor'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-GERM.md b/_pages/tag-def/month-GERM.md
index 84140d7..8548ce0 100644
--- a/_pages/tag-def/month-GERM.md
+++ b/_pages/tag-def/month-GERM.md
@@ -25,6 +25,8 @@ label: 'Germinal'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-IYR.md b/_pages/tag-def/month-IYR.md
index db725de..ebd24dc 100644
--- a/_pages/tag-def/month-IYR.md
+++ b/_pages/tag-def/month-IYR.md
@@ -25,6 +25,8 @@ label: 'Iyar'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-JAN.md b/_pages/tag-def/month-JAN.md
index c6e0e81..4d63ec5 100644
--- a/_pages/tag-def/month-JAN.md
+++ b/_pages/tag-def/month-JAN.md
@@ -26,6 +26,8 @@ label: 'January'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-JUL.md b/_pages/tag-def/month-JUL.md
index 626526b..3300ab3 100644
--- a/_pages/tag-def/month-JUL.md
+++ b/_pages/tag-def/month-JUL.md
@@ -26,6 +26,8 @@ label: 'July'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-JUN.md b/_pages/tag-def/month-JUN.md
index e8b55bb..b35bb0d 100644
--- a/_pages/tag-def/month-JUN.md
+++ b/_pages/tag-def/month-JUN.md
@@ -26,6 +26,8 @@ label: 'June'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-KSL.md b/_pages/tag-def/month-KSL.md
index e424407..affbc96 100644
--- a/_pages/tag-def/month-KSL.md
+++ b/_pages/tag-def/month-KSL.md
@@ -25,6 +25,8 @@ label: 'Kislev'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-MAR.md b/_pages/tag-def/month-MAR.md
index 9b4cdc3..60fc6b3 100644
--- a/_pages/tag-def/month-MAR.md
+++ b/_pages/tag-def/month-MAR.md
@@ -26,6 +26,8 @@ label: 'March'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-MAY.md b/_pages/tag-def/month-MAY.md
index 6726195..ae56165 100644
--- a/_pages/tag-def/month-MAY.md
+++ b/_pages/tag-def/month-MAY.md
@@ -26,6 +26,8 @@ label: 'May'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-MESS.md b/_pages/tag-def/month-MESS.md
index a98538a..9bf2e2f 100644
--- a/_pages/tag-def/month-MESS.md
+++ b/_pages/tag-def/month-MESS.md
@@ -25,6 +25,8 @@ label: 'Messidor'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-NIVO.md b/_pages/tag-def/month-NIVO.md
index ffa3113..3e198d6 100644
--- a/_pages/tag-def/month-NIVO.md
+++ b/_pages/tag-def/month-NIVO.md
@@ -25,6 +25,8 @@ label: 'Nivôse'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-NOV.md b/_pages/tag-def/month-NOV.md
index 6e17fc0..a2ecefd 100644
--- a/_pages/tag-def/month-NOV.md
+++ b/_pages/tag-def/month-NOV.md
@@ -26,6 +26,8 @@ label: 'November'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-NSN.md b/_pages/tag-def/month-NSN.md
index 9e0401f..79f3df8 100644
--- a/_pages/tag-def/month-NSN.md
+++ b/_pages/tag-def/month-NSN.md
@@ -25,6 +25,8 @@ label: 'Nisan'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-OCT.md b/_pages/tag-def/month-OCT.md
index 5a9de0d..2f4311a 100644
--- a/_pages/tag-def/month-OCT.md
+++ b/_pages/tag-def/month-OCT.md
@@ -26,6 +26,8 @@ label: 'October'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-PLUV.md b/_pages/tag-def/month-PLUV.md
index c27a861..2811330 100644
--- a/_pages/tag-def/month-PLUV.md
+++ b/_pages/tag-def/month-PLUV.md
@@ -25,6 +25,8 @@ label: 'Pluviôse'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-PRAI.md b/_pages/tag-def/month-PRAI.md
index b4b97b4..6b506d4 100644
--- a/_pages/tag-def/month-PRAI.md
+++ b/_pages/tag-def/month-PRAI.md
@@ -25,6 +25,8 @@ label: 'Prairial'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-SEP.md b/_pages/tag-def/month-SEP.md
index 4b29b73..fe4e072 100644
--- a/_pages/tag-def/month-SEP.md
+++ b/_pages/tag-def/month-SEP.md
@@ -26,6 +26,8 @@ label: 'September'
 calendars:
   - "https://gedcom.io/terms/v7/cal-GREGORIAN"
   - "https://gedcom.io/terms/v7/cal-JULIAN"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-SHV.md b/_pages/tag-def/month-SHV.md
index 7dff397..9165aeb 100644
--- a/_pages/tag-def/month-SHV.md
+++ b/_pages/tag-def/month-SHV.md
@@ -25,6 +25,8 @@ label: 'Shevat'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-SVN.md b/_pages/tag-def/month-SVN.md
index 8a07f6f..fdb9192 100644
--- a/_pages/tag-def/month-SVN.md
+++ b/_pages/tag-def/month-SVN.md
@@ -25,6 +25,8 @@ label: 'Sivan'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-THER.md b/_pages/tag-def/month-THER.md
index 28e4882..867a81f 100644
--- a/_pages/tag-def/month-THER.md
+++ b/_pages/tag-def/month-THER.md
@@ -25,6 +25,8 @@ label: 'Thermidor'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-TMZ.md b/_pages/tag-def/month-TMZ.md
index a222297..c075ed7 100644
--- a/_pages/tag-def/month-TMZ.md
+++ b/_pages/tag-def/month-TMZ.md
@@ -25,6 +25,8 @@ label: 'Tammuz'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-TSH.md b/_pages/tag-def/month-TSH.md
index 33f031b..e859765 100644
--- a/_pages/tag-def/month-TSH.md
+++ b/_pages/tag-def/month-TSH.md
@@ -25,6 +25,8 @@ label: 'Tishrei'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-TVT.md b/_pages/tag-def/month-TVT.md
index 515c17e..8032de1 100644
--- a/_pages/tag-def/month-TVT.md
+++ b/_pages/tag-def/month-TVT.md
@@ -25,6 +25,8 @@ label: 'Tevet'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-HEBREW"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-VEND.md b/_pages/tag-def/month-VEND.md
index 333df4f..c1ec385 100644
--- a/_pages/tag-def/month-VEND.md
+++ b/_pages/tag-def/month-VEND.md
@@ -25,6 +25,8 @@ label: 'Vendémiaire'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/month-VENT.md b/_pages/tag-def/month-VENT.md
index 8b544cd..4b49b40 100644
--- a/_pages/tag-def/month-VENT.md
+++ b/_pages/tag-def/month-VENT.md
@@ -25,6 +25,8 @@ label: 'Ventôse'
 
 calendars:
   - "https://gedcom.io/terms/v7/cal-FRENCH_R"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/ord-STAT.md b/_pages/tag-def/ord-STAT.md
index 3452517..4698679 100644
--- a/_pages/tag-def/ord-STAT.md
+++ b/_pages/tag-def/ord-STAT.md
@@ -39,6 +39,8 @@ superstructures:
   "https://gedcom.io/terms/v7/INIL": "{0:1}"
   "https://gedcom.io/terms/v7/SLGC": "{0:1}"
   "https://gedcom.io/terms/v7/SLGS": "{0:1}"
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/record-FAM.md b/_pages/tag-def/record-FAM.md
index 8e9446b..321abd3 100644
--- a/_pages/tag-def/record-FAM.md
+++ b/_pages/tag-def/record-FAM.md
@@ -122,6 +122,8 @@ substructures:
   "https://gedcom.io/terms/v7/UID": "{0:M}"
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/record-INDI.md b/_pages/tag-def/record-INDI.md
index 2cb433e..6ad0391 100644
--- a/_pages/tag-def/record-INDI.md
+++ b/_pages/tag-def/record-INDI.md
@@ -131,6 +131,8 @@ substructures:
   "https://gedcom.io/terms/v7/WILL": "{0:M}"
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/record-OBJE.md b/_pages/tag-def/record-OBJE.md
index f0c0682..520b23a 100644
--- a/_pages/tag-def/record-OBJE.md
+++ b/_pages/tag-def/record-OBJE.md
@@ -49,6 +49,8 @@ substructures:
   "https://gedcom.io/terms/v7/UID": "{0:M}"
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/record-REPO.md b/_pages/tag-def/record-REPO.md
index 7e2a70d..ff1316b 100644
--- a/_pages/tag-def/record-REPO.md
+++ b/_pages/tag-def/record-REPO.md
@@ -55,6 +55,8 @@ substructures:
   "https://gedcom.io/terms/v7/WWW": "{0:M}"
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/record-SNOTE.md b/_pages/tag-def/record-SNOTE.md
index 4fecf80..75d4997 100644
--- a/_pages/tag-def/record-SNOTE.md
+++ b/_pages/tag-def/record-SNOTE.md
@@ -82,6 +82,8 @@ substructures:
   "https://gedcom.io/terms/v7/UID": "{0:M}"
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/record-SOUR.md b/_pages/tag-def/record-SOUR.md
index 4c28a12..8f07137 100644
--- a/_pages/tag-def/record-SOUR.md
+++ b/_pages/tag-def/record-SOUR.md
@@ -61,6 +61,8 @@ substructures:
   "https://gedcom.io/terms/v7/UID": "{0:M}"
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/record-SUBM.md b/_pages/tag-def/record-SUBM.md
index ed30c53..5745b62 100644
--- a/_pages/tag-def/record-SUBM.md
+++ b/_pages/tag-def/record-SUBM.md
@@ -49,6 +49,8 @@ substructures:
   "https://gedcom.io/terms/v7/WWW": "{0:M}"
 
 superstructures: {}
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/type-Age.md b/_pages/tag-def/type-Age.md
index e3c1eef..5f0b1b1 100644
--- a/_pages/tag-def/type-Age.md
+++ b/_pages/tag-def/type-Age.md
@@ -80,6 +80,8 @@ specification:
     </div>
     
     The URI for the `Age` data type is `https://gedcom.io/terms/v7/type-Age`.
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/type-Date.md b/_pages/tag-def/type-Date.md
index 79c4af4..8f4960e 100644
--- a/_pages/tag-def/type-Date.md
+++ b/_pages/tag-def/type-Date.md
@@ -132,6 +132,8 @@ specification:
     
     The URI for the `DatePeriod` data type is
     `https://gedcom.io/terms/v7/type-Date#period`.
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/type-Enum.md b/_pages/tag-def/type-Enum.md
index 1b31fb3..e7ee01b 100644
--- a/_pages/tag-def/type-Enum.md
+++ b/_pages/tag-def/type-Enum.md
@@ -60,6 +60,8 @@ specification:
     </div>
     
     The URI for the `Enum` data type is `https://gedcom.io/terms/v7/type-Enum`.
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/type-FilePath.md b/_pages/tag-def/type-FilePath.md
index e63e929..6b34375 100644
--- a/_pages/tag-def/type-FilePath.md
+++ b/_pages/tag-def/type-FilePath.md
@@ -63,6 +63,8 @@ specification:
     
     The URI for the `FilePath` data type is
     `https://gedcom.io/terms/v7/type-FilePath`.
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/type-List.md b/_pages/tag-def/type-List.md
index e03a926..046a0f8 100644
--- a/_pages/tag-def/type-List.md
+++ b/_pages/tag-def/type-List.md
@@ -53,6 +53,8 @@ specification:
     
     The URI for the `List:Enum` data type is
     `https://gedcom.io/terms/v7/type-List#Enum`.
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/type-Name.md b/_pages/tag-def/type-Name.md
index cbd9f0d..ab64da7 100644
--- a/_pages/tag-def/type-Name.md
+++ b/_pages/tag-def/type-Name.md
@@ -38,6 +38,8 @@ specification:
     
     The URI for the `PersonalName` data type is
     `https://gedcom.io/terms/v7/type-Name`.
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/_pages/tag-def/type-Time.md b/_pages/tag-def/type-Time.md
index 05ae139..85487a3 100644
--- a/_pages/tag-def/type-Time.md
+++ b/_pages/tag-def/type-Time.md
@@ -28,10 +28,10 @@ specification:
     ```abnf
     Time     =  hour ":" minute [":" second ["." fraction]] [%s"Z"]
     
-    hour     = digit / ("0" / "1") digit / "2" ("0" / "1" / "2" / "3")
-    minute   = ("0" / "1" / "2" / "3" / "4" / "5") digit
-    second   = ("0" / "1" / "2" / "3" / "4" / "5") digit
-    fraction = 1*digit
+    hour     = DIGIT / ("0" / "1") DIGIT / "2" ("0" / "1" / "2" / "3")
+    minute   = ("0" / "1" / "2" / "3" / "4" / "5") DIGIT
+    second   = ("0" / "1" / "2" / "3" / "4" / "5") DIGIT
+    fraction = 1*DIGIT
     ```
     
     <div class="note">
@@ -42,6 +42,8 @@ specification:
     </div>
     
     The URI for the `Time` data type is `https://gedcom.io/terms/v7/type-Time`.
+
+contact: "https://gedcom.io/community/"
 ...
 
 ```
diff --git a/specifications/FamilySearchGEDCOMv7.html b/specifications/FamilySearchGEDCOMv7.html
index 21b37c9..59248f4 100644
--- a/specifications/FamilySearchGEDCOMv7.html
+++ b/specifications/FamilySearchGEDCOMv7.html
@@ -3,7 +3,7 @@
 <head>
   <meta charset="utf-8" />
   <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
-  <meta name="dcterms.date" content="2024-02-08" />
+  <meta name="dcterms.date" content="2024-09-03" />
   <title>The FamilySearch GEDCOM Specification</title>
   <style>
     code{white-space: pre-wrap;}
@@ -79,7 +79,7 @@
     code span.wa { color: #bf0303; } /* Warning */
     @page {
     @top-left { content: "The FamilySearch GEDCOM Specification"; font-size: 70%; }
-    @top-right { content: "7.0.14"; font-size: 70%; }
+    @top-right { content: "7.0.15"; font-size: 70%; }
     }
   </style>
   <style type="text/css">
@@ -440,13 +440,13 @@
 
 <header>
 <h1 class="title">The FamilySearch GEDCOM Specification</h1>
-<h3 class="subtitle">7.0.14</h3>
+<h3 class="subtitle">7.0.15</h3>
 
 <div class="author">
 <p>Prepared by the</p><div style="font-size:130%"><p>Family History Department<br /> The Church of Jesus Christ of Latter-day Saints</p></div>
 </div>
 
-<p class="date"> 8 February 2024</p>
+<p class="date"> 3 September 2024</p>
 
 <div class="contact">
 <strong>Suggestions and Correspondence:</strong>
@@ -475,13 +475,13 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb1-3"><a href="#cb1-3"></a>       <span class="cf">/</span> <span class="ch">%x80-9F</span>                     <span class="co">; C1</span></span>
 <span id="cb1-4"><a href="#cb1-4"></a>       <span class="cf">/</span> <span class="ch">%xD800-DFFF</span>                 <span class="co">; Surrogates</span></span>
 <span id="cb1-5"><a href="#cb1-5"></a>       <span class="cf">/</span> <span class="ch">%xFFFE-FFFF</span>                 <span class="co">; invalid</span></span>
-<span id="cb1-6"><a href="#cb1-6"></a><span class="co">; All other rules assume the absence of any banned characters</span></span></code></pre></div><p>All other ABNF expressions in this document assume the absence of any characters matching production <a href="#characters" class="close"><code>banned</code></a>.</p><p>This document additionally makes use of the following named character sets in ABNF:</p><div class="sourceCode" id="cb2"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb2-1"><a href="#cb2-1"></a><span class="va">digit</span>       <span class="cf">=</span> <span class="ch">%x30-39</span>   <span class="co">; 0 through 9</span></span>
+<span id="cb1-6"><a href="#cb1-6"></a><span class="co">; All other rules assume the absence of any banned characters</span></span></code></pre></div><p>All other ABNF expressions in this document assume the absence of any characters matching production <a href="#characters" class="close"><code>banned</code></a>.</p><p>This document additionally makes use of the following named character sets in ABNF:</p><div class="sourceCode" id="cb2"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb2-1"><a href="#cb2-1"></a><span class="co">; DIGIT     = %x30-39   ; 0 through 9 -- defined in RFC 5234 section B.1</span></span>
 <span id="cb2-2"><a href="#cb2-2"></a><span class="va">nonzero</span>     <span class="cf">=</span> <span class="ch">%x31-39</span>   <span class="co">; 1 through 9</span></span>
 <span id="cb2-3"><a href="#cb2-3"></a><span class="va">ucletter</span>    <span class="cf">=</span> <span class="ch">%x41-5A</span>   <span class="co">; A through Z</span></span>
 <span id="cb2-4"><a href="#cb2-4"></a><span class="va">underscore</span>  <span class="cf">=</span> <span class="ch">%x5F</span>      <span class="co">; _</span></span>
 <span id="cb2-5"><a href="#cb2-5"></a><span class="va">atsign</span>      <span class="cf">=</span> <span class="ch">%x40</span>      <span class="co">; @</span></span></code></pre></div></section><section id="structures" data-number="1.2"><h2 data-number="1.2"><span class="header-section-number">1.2</span> Structures</h2><p>A <strong>structure</strong> consists of a structure type, an optional <strong>payload</strong>, and a collection of substructures. The payload is a value expressed as a string using 1 of several data types, as described in <a href="#datatypes">Chapter 2</a>.</p><p>Every structure is either a <strong>record</strong>, meaning it is not contained in any other structure’s collection of substructures, or it is a <strong>substructure</strong> of exactly 1 other structure. The other structure is called its <strong>superstructure</strong>. Each substructure either refines the meaning of its superstructure, provides metadata about its superstructure, or introduces new data that is closely related to its superstructure.</p><p>Each <strong>structure type</strong> is identified by a URI and defines several properties of any structure with that type, including</p><ul><li><p>The meaning of structures of this type.</p></li><li><p>The payload type of the structure’s payload, which shall be one of</p><ul><li>no payload, or</li><li>a pointer to a record with a specific structure type, or</li><li>a <a href="#datatypes">data type</a>; if an <a href="#enumeration">enumeration</a> or <a href="#list">list of enumerations</a>, also a set of permitted enumeration values.</li></ul></li><li><p>Which structure types may appear as substructures of the structure and with what <strong>cardinality</strong> they may appear. Cardinality is specified by two flags:</p><ul><li>whether a substructure of this type is required or not; and</li><li>whether multiple substructures of this type are permitted or not.</li></ul></li></ul><p>The collection of substructures is partially ordered. Substructures with the same structure type are in a fixed order, but substructures with different structure types may be reordered. The order of substructures of a single type indicates user preference, with the first substructure being the most-preferred value, unless a different meaning is explicitly indicated in the structure’s definition.</p><p>A structure must have either a non-empty payload or at least 1 substructure. Empty payloads and missing payloads are considered equivalent. The remainder of this document uses “payload” as shorthand for “non-empty payload”.</p><div class="note"><p>Unlike structures, pseudo-structures needn’t have either payloads or substructures. <a href="#TRLR"><code>TRLR</code></a> never has either, and <a href="#CONT"><code>CONT</code></a> doesn’t when payloads contain empty lines.</p></div><p>A structure is a representation of data about its <strong>subject</strong>. Examples include the entity, event, claim, or activity that the structure describes.</p><p>Datasets also contain 3 types of pseudo-structures:</p><ul><li><p>The header resembles a record, comes first in each document, and contains metadata about the entire document in its substructures. See <a href="#the-header">The Header</a> for more details.</p></li><li><p>The trailer resembles a record, comes last in each document, and cannot contain substructures.</p></li><li><p>A line continuation resembles a substructure, comes before any other substructures, is used to encode multi-line payloads, and cannot contain substructures.</p></li></ul><p>Previous versions limited the number of characters that could appear in a structure, record, and payload. Those restrictions were removed in 7.0.</p></section><section id="lines" data-number="1.3"><h2 data-number="1.3"><span class="header-section-number">1.3</span> Lines</h2><p>A <strong>line</strong> is a string representation of (part of) a <em>structure</em>. A line consists of a level, optional cross-reference identifier, tag, optional line value, and line terminator. It matches the production <a href="#lines" class="close"><code>Line</code></a>:</p><div class="sourceCode" id="cb3"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb3-1"><a href="#cb3-1"></a><span class="va">Line</span>    <span class="cf">=</span> Level D <span class="cf">[</span>Xref D<span class="cf">]</span> Tag <span class="cf">[</span>D LineVal<span class="cf">]</span> EOL</span>
 <span id="cb3-2"><a href="#cb3-2"></a></span>
-<span id="cb3-3"><a href="#cb3-3"></a><span class="va">Level</span>   <span class="cf">=</span> <span class="st">&quot;0&quot;</span> <span class="cf">/</span> nonzero <span class="cf">*</span>digit</span>
+<span id="cb3-3"><a href="#cb3-3"></a><span class="va">Level</span>   <span class="cf">=</span> <span class="st">&quot;0&quot;</span> <span class="cf">/</span> nonzero <span class="cf">*</span>DIGIT</span>
 <span id="cb3-4"><a href="#cb3-4"></a><span class="va">D</span>       <span class="cf">=</span> <span class="ch">%x20</span>                            <span class="co">; space</span></span>
 <span id="cb3-5"><a href="#cb3-5"></a><span class="va">Xref</span>    <span class="cf">=</span> atsign <span class="cf">1</span><span class="er">*</span>tagchar atsign         <span class="co">; but not &quot;@VOID@&quot;</span></span>
 <span id="cb3-6"><a href="#cb3-6"></a><span class="va">Tag</span>     <span class="cf">=</span> stdTag <span class="cf">/</span> extTag</span>
@@ -490,7 +490,7 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb3-9"><a href="#cb3-9"></a></span>
 <span id="cb3-10"><a href="#cb3-10"></a><span class="va">stdTag</span>  <span class="cf">=</span> ucletter <span class="cf">*</span>tagchar</span>
 <span id="cb3-11"><a href="#cb3-11"></a><span class="va">extTag</span>  <span class="cf">=</span> underscore <span class="cf">1</span><span class="er">*</span>tagchar</span>
-<span id="cb3-12"><a href="#cb3-12"></a><span class="va">tagchar</span> <span class="cf">=</span> ucletter <span class="cf">/</span> digit <span class="cf">/</span> underscore</span>
+<span id="cb3-12"><a href="#cb3-12"></a><span class="va">tagchar</span> <span class="cf">=</span> ucletter <span class="cf">/</span> DIGIT <span class="cf">/</span> underscore</span>
 <span id="cb3-13"><a href="#cb3-13"></a></span>
 <span id="cb3-14"><a href="#cb3-14"></a><span class="va">pointer</span> <span class="cf">=</span> voidPtr <span class="cf">/</span> Xref</span>
 <span id="cb3-15"><a href="#cb3-15"></a><span class="va">voidPtr</span> <span class="cf">=</span> <span class="ss">%s&quot;@VOID@&quot;</span></span>
@@ -521,7 +521,7 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb11-3"><a href="#cb11-3"></a><span class="dt">1 </span><span class="fu">NOTE </span>The above enumeration value is not allowed</span></code></pre></div></div><p>Dates may be extended provided they use a calendar that matches production <a href="#lines" class="close"><code>extTag</code></a>. Dates with extension calendars may also use extension months and epochs.</p><section id="extension-tags" data-number="1.5.1"><h3 data-number="1.5.1"><span class="header-section-number">1.5.1</span> Extension Tags</h3><p>Each use of the <a href="#lines" class="close"><code>extTag</code></a> production is called an extension tag, including when used as a tag, calendar, month, epoch, or enumerated value. Each <a href="#lines" class="close"><code>extTag</code></a> is either a <em>documented extension tag</em> or an <em>undocumented extension tag</em>. It is recommended that documented extension tags be used instead of undocumented extension tags wherever possible.</p><p>A <strong>documented extension tag</strong> is a tag that is mapped to a URI using the schema structure. The schema structure is a substructure of the header with tag <a href="#SCHMA"><code>SCHMA</code></a>. It should appear within the document before any extension tags. The schema’s substructures are tag definitions.</p><p>A tag definition is a structure with tag <a href="#TAG"><code>TAG</code></a>. Its payload is an extension tag, a space, and a URI and defines that extension tag to be an abbreviation for that URI within the current document.</p><div class="example"><p>The following header</p><div class="sourceCode" id="cb12"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb12-1"><a href="#cb12-1"></a><span class="dt">0 </span><span class="fu">HEAD</span></span>
 <span id="cb12-2"><a href="#cb12-2"></a><span class="dt">1 </span><span class="fu">SCHMA</span></span>
 <span id="cb12-3"><a href="#cb12-3"></a><span class="dt">2 </span><span class="fu">TAG </span>_SKYPEID http://xmlns.com/foaf/0.1/skypeID</span>
-<span id="cb12-4"><a href="#cb12-4"></a><span class="dt">2 </span><span class="fu">TAG </span>_MEMBER http://xmlns.com/foaf/0.1/member</span></code></pre></div><p>defines the following tags</p><table><thead><tr class="header"><th style="text-align: left;">Tag</th><th style="text-align: left;">Means</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>_SKYPEID</code></td><td style="text-align: left;"><code>http://xmlns.com/foaf/0.1/skypeID</code></td></tr><tr class="even"><td style="text-align: left;"><code>_MEMBER</code></td><td style="text-align: left;"><code>http://xmlns.com/foaf/0.1/member</code></td></tr></tbody></table><p>Note that at the time of writing, the <a href="https://xmlns.com/foaf/spec/20140114.html">FOAF</a> URIs used in this example are not URLs.</p></div><p>The meaning of a documented extension tag is identified by its superstructure type and its URI, not its tag. As such each documented extension tag needs its own URI: it is its URI, not its tag, that defines its meaning. Documented extension tags can be changed freely by modifying the schema, though it is recommended that documented extension tags not be changed. However, a tag change may be necessary if a product picks the same tags for URIs that another product uses for different URIs. A given schema should map only one tag to each URI.</p><div class="example"><p>The following 2 document fragments are semantically equivalent and a system importing one may export it as the other without change of meaning.</p><div class="sourceCode" id="cb13"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb13-1"><a href="#cb13-1"></a><span class="dt">0 </span><span class="fu">HEAD</span></span>
+<span id="cb12-4"><a href="#cb12-4"></a><span class="dt">2 </span><span class="fu">TAG </span>_MEMBER http://xmlns.com/foaf/0.1/member</span></code></pre></div><p>defines the following tags</p><table><thead><tr class="header"><th style="text-align: left;">Tag</th><th style="text-align: left;">Means</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>_SKYPEID</code></td><td style="text-align: left;"><code>http://xmlns.com/foaf/0.1/skypeID</code></td></tr><tr class="even"><td style="text-align: left;"><code>_MEMBER</code></td><td style="text-align: left;"><code>http://xmlns.com/foaf/0.1/member</code></td></tr></tbody></table><p>Note that at the time of writing, the <a href="https://xmlns.com/foaf/spec/20140114.html">FOAF</a> URIs used in this example are not URLs.</p></div><p>The meaning of a documented extension tag is identified by its URI, not its tag. As such each documented extension tag needs its own URI: it is its URI, not its tag, that defines its meaning. Documented extension tags can be changed freely by modifying the schema, though it is recommended that documented extension tags not be changed. However, a tag change may be necessary if a product picks the same tags for URIs that another product uses for different URIs. A given schema should map only one tag to each URI.</p><div class="example"><p>The following 2 document fragments are semantically equivalent and a system importing one may export it as the other without change of meaning.</p><div class="sourceCode" id="cb13"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb13-1"><a href="#cb13-1"></a><span class="dt">0 </span><span class="fu">HEAD</span></span>
 <span id="cb13-2"><a href="#cb13-2"></a><span class="dt">1 </span><span class="fu">SCHMA</span></span>
 <span id="cb13-3"><a href="#cb13-3"></a><span class="dt">2 </span><span class="fu">TAG </span>_SKYPEID http://xmlns.com/foaf/0.1/skypeID</span>
 <span id="cb13-4"><a href="#cb13-4"></a><span class="dt">0 </span><span class="cf">@I0@ </span><span class="fu">INDI</span></span>
@@ -541,7 +541,7 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb16-7"><a href="#cb16-7"></a><span class="dt">1 </span><span class="fu">CHIL </span><span class="va">@I1@</span></span>
 <span id="cb16-8"><a href="#cb16-8"></a><span class="dt">1 </span><span class="fu">CHIL </span><span class="va">@I1@</span></span></code></pre></div><p>provides no information beyond the simpler form:</p><div class="sourceCode" id="cb17"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb17-1"><a href="#cb17-1"></a><span class="dt">0 </span><span class="cf">@I1@ </span><span class="fu">INDI</span></span>
 <span id="cb17-2"><a href="#cb17-2"></a><span class="dt">1 </span><span class="fu">NAME </span>John /Doe/</span></code></pre></div></section></section><section id="datatypes" data-number="2"><h1 data-number="2"><span class="header-section-number">2</span> Data types</h1><p>Every line value (with any continuation pseudo-structures) is a string. However, those strings can encode 1 of several conceptual data types.</p><section id="text" data-number="2.1"><h2 data-number="2.1"><span class="header-section-number">2.1</span> Text</h2><p>A free-text string is text in a human language. Conceptually, it may be either a user-generated string or a source-generated string. Programmatically, both are treated as unconstrained sequences of characters with an associated language.</p><div class="sourceCode" id="cb18"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb18-1"><a href="#cb18-1"></a><span class="va">anychar</span> <span class="cf">=</span> <span class="ch">%x09-10FFFF</span> <span class="co">; but not banned, as with all ABNF rules</span></span>
-<span id="cb18-2"><a href="#cb18-2"></a><span class="va">Text</span>    <span class="cf">=</span> <span class="cf">*</span>anychar</span></code></pre></div><p>The URI for the <a href="#text" class="close"><code>Text</code></a> data type is <code>xsd:string</code>.</p></section><section id="integer" data-number="2.2"><h2 data-number="2.2"><span class="header-section-number">2.2</span> Integer</h2><p>An integer is a non-empty sequence of ASCII decimal digits and represents a non-negative integer in base-10. Leading zeros have no semantic meaning and should be omitted.</p><div class="sourceCode" id="cb19"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb19-1"><a href="#cb19-1"></a><span class="va">Integer</span> <span class="cf">=</span> <span class="cf">1</span><span class="er">*</span>digit</span></code></pre></div><p>Negative integers are not supported by this specification.</p><p>The URI for the <a href="#integer" class="close"><code>Integer</code></a> data type is <code>xsd:nonNegativeInteger</code>.</p></section><section id="enumeration" data-number="2.3"><h2 data-number="2.3"><span class="header-section-number">2.3</span> Enumeration</h2><p>An enumeration is a selection from a set of options. They are represented as a string matching the same production as a tag, with the additional permission that standard enumerations may be integers.</p><div class="sourceCode" id="cb20"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb20-1"><a href="#cb20-1"></a><span class="va">stdEnum</span> <span class="cf">=</span> stdTag <span class="cf">/</span> Integer</span>
+<span id="cb18-2"><a href="#cb18-2"></a><span class="va">Text</span>    <span class="cf">=</span> <span class="cf">*</span>anychar</span></code></pre></div><p>The URI for the <a href="#text" class="close"><code>Text</code></a> data type is <code>xsd:string</code>.</p></section><section id="integer" data-number="2.2"><h2 data-number="2.2"><span class="header-section-number">2.2</span> Integer</h2><p>An integer is a non-empty sequence of ASCII decimal digits and represents a non-negative integer in base-10. Leading zeros have no semantic meaning and should be omitted.</p><div class="sourceCode" id="cb19"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb19-1"><a href="#cb19-1"></a><span class="va">Integer</span> <span class="cf">=</span> <span class="cf">1</span><span class="er">*</span>DIGIT</span></code></pre></div><p>Negative integers are not supported by this specification.</p><p>The URI for the <a href="#integer" class="close"><code>Integer</code></a> data type is <code>xsd:nonNegativeInteger</code>.</p></section><section id="enumeration" data-number="2.3"><h2 data-number="2.3"><span class="header-section-number">2.3</span> Enumeration</h2><p>An enumeration is a selection from a set of options. They are represented as a string matching the same production as a tag, with the additional permission that standard enumerations may be integers.</p><div class="sourceCode" id="cb20"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb20-1"><a href="#cb20-1"></a><span class="va">stdEnum</span> <span class="cf">=</span> stdTag <span class="cf">/</span> Integer</span>
 <span id="cb20-2"><a href="#cb20-2"></a><span class="va">Enum</span>    <span class="cf">=</span> stdEnum <span class="cf">/</span> extTag</span></code></pre></div><p>Each structure type with an enumeration payload also defines specific payload values it permits. These permitted payloads match production <a href="#enumeration" class="close"><code>stdEnum</code></a> and should each have a defined URI. Payload values that match production <a href="#lines"><code>extTag</code></a> are always permitted in structures with an enumeration payload and have their URI defined by the schema.</p><p>Each enumeration value has a distinct meaning as identified by its corresponding URI.</p><p>The URI of a given tag in an enumeration payload is determined by the tag itself and by the structure type of the structure it is in the payload of.</p><div class="example"><p>The tag <a href="#HUSB"><code>HUSB</code></a> is used in this document to represent two enumeration values. Which one is meant can be identified by the structure type it appears in as follows:</p><table><thead><tr class="header"><th>Containing structure type</th><th>Enumeration value identified by tag <code>HUSB</code></th></tr></thead><tbody><tr class="odd"><td><a href="#FAMC-ADOP"><code>g7:FAMC-ADOP</code></a></td><td><code>g7:enum-ADOP-HUSB</code></td></tr><tr class="even"><td><a href="#ROLE"><code>g7:ROLE</code></a></td><td><code>g7:enum-HUSB</code></td></tr></tbody></table><p>An <a href="#extensions">extension</a> could also place either of these enumeration values in an extension structure type; the extension authors should document which one they permit.</p><p>The <a href="#HUSB" class="close"><code>HUSB</code></a> tag is also used to identify two different structure types, <a href="#FAM-HUSB"><code>g7:FAM-HUSB</code></a> and <a href="#HUSB" class="close"><code>g7:HUSB</code></a>.</p></div><p>The URI for the <a href="#enumeration"><code>Enum</code></a> data type is <code>g7:type-Enum</code>.</p></section><section id="date" data-number="2.4"><h2 data-number="2.4"><span class="header-section-number">2.4</span> Date</h2><p>The date formats defined in this specification include the ability to store approximate dates, date periods, and dates expressed in different calendars.</p><p>Technically, there are 3 distinct date data types:</p><ul><li><a href="#date" class="close"><code>DateValue</code></a> is a generic type that can express many kinds of dates.</li><li><a href="#date" class="close"><code>DateExact</code></a> is used for timestamps and other fully-known dates.</li><li><a href="#date" class="close"><code>DatePeriod</code></a> is used to express time intervals that span multiple days.</li></ul><div class="sourceCode" id="cb21"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb21-1"><a href="#cb21-1"></a><span class="va">DateValue</span>   <span class="cf">=</span> <span class="cf">[</span> date <span class="cf">/</span> DatePeriod <span class="cf">/</span> dateRange <span class="cf">/</span> dateApprox <span class="cf">]</span></span>
 <span id="cb21-2"><a href="#cb21-2"></a><span class="va">DateExact</span>   <span class="cf">=</span> day D month D year  <span class="co">; in Gregorian calendar</span></span>
 <span id="cb21-3"><a href="#cb21-3"></a><span class="va">DatePeriod</span>  <span class="cf">=</span> <span class="cf">[</span> <span class="ss">%s&quot;TO&quot;</span> D date <span class="cf">]</span></span>
@@ -566,10 +566,10 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb21-22"><a href="#cb21-22"></a><span class="va">epoch</span>   <span class="cf">=</span> <span class="ss">%s&quot;BCE&quot;</span> <span class="cf">/</span> extTag <span class="co">; constrained by calendar</span></span></code></pre></div><p>In addition to the constraints above:</p><ul><li>The allowable <a href="#date"><code>day</code></a>s, <a href="#date" class="close"><code>month</code></a>s, <a href="#date" class="close"><code>year</code></a>s, and <a href="#date" class="close"><code>epoch</code></a>s are determined by the <a href="#date" class="close"><code>calendar</code></a>. All known calendars restrict <a href="#date" class="close"><code>day</code></a> to be between 1 and a month-specific maximum. The largest known maximum is 36, and most months in most calendars have a lower maximum.</li><li>No calendar names, months, or epochs match <a href="#date" class="close"><code>dateRestrict</code></a>.</li><li>Extension calendars (those with <a href="#lines" class="close"><code>extTag</code></a> for their <a href="#date" class="close"><code>calendar</code></a>) must use <a href="#lines" class="close"><code>extTag</code></a>, not <a href="#lines" class="close"><code>stdTag</code></a>, for months.</li></ul><p>It is recommended that calendars avoid using a single tag to refer to both a month and an epoch.</p><p>An absent <a href="#date" class="close"><code>calendar</code></a> is equivalent to the calendar <a href="#GREGORIAN"><code>GREGORIAN</code></a>.</p><p>The grammar above allows for <a href="#date" class="close"><code>date</code></a>s to be preceded by various words. The meaning of these words is given as follows:</p><table><thead><tr class="header"><th style="text-align: left;">Production</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>FROM</code> <em>x</em></td><td style="text-align: left;">Lasted for multiple days, beginning on <em>x</em>.</td></tr><tr class="even"><td style="text-align: left;"><code>TO</code> <em>x</em></td><td style="text-align: left;">Lasted for multiple days, ending on <em>x</em>.</td></tr><tr class="odd"><td style="text-align: left;"><code>BET</code> <em>x</em></td><td style="text-align: left;">Exact date unknown, but no earlier than <em>x</em>.</td></tr><tr class="even"><td style="text-align: left;"><code>AND</code> <em>x</em></td><td style="text-align: left;">Exact date unknown, but no later than <em>x</em>.</td></tr><tr class="odd"><td style="text-align: left;"><code>BEF</code> <em>x</em></td><td style="text-align: left;">Exact date unknown, but no later than <em>x</em>.</td></tr><tr class="even"><td style="text-align: left;"><code>AFT</code> <em>x</em></td><td style="text-align: left;">Exact date unknown, but no earlier than <em>x</em>.</td></tr><tr class="odd"><td style="text-align: left;"><code>ABT</code> <em>x</em></td><td style="text-align: left;">Exact date unknown, but near <em>x</em>.</td></tr><tr class="even"><td style="text-align: left;"><code>CAL</code> <em>x</em></td><td style="text-align: left;"><em>x</em> is calculated from other data.</td></tr><tr class="odd"><td style="text-align: left;"><code>EST</code> <em>x</em></td><td style="text-align: left;">Exact date unknown, but near <em>x</em>; and <em>x</em> is calculated from other data.</td></tr></tbody></table><p>Known calendars and tips for handling dual dating and extension calendars are given in <a href="#A-calendars">Appendix A: Calendars and Dates</a>.</p><p><a href="#date" class="close"><code>DateValue</code></a> and <a href="#date" class="close"><code>DatePeriod</code></a> payloads may also be the empty string if no suitable form is known but a substructure (such as a <a href="#PHRASE"><code>PHRASE</code></a> or <a href="#TIME"><code>TIME</code></a>) is desired.</p><div class="note"><p>Versions 5.3 through 5.5.1 allowed phrases inside <a href="#date" class="close"><code>DateValue</code></a> payloads. Date phrases were moved to the <a href="#PHRASE" class="close"><code>PHRASE</code></a> substructure in version 7.0. A current limitation, however, is that a phrase in the <a href="#PHRASE" class="close"><code>PHRASE</code></a> substructure cannot specify a language, so if a non-default language is needed to correctly interpret the phrase two options exist:</p><ul><li><p><a href="#PHRASE" class="close"><code>PHRASE</code></a> can be used with a documented extension tag for the language, as discussed in <a href="#LANG"><code>g7:LANG</code></a>.</p></li><li><p><code>&lt;&lt;EVENT_DETAIL&gt;&gt;.SOUR.DATA.TEXT</code> can be used instead along with a <a href="#LANG" class="close"><code>LANG</code></a> substructure; this loses the connection with the date, but includes the language with a standard tag.</p></li></ul></div><div class="note"><p>As defined by the grammar above, every date must have a year. If no year is known, the entire date may be omitted.</p><div class="example"><p>The following is an appropriate way to handle a missing year</p><div class="sourceCode" id="cb22"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb22-1"><a href="#cb22-1"></a><span class="dt">2 </span><span class="fu">DATE</span></span>
 <span id="cb22-2"><a href="#cb22-2"></a><span class="dt">3 </span><span class="fu">PHRASE </span>5 January (year unknown)</span></code></pre></div></div></div><p>The URI for the <a href="#date"><code>DateValue</code></a> data type is <code>g7:type-Date</code>.</p><p>The URI for the <a href="#date" class="close"><code>DateExact</code></a> data type is <code>g7:type-Date#exact</code>.</p><p>The URI for the <a href="#date" class="close"><code>DatePeriod</code></a> data type is <code>g7:type-Date#period</code>.</p></section><section id="time" data-number="2.5"><h2 data-number="2.5"><span class="header-section-number">2.5</span> Time</h2><p>Time is represented on a 24-hour clock (for example, 23:00 rather than 11:00 PM). It may be represented either in event-local time or in Coordinated Universal Time (UTC). UTC is indicated by including a <code>Z</code> (U+005A) after the time value; event-local time is indicated by its absence. When a time is used together with a <a href="#date" class="close"><code>DateExact</code></a>, it is recommended that UTC time be used rather than event-local time.</p><div class="sourceCode" id="cb23"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb23-1"><a href="#cb23-1"></a><span class="va">Time</span>     <span class="cf">=</span>  hour <span class="st">&quot;:&quot;</span> minute <span class="cf">[</span><span class="st">&quot;:&quot;</span> second <span class="cf">[</span><span class="st">&quot;.&quot;</span> fraction<span class="cf">]]</span> <span class="cf">[</span><span class="ss">%s&quot;Z&quot;</span><span class="cf">]</span></span>
 <span id="cb23-2"><a href="#cb23-2"></a></span>
-<span id="cb23-3"><a href="#cb23-3"></a><span class="va">hour</span>     <span class="cf">=</span> digit <span class="cf">/</span> <span class="cf">(</span><span class="st">&quot;0&quot;</span> <span class="cf">/</span> <span class="st">&quot;1&quot;</span><span class="cf">)</span> digit <span class="cf">/</span> <span class="st">&quot;2&quot;</span> <span class="cf">(</span><span class="st">&quot;0&quot;</span> <span class="cf">/</span> <span class="st">&quot;1&quot;</span> <span class="cf">/</span> <span class="st">&quot;2&quot;</span> <span class="cf">/</span> <span class="st">&quot;3&quot;</span><span class="cf">)</span></span>
-<span id="cb23-4"><a href="#cb23-4"></a><span class="va">minute</span>   <span class="cf">=</span> <span class="cf">(</span><span class="st">&quot;0&quot;</span> <span class="cf">/</span> <span class="st">&quot;1&quot;</span> <span class="cf">/</span> <span class="st">&quot;2&quot;</span> <span class="cf">/</span> <span class="st">&quot;3&quot;</span> <span class="cf">/</span> <span class="st">&quot;4&quot;</span> <span class="cf">/</span> <span class="st">&quot;5&quot;</span><span class="cf">)</span> digit</span>
-<span id="cb23-5"><a href="#cb23-5"></a><span class="va">second</span>   <span class="cf">=</span> <span class="cf">(</span><span class="st">&quot;0&quot;</span> <span class="cf">/</span> <span class="st">&quot;1&quot;</span> <span class="cf">/</span> <span class="st">&quot;2&quot;</span> <span class="cf">/</span> <span class="st">&quot;3&quot;</span> <span class="cf">/</span> <span class="st">&quot;4&quot;</span> <span class="cf">/</span> <span class="st">&quot;5&quot;</span><span class="cf">)</span> digit</span>
-<span id="cb23-6"><a href="#cb23-6"></a><span class="va">fraction</span> <span class="cf">=</span> <span class="cf">1</span><span class="er">*</span>digit</span></code></pre></div><div class="note"><p>The above grammar prohibits end-of-day instant <code>24:00:00</code> and leap-seconds. It allows both <code>02:50</code> and <code>2:50</code> as the same time.</p></div><p>The URI for the <a href="#time"><code>Time</code></a> data type is <code>g7:type-Time</code>.</p></section><section id="age" data-number="2.6"><h2 data-number="2.6"><span class="header-section-number">2.6</span> Age</h2><p>Ages are represented by counts of years, months, weeks, and days.</p><div class="sourceCode" id="cb24"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb24-1"><a href="#cb24-1"></a><span class="va">Age</span>         <span class="cf">=</span> <span class="cf">[[</span>ageBound D<span class="cf">]</span> ageDuration<span class="cf">]</span></span>
+<span id="cb23-3"><a href="#cb23-3"></a><span class="va">hour</span>     <span class="cf">=</span> DIGIT <span class="cf">/</span> <span class="cf">(</span><span class="st">&quot;0&quot;</span> <span class="cf">/</span> <span class="st">&quot;1&quot;</span><span class="cf">)</span> DIGIT <span class="cf">/</span> <span class="st">&quot;2&quot;</span> <span class="cf">(</span><span class="st">&quot;0&quot;</span> <span class="cf">/</span> <span class="st">&quot;1&quot;</span> <span class="cf">/</span> <span class="st">&quot;2&quot;</span> <span class="cf">/</span> <span class="st">&quot;3&quot;</span><span class="cf">)</span></span>
+<span id="cb23-4"><a href="#cb23-4"></a><span class="va">minute</span>   <span class="cf">=</span> <span class="cf">(</span><span class="st">&quot;0&quot;</span> <span class="cf">/</span> <span class="st">&quot;1&quot;</span> <span class="cf">/</span> <span class="st">&quot;2&quot;</span> <span class="cf">/</span> <span class="st">&quot;3&quot;</span> <span class="cf">/</span> <span class="st">&quot;4&quot;</span> <span class="cf">/</span> <span class="st">&quot;5&quot;</span><span class="cf">)</span> DIGIT</span>
+<span id="cb23-5"><a href="#cb23-5"></a><span class="va">second</span>   <span class="cf">=</span> <span class="cf">(</span><span class="st">&quot;0&quot;</span> <span class="cf">/</span> <span class="st">&quot;1&quot;</span> <span class="cf">/</span> <span class="st">&quot;2&quot;</span> <span class="cf">/</span> <span class="st">&quot;3&quot;</span> <span class="cf">/</span> <span class="st">&quot;4&quot;</span> <span class="cf">/</span> <span class="st">&quot;5&quot;</span><span class="cf">)</span> DIGIT</span>
+<span id="cb23-6"><a href="#cb23-6"></a><span class="va">fraction</span> <span class="cf">=</span> <span class="cf">1</span><span class="er">*</span>DIGIT</span></code></pre></div><div class="note"><p>The above grammar prohibits end-of-day instant <code>24:00:00</code> and leap-seconds. It allows both <code>02:50</code> and <code>2:50</code> as the same time.</p></div><p>The URI for the <a href="#time"><code>Time</code></a> data type is <code>g7:type-Time</code>.</p></section><section id="age" data-number="2.6"><h2 data-number="2.6"><span class="header-section-number">2.6</span> Age</h2><p>Ages are represented by counts of years, months, weeks, and days.</p><div class="sourceCode" id="cb24"><pre class="sourceCode abnf"><code class="sourceCode abnf"><span id="cb24-1"><a href="#cb24-1"></a><span class="va">Age</span>         <span class="cf">=</span> <span class="cf">[[</span>ageBound D<span class="cf">]</span> ageDuration<span class="cf">]</span></span>
 <span id="cb24-2"><a href="#cb24-2"></a></span>
 <span id="cb24-3"><a href="#cb24-3"></a><span class="va">ageBound</span>    <span class="cf">=</span> <span class="st">&quot;&lt;&quot;</span> <span class="cf">/</span> <span class="st">&quot;&gt;&quot;</span></span>
 <span id="cb24-4"><a href="#cb24-4"></a><span class="va">ageDuration</span> <span class="cf">=</span> years <span class="cf">[</span>D months<span class="cf">]</span> <span class="cf">[</span>D weeks<span class="cf">]</span> <span class="cf">[</span>D days<span class="cf">]</span></span>
@@ -1092,7 +1092,7 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb67-8"><a href="#cb67-8"></a>     <span class="dt">+2 </span><span class="fu">LONG </span>&lt;<a href="#cb28-1">Special</a>&gt;                     <span class="ch">{1:1} </span> <span class="at">g7:LONG</span></span>
 <span id="cb67-9"><a href="#cb67-9"></a>  <span class="dt">+1 </span><span class="fu">EXID </span>&lt;<a href="#cb28-1">Special</a>&gt;                        <span class="ch">{0:M} </span> <span class="at">g7:EXID</span></span>
 <span id="cb67-10"><a href="#cb67-10"></a>     <span class="dt">+2 </span><span class="fu">TYPE </span>&lt;<a href="#cb28-1">Special</a>&gt;                     <span class="ch">{0:1} </span> <span class="at">g7:EXID-TYPE</span></span>
-<span id="cb67-11"><a href="#cb67-11"></a>  <span class="dt">+1 </span><span class="kw">&lt;&lt;NOTE_STRUCTURE&gt;&gt;</span>                    <span class="ch">{0:M}</span></span></code></pre></div><div class="deprecation"><p>Having an <a href="#EXID"><code>EXID</code></a> without an <a href="#EXID-TYPE"><code>EXID</code>.<code>TYPE</code></a> substructure is deprecated. The meaning of an <a href="#EXID" class="close"><code>EXID</code></a> depends on its <a href="#EXID-TYPE" class="close"><code>EXID</code>.<code>TYPE</code></a>. The cardinality of <a href="#EXID-TYPE" class="close"><code>EXID</code>.<code>TYPE</code></a> will be changed to <code>{1:1}</code> in version 8.0.</p></div><p>A place, which can be represented in several ways:</p><ul><li><p>The payload contains a comma-separated list of region names, ordered from smallest to largest. The specific meaning of each element is given by the <a href="#FORM"><code>FORM</code></a> substructure, or in the <a href="#HEAD-PLAC-FORM"><code>HEAD</code>.<code>PLAC</code>.<code>FORM</code></a> if there is no <a href="#FORM" class="close"><code>FORM</code></a> substructure. Elements should be left blank if they are unknown, do not apply to the location, or are too specific for the region in question.</p><div class="example"><p>A record describing births throughout Oneida county could be recorded as</p><div class="sourceCode" id="cb68"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb68-1"><a href="#cb68-1"></a><span class="dt">0 </span><span class="cf">@S1@ </span><span class="fu">SOUR</span></span>
+<span id="cb67-11"><a href="#cb67-11"></a>  <span class="dt">+1 </span><span class="kw">&lt;&lt;NOTE_STRUCTURE&gt;&gt;</span>                    <span class="ch">{0:M}</span></span></code></pre></div><div class="deprecation"><p>Having an <a href="#EXID"><code>EXID</code></a> without an <a href="#EXID-TYPE"><code>EXID</code>.<code>TYPE</code></a> substructure is deprecated. The meaning of an <a href="#EXID" class="close"><code>EXID</code></a> depends on its <a href="#EXID-TYPE" class="close"><code>EXID</code>.<code>TYPE</code></a>. The cardinality of <a href="#EXID-TYPE" class="close"><code>EXID</code>.<code>TYPE</code></a> will be changed to <code>{1:1}</code> in version 8.0.</p></div><p>A place, which can be represented in several ways:</p><ul><li><p>The payload contains a comma-separated list of region names, ordered from smallest to largest. The specific meaning of each element is given by the <a href="#FORM"><code>FORM</code></a> substructure, or in the <a href="#HEAD-PLAC-FORM"><code>HEAD</code>.<code>PLAC</code>.<code>FORM</code></a> if there is no <a href="#FORM" class="close"><code>FORM</code></a> substructure. If neither <a href="#FORM" class="close"><code>FORM</code></a> exists, the meaning of the elements are not defined in this specification beyond being names of jurisdictions of some kind, ordered from smallest to largest.</p><p>Elements should be left blank if they are unknown, do not apply to the location, or are too specific for the region in question.</p><div class="example"><p>A record describing births throughout Oneida county could be recorded as</p><div class="sourceCode" id="cb68"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb68-1"><a href="#cb68-1"></a><span class="dt">0 </span><span class="cf">@S1@ </span><span class="fu">SOUR</span></span>
 <span id="cb68-2"><a href="#cb68-2"></a><span class="dt">1 </span><span class="fu">DATA</span></span>
 <span id="cb68-3"><a href="#cb68-3"></a><span class="dt">2 </span><span class="fu">EVEN </span>BIRT</span>
 <span id="cb68-4"><a href="#cb68-4"></a><span class="dt">3 </span><span class="fu">PLAC </span>, Oneida, Idaho, USA</span>
@@ -1117,7 +1117,7 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb71-2"><a href="#cb71-2"></a><span class="dt">2 </span><span class="fu">DATE </span>2 OCT 1937</span></code></pre></div></div><div class="note"><p>Version 5.4 (1995) introduced the “event did occur” meaning of event.<code>DATE</code>, so it is now well-established in applications and files. However, it is common for users to enter a date range with no end without intending to indicate that the event occurred. For example, pre 7.0 files sometimes used</p><div class="sourceCode" id="cb72"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb72-1"><a href="#cb72-1"></a><span class="dt">1 </span><span class="fu">NATU</span></span>
 <span id="cb72-2"><a href="#cb72-2"></a><span class="dt">2 </span><span class="fu">DATE </span>AFT 1800</span></code></pre></div><p>to mean what 7.0 encodes as</p><div class="sourceCode" id="cb73"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb73-1"><a href="#cb73-1"></a><span class="dt">1 </span><span class="fu">NOT </span>NATU</span>
 <span id="cb73-2"><a href="#cb73-2"></a><span class="dt">2 </span><span class="fu">DATE </span>TO 1800</span></code></pre></div><p>without intending to imply that <a href="#NATU"><code>NATU</code></a> ever did actually occur. Because this is a “sometimes used” rather than a “formally means” situation, it is likely that data using 5.x “after meaning not before” <em>de facto</em> pattern will be transferred as-is into 7.0 and persist in files for the foreseeable future.</p></div></li><li><p>There is a <a href="#PLAC"><code>PLAC</code></a> substructure</p><div class="example"><div class="sourceCode" id="cb74"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb74-1"><a href="#cb74-1"></a><span class="dt">1 </span><span class="fu">DEAT</span></span>
-<span id="cb74-2"><a href="#cb74-2"></a><span class="dt">2 </span><span class="fu">PLAC </span>Cove, Cache, Utah</span></code></pre></div></div></li><li><p>The event has a payload. A special payload <code>Y</code> can be used with some event types to indicate that the event is known to have occurred without providing any additional information about it.</p><div class="example"><div class="sourceCode" id="cb75"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb75-1"><a href="#cb75-1"></a><span class="dt">1 </span><span class="fu">DEAT </span>Y</span></code></pre></div></div></li></ul><p>If none of the above are true, the structure should be seen as a place for inconclusive research notes about the possibility of the event. An assertion that an event did not occur should be encoded using the <a href="#NO"><code>NO</code></a> structure.</p><section id="individual-events" data-number="3.3.1.1"><h4 data-number="3.3.1.1"><span class="header-section-number">3.3.1.1</span> Individual Events</h4><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>ADOP</code></td><td>adoption<br /><a href="#ADOP"><code>g7:ADOP</code></a></td><td>Creation of a legally approved child-parent relationship that does not exist biologically.</td></tr><tr class="even"><td><code>BAPM</code></td><td>baptism<br /><a href="#BAPM"><code>g7:BAPM</code></a></td><td>Baptism, performed in infancy or later. (See also <a href="#latter-day-saint-ordinances"><code>BAPL</code></a> and <code>CHR</code>.)</td></tr><tr class="odd"><td><code>BARM</code></td><td>Bar Mitzvah<br /><a href="#BARM"><code>g7:BARM</code></a></td><td>The ceremonial event held when a Jewish boy reaches age 13.</td></tr><tr class="even"><td><code>BASM</code></td><td>Bas Mitzvah<br /><a href="#BASM"><code>g7:BASM</code></a></td><td>The ceremonial event held when a Jewish girl reaches age 13, also known as “Bat Mitzvah.”</td></tr><tr class="odd"><td><code>BIRT</code></td><td>birth<br /><a href="#BIRT"><code>g7:BIRT</code></a></td><td>Entering into life.</td></tr><tr class="even"><td><code>BLES</code></td><td>blessing<br /><a href="#BLES"><code>g7:BLES</code></a></td><td>Bestowing divine care or intercession. Sometimes given in connection with a naming ceremony.</td></tr><tr class="odd"><td><code>BURI</code></td><td>depositing remains<br /><a href="#BURI"><code>g7:BURI</code></a></td><td>Depositing the mortal remains of a deceased person.</td></tr><tr class="even"><td><code>CENS</code></td><td>census<br /><a href="#INDI-CENS"><code>g7:INDI-CENS</code></a></td><td>Periodic count of the population for a designated locality, such as a national or state census.</td></tr><tr class="odd"><td><code>CHR</code></td><td>christening<br /><a href="#CHR"><code>g7:CHR</code></a></td><td>Baptism or naming events for a child.</td></tr><tr class="even"><td><code>CHRA</code></td><td>adult christening<br /><a href="#CHRA"><code>g7:CHRA</code></a></td><td>Baptism or naming events for an adult person.</td></tr><tr class="odd"><td><code>CONF</code></td><td>confirmation<br /><a href="#CONF"><code>g7:CONF</code></a></td><td>Conferring full church membership.</td></tr><tr class="even"><td><code>CREM</code></td><td>cremation<br /><a href="#CREM"><code>g7:CREM</code></a></td><td>The act of reducing a dead body to ashes by fire.</td></tr><tr class="odd"><td><code>DEAT</code></td><td>death<br /><a href="#DEAT"><code>g7:DEAT</code></a></td><td>Mortal life terminates.</td></tr><tr class="even"><td><code>EMIG</code></td><td>emigration<br /><a href="#EMIG"><code>g7:EMIG</code></a></td><td>Leaving one’s homeland with the intent of residing elsewhere.</td></tr><tr class="odd"><td><code>FCOM</code></td><td>first communion<br /><a href="#FCOM"><code>g7:FCOM</code></a></td><td>The first act of sharing in the Lord’s supper as part of church worship.</td></tr><tr class="even"><td><code>GRAD</code></td><td>graduation<br /><a href="#GRAD"><code>g7:GRAD</code></a></td><td>Awarding educational diplomas or degrees to individuals.</td></tr><tr class="odd"><td><code>IMMI</code></td><td>immigration<br /><a href="#IMMI"><code>g7:IMMI</code></a></td><td>Entering into a new locality with the intent of residing there.</td></tr><tr class="even"><td><code>NATU</code></td><td>naturalization<br /><a href="#NATU"><code>g7:NATU</code></a></td><td>Obtaining citizenship.</td></tr><tr class="odd"><td><code>ORDN</code></td><td>ordination<br /><a href="#ORDN"><code>g7:ORDN</code></a></td><td>Receiving authority to act in religious matters.</td></tr><tr class="even"><td><code>PROB</code></td><td>probate<br /><a href="#PROB"><code>g7:PROB</code></a></td><td>Judicial determination of the validity of a will. It may indicate several related court activities over several dates.</td></tr><tr class="odd"><td><code>RETI</code></td><td>retirement<br /><a href="#RETI"><code>g7:RETI</code></a></td><td>Exiting an occupational relationship with an employer after a qualifying time period.</td></tr><tr class="even"><td><code>WILL</code></td><td>will<br /><a href="#WILL"><code>g7:WILL</code></a></td><td>A legal document treated as an event, by which a person disposes of his or her estate. It takes effect after death. The event date is the date the will was signed while the person was alive. (See also <code>PROB</code>)</td></tr></tbody></table><p>In addition, <a href="#INDI-EVEN"><code>INDI</code>.<code>EVEN</code></a> is a structure for a generic individual event. It must have a <a href="#TYPE"><code>TYPE</code></a> substructure to define what kind of event is being provided.</p></section><section id="family-events" data-number="3.3.1.2"><h4 data-number="3.3.1.2"><span class="header-section-number">3.3.1.2</span> Family Events</h4><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>ANUL</code></td><td>annulment<br /><a href="#ANUL"><code>g7:ANUL</code></a></td><td>Declaring a marriage void from the beginning (never existed).</td></tr><tr class="even"><td><code>CENS</code></td><td>census<br /><a href="#FAM-CENS"><code>g7:FAM-CENS</code></a></td><td>Periodic count of the population for a designated locality, such as a national or state census.</td></tr><tr class="odd"><td><code>DIV</code></td><td>divorce<br /><a href="#DIV"><code>g7:DIV</code></a></td><td>Dissolving a marriage through civil action.</td></tr><tr class="even"><td><code>DIVF</code></td><td>divorce filed<br /><a href="#DIVF"><code>g7:DIVF</code></a></td><td>Filing for a divorce by a spouse.</td></tr><tr class="odd"><td><code>ENGA</code></td><td>engagement<br /><a href="#ENGA"><code>g7:ENGA</code></a></td><td>Recording or announcing an agreement between 2 people to become married.</td></tr><tr class="even"><td><code>MARB</code></td><td>marriage bann<br /><a href="#MARB"><code>g7:MARB</code></a></td><td>Official public notice given that 2 people intend to marry.</td></tr><tr class="odd"><td><code>MARC</code></td><td>marriage contract<br /><a href="#MARC"><code>g7:MARC</code></a></td><td>Recording a formal agreement of marriage, including the prenuptial agreement in which marriage partners reach agreement about the property rights of 1 or both, securing property to their children.</td></tr><tr class="even"><td><code>MARL</code></td><td>marriage license<br /><a href="#MARL"><code>g7:MARL</code></a></td><td>Obtaining a legal license to marry.</td></tr><tr class="odd"><td><code>MARR</code></td><td>marriage<br /><a href="#MARR"><code>g7:MARR</code></a></td><td>A legal, common-law, or customary event such as a wedding or marriage ceremony that joins 2 partners to create or extend a family unit.</td></tr><tr class="even"><td><code>MARS</code></td><td>marriage settlement<br /><a href="#MARS"><code>g7:MARS</code></a></td><td>Creating an agreement between 2 people contemplating marriage, at which time they agree to release or modify property rights that would otherwise arise from the marriage.</td></tr></tbody></table><p>In addition, <a href="#FAM-EVEN"><code>FAM</code>.<code>EVEN</code></a> is a structure for a generic family event. It must have a <a href="#TYPE" class="close"><code>TYPE</code></a> substructure to define what kind of event is being provided.</p></section></section><section id="attributes" data-number="3.3.2"><h3 data-number="3.3.2"><span class="header-section-number">3.3.2</span> Attributes</h3><p>Unlike events, the presence of an attribute is sufficient to assert the attribute applied to the individual, regardless of the attribute’s substructures and payload.</p><section id="individual-attributes" data-number="3.3.2.1"><h4 data-number="3.3.2.1"><span class="header-section-number">3.3.2.1</span> Individual Attributes</h4><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>CAST</code></td><td>caste<br /><a href="#CAST"><code>g7:CAST</code></a></td><td>The name of an individual’s rank or status in society which is sometimes based on racial or religious differences, or differences in wealth, inherited rank, profession, or occupation.</td></tr><tr class="even"><td><code>DSCR</code></td><td>physical description<br /><a href="#DSCR"><code>g7:DSCR</code></a></td><td>The physical characteristics of a person.</td></tr><tr class="odd"><td><code>EDUC</code></td><td>education<br /><a href="#EDUC"><code>g7:EDUC</code></a></td><td>Indicator of a level of education attained.</td></tr><tr class="even"><td><code>IDNO</code></td><td>identifying number<br /><a href="#IDNO"><code>g7:IDNO</code></a></td><td>A number or other string assigned to identify a person within some significant external system. It must have a <code>TYPE</code> substructure to define what kind of identification number is being provided.</td></tr><tr class="odd"><td><code>NATI</code></td><td>nationality<br /><a href="#NATI"><code>g7:NATI</code></a></td><td>An individual’s national heritage or origin, or other folk, house, kindred, lineage, or tribal interest.</td></tr><tr class="even"><td><code>NCHI</code></td><td>number of children<br /><a href="#INDI-NCHI"><code>g7:INDI-NCHI</code></a></td><td>The number of children that this person is known to be the parent of (all marriages).</td></tr><tr class="odd"><td><code>NMR</code></td><td>number of marriages<br /><a href="#NMR"><code>g7:NMR</code></a></td><td>The number of times this person has participated in a family as a spouse or parent.</td></tr><tr class="even"><td><code>OCCU</code></td><td>occupation<br /><a href="#OCCU"><code>g7:OCCU</code></a></td><td>The type of work or profession of an individual.</td></tr><tr class="odd"><td><code>PROP</code></td><td>property<br /><a href="#PROP"><code>g7:PROP</code></a></td><td>Pertaining to possessions such as real estate or other property of interest.</td></tr><tr class="even"><td><code>RELI</code></td><td>religion<br /><a href="#INDI-RELI"><code>g7:INDI-RELI</code></a></td><td>A religious denomination to which a person is affiliated or for which a record applies.</td></tr><tr class="odd"><td><code>RESI</code></td><td>residence<br /><a href="#INDI-RESI"><code>g7:INDI-RESI</code></a></td><td>An address or place of residence where an individual resided.</td></tr><tr class="even"><td><code>SSN</code></td><td>social security number<br /><a href="#SSN"><code>g7:SSN</code></a></td><td>A number assigned by the United States Social Security Administration, used for tax identification purposes. It is a type of <code>IDNO</code>.</td></tr><tr class="odd"><td><code>TITL</code></td><td>title<br /><a href="#INDI-TITL"><code>g7:INDI-TITL</code></a></td><td>A formal designation used by an individual in connection with positions of royalty or other social status, such as Grand Duke.</td></tr></tbody></table><p>In addition, <a href="#INDI-FACT"><code>INDI</code>.<code>FACT</code></a> is a structure for a generic individual attribute. It must have a <a href="#TYPE"><code>TYPE</code></a> substructure to define what kind of attribute is being provided.</p></section><section id="family-attributes" data-number="3.3.2.2"><h4 data-number="3.3.2.2"><span class="header-section-number">3.3.2.2</span> Family Attributes</h4><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>NCHI</code></td><td>number of children<br /><a href="#FAM-NCHI"><code>g7:FAM-NCHI</code></a></td><td>The number of children that belong to this family.</td></tr><tr class="even"><td><code>RESI</code></td><td>residence<br /><a href="#FAM-RESI"><code>g7:FAM-RESI</code></a></td><td>An address or place of residence where a family resided.</td></tr></tbody></table><p>In addition, <a href="#FAM-FACT"><code>FAM</code>.<code>FACT</code></a> is a structure for a generic family attribute. It must have a <a href="#TYPE" class="close"><code>TYPE</code></a> substructure to define what kind of attribute is being provided.</p></section></section><section id="latter-day-saint-ordinances" data-number="3.3.3"><h3 data-number="3.3.3"><span class="header-section-number">3.3.3</span> Latter-day Saint Ordinances</h3><p>The structures describing ordinances performed by The Church of Jesus Christ of Latter-day Saints are unlike regular events in that they might either be performed during life or by proxy on the behalf of a deceased individual.</p><p>Proxy ordinances on behalf of deceased persons were once requested and officially recorded using an earlier version of GEDCOM. This is no longer the case, but when it was the case the following principles held:</p><ul><li><a href="#PLAC"><code>PLAC</code></a> was used only for ordinances that were performed by the recipient in life.</li><li><a href="#TEMP"><code>TEMP</code></a> was used with all <a href="#ENDL"><code>ENDL</code></a>, <a href="#SLGC"><code>SLGC</code></a>, and <a href="#SLGS"><code>SLGS</code></a>, but only with posthumous proxy <a href="#BAPL"><code>BAPL</code></a> and <a href="#CONL"><code>CONL</code></a>.</li></ul><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>BAPL</code></td><td>baptism<br /><a href="#BAPL" class="close"><code>g7:BAPL</code></a></td><td>The event of baptism performed at age 8 or later by priesthood authority of The Church of Jesus Christ of Latter-day Saints. (See also <a href="#individual-events"><code>BAPM</code></a>)</td></tr><tr class="even"><td><code>CONL</code></td><td>confirmation<br /><a href="#CONL" class="close"><code>g7:CONL</code></a></td><td>The religious event by which a person receives membership in The Church of Jesus Christ of Latter-day Saints. (See also <a href="#individual-events"><code>CONF</code></a>)</td></tr><tr class="odd"><td><code>INIL</code></td><td>initiatory<br /><a href="#INIL"><code>g7:INIL</code></a></td><td>A religious event where an initiatory ordinance for an individual was performed by priesthood authority in a temple of The Church of Jesus Christ of Latter-day Saints.</td></tr><tr class="even"><td><code>ENDL</code></td><td>endowment<br /><a href="#ENDL" class="close"><code>g7:ENDL</code></a></td><td>A religious event where an endowment ordinance for an individual was performed by priesthood authority in a temple of The Church of Jesus Christ of Latter-day Saints.</td></tr><tr class="odd"><td><code>SLGC</code></td><td>sealing child<br /><a href="#SLGC" class="close"><code>g7:SLGC</code></a></td><td>A religious event pertaining to the sealing of a child to his or her parents in a temple ceremony of The Church of Jesus Christ of Latter-day Saints.</td></tr><tr class="even"><td><code>SLGS</code></td><td>sealing spouse<br /><a href="#SLGS" class="close"><code>g7:SLGS</code></a></td><td>A religious event pertaining to the sealing of a husband and wife in a temple ceremony of The Church of Jesus Christ of Latter-day Saints. (See also <a href="#family-events"><code>MARR</code></a>)</td></tr></tbody></table></section><section id="structure-types" data-number="3.3.4"><h3 data-number="3.3.4"><span class="header-section-number">3.3.4</span> Structure types</h3><p>Structure types are listed in this section alphabetically by tag. When the same tag is used for different structure types in different contexts, they may be distinguished by their URI.</p><section id="ABBR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ABBR</code> (Abbreviation) <code class="uri">g7:ABBR</code></h4><p>A short name of a title, description, or name used for sorting, filing, and retrieving records.</p></section><section id="ADDR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADDR</code> (Address) <code class="uri">g7:ADDR</code></h4><p>The location of, or most relevant to, the subject of the superstructure. See <a href="#ADDRESS_STRUCTURE"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></section><section id="ADOP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADOP</code> (Adoption) <code class="uri">g7:ADOP</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="FAMC-ADOP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADOP</code> (Adoption) <code class="uri">g7:FAMC-ADOP</code></h4><p>An enumerated value from set <a href="#enumset-ADOP"><code>g7:enumset-ADOP</code></a> indicating which parent(s) in the family adopted this individual.</p></section><section id="ADR1" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADR1</code> (Address Line 1) <code class="uri">g7:ADR1</code></h4><p>The first line of the address, used for indexing. This structure’s payload should be a single line of text equal to the first line of the corresponding <a href="#ADDR" class="close"><code>ADDR</code></a>. See <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p><div class="deprecation"><p><a href="#ADR1" class="close"><code>ADR1</code></a> should not be added to new files; see <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></div></section><section id="ADR2" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADR2</code> (Address Line 2) <code class="uri">g7:ADR2</code></h4><p>The second line of the address, used for indexing. This structure’s payload should be a single line of text equal to the second line of the corresponding <a href="#ADDR" class="close"><code>ADDR</code></a>. See <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p><div class="deprecation"><p><a href="#ADR2" class="close"><code>ADR2</code></a> should not be added to new files; see <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></div></section><section id="ADR3" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADR3</code> (Address Line 3) <code class="uri">g7:ADR3</code></h4><p>The third line of the address, used for indexing. This structure’s payload should be a single line of text equal to the third line of the corresponding <a href="#ADDR" class="close"><code>ADDR</code></a>. See <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p><div class="deprecation"><p><a href="#ADR3" class="close"><code>ADR3</code></a> should not be added to new files; see <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></div></section><section id="AGE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>AGE</code> (Age at event) <code class="uri">g7:AGE</code></h4><p>The age of the individual at the time an event occurred, or the age listed in the document.</p></section><section id="AGNC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>AGNC</code> (Responsible agency) <code class="uri">g7:AGNC</code></h4><p>The organization, institution, corporation, person, or other entity that has responsibility for the associated context. Examples are an employer of a person of an associated occupation, or a church that administered rites or events, or an organization responsible for creating or archiving records.</p></section><section id="ALIA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ALIA</code> (Alias) <code class="uri">g7:ALIA</code></h4><p>A single individual may have facts distributed across multiple individual records, connected by <a href="#ALIA" class="close"><code>ALIA</code></a> pointers (named after “alias” in the computing sense, not the pseudonym sense).</p><div class="note"><p>This specification does not define how to connect <code>INDI</code> records with <a href="#ALIA" class="close"><code>ALIA</code></a>. Some systems organize <a href="#ALIA" class="close"><code>ALIA</code></a> pointers to create a tree structure, with the root <code>INDI</code> record containing the composite view of all facts in the leaf <code>INDI</code> records. Others distribute events and attributes between <code>INDI</code> records mutually linked by symmetric pairs of <a href="#ALIA" class="close"><code>ALIA</code></a> pointers. A future version of this specification may adjust the definition of <a href="#ALIA" class="close"><code>ALIA</code></a>.</p></div></section><section id="ANCI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ANCI</code> (Ancestor interest) <code class="uri">g7:ANCI</code></h4><p>Indicates an interest in additional research for ancestors of this individual. (See also <a href="#DESI"><code>DESI</code></a>).</p></section><section id="ANUL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ANUL</code> (Annulment) <code class="uri">g7:ANUL</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="ASSO" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ASSO</code> (Associates) <code class="uri">g7:ASSO</code></h4><p>A pointer to an associated individual. See <a href="#ASSOCIATION_STRUCTURE"><code>ASSOCIATION_STRUCTURE</code></a> for more details.</p></section><section id="AUTH" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>AUTH</code> (Author) <code class="uri">g7:AUTH</code></h4><p>The person, agency, or entity who created the record. For a published work, this could be the author, compiler, transcriber, abstractor, or editor. For an unpublished source, this may be an individual, a government agency, church organization, or private organization.</p></section><section id="BAPL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BAPL</code> (Baptism, Latter-Day Saint) <code class="uri">g7:BAPL</code></h4><p>A <a href="#latter-day-saint-ordinances">Latter-Day Saint Ordinance</a>. See also <a href="#LDS_INDIVIDUAL_ORDINANCE"><code>LDS_INDIVIDUAL_ORDINANCE</code></a>.</p></section><section id="BAPM" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BAPM</code> (Baptism) <code class="uri">g7:BAPM</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BARM" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BARM</code> (Bar Mitzvah) <code class="uri">g7:BARM</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BASM" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BASM</code> (Bas Mitzvah) <code class="uri">g7:BASM</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BIRT" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BIRT</code> (Birth) <code class="uri">g7:BIRT</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BLES" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BLES</code> (Blessing) <code class="uri">g7:BLES</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BURI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BURI</code> (Depositing remains) <code class="uri">g7:BURI</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p><p>Although defined as any depositing of remains since it was introduced in the first version of GEDCOM, this tag is a shortened form of the English word “burial” and has been interpreted to mean “depositing of remains by burial” by some applications and users. In the absence of a clarifying <a href="#TYPE"><code>TYPE</code></a> substructure it is likely, but not guaranteed, that a <a href="#BURI" class="close"><code>BURI</code></a> structure refers to a burial rather than another form of depositing remains.</p></section><section id="CALN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CALN</code> (Call number) <code class="uri">g7:CALN</code></h4><p>An identification or reference description used to file and retrieve items from the holdings of a repository. Despite the word “number” in the name, may contain any character, not just digits.</p></section><section id="CAST" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CAST</code> (Caste) <code class="uri">g7:CAST</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="CAUS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CAUS</code> (Cause) <code class="uri">g7:CAUS</code></h4><p>The reasons which precipitated an event. It is often used subordinate to a death event to show cause of death, such as might be listed on a death certificate.</p></section><section id="FAM-CENS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CENS</code> (Census) <code class="uri">g7:FAM-CENS</code></h4><p>An <a href="#family-events">Family Event</a>.</p></section><section id="INDI-CENS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CENS</code> (Census) <code class="uri">g7:INDI-CENS</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CHAN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CHAN</code> (Change) <code class="uri">g7:CHAN</code></h4><p>The most recent change to the superstructure. This is metadata about the structure itself, not data about its subject. See <a href="#CHANGE_DATE"><code>CHANGE_DATE</code></a> for more details.</p></section><section id="CHIL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CHIL</code> (Child) <code class="uri">g7:CHIL</code></h4><p>The child in a family, whether biological, adopted, foster, sealed, or other relationship.</p></section><section id="CHRA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CHRA</code> (Christening, adult) <code class="uri">g7:CHRA</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CHR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CHR</code> (Christening) <code class="uri">g7:CHR</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CITY" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CITY</code> (City) <code class="uri">g7:CITY</code></h4><p>The name of the city used in the address. See <a href="#ADDRESS_STRUCTURE"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></section><section id="CONF" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CONF</code> (Confirmation) <code class="uri">g7:CONF</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CONL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CONL</code> (Confirmation, Latter-Day Saint) <code class="uri">g7:CONL</code></h4><p>A <a href="#latter-day-saint-ordinances">Latter-Day Saint Ordinance</a>. See also <a href="#LDS_INDIVIDUAL_ORDINANCE"><code>LDS_INDIVIDUAL_ORDINANCE</code></a>.</p></section><section id="CONT" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CONT</code> (Continued) <code class="uri">g7:CONT</code></h4><p>A pseudo-structure to indicate a line break. The <a href="#CONT" class="close"><code>CONT</code></a> tag is generated during serialization and is never present in parsed datasets. See <a href="#lines">Lines</a> for more details.</p></section><section id="COPR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>COPR</code> (Copyright) <code class="uri">g7:COPR</code></h4><p>A copyright statement, as appropriate for the copyright laws applicable to this data.</p></section><section id="CORP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CORP</code> (Corporate name) <code class="uri">g7:CORP</code></h4><p>The name of the business, corporation, or person that produced or commissioned the product.</p></section><section id="CREA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CREA</code> (Creation) <code class="uri">g7:CREA</code></h4><p>The initial creation of the superstructure. This is metadata about the structure itself, not data about its subject. See <a href="#CREATION_DATE"><code>CREATION_DATE</code></a> for more details.</p></section><section id="CREM" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CREM</code> (Cremation) <code class="uri">g7:CREM</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CROP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CROP</code> (Crop) <code class="uri">g7:CROP</code></h4><p>A subregion of an image to display. It is only valid when the superstructure links to a <a href="#MULTIMEDIA_RECORD"><code>MULTIMEDIA_RECORD</code></a> with at least 1 <a href="#FILE"><code>FILE</code></a> substructure that refers to an external file with a defined pixel unit.</p><p><a href="#LEFT"><code>LEFT</code></a> and <a href="#TOP"><code>TOP</code></a> indicate the top-left corner of the region to display. <a href="#WIDTH"><code>WIDTH</code></a> and <a href="#HEIGHT"><code>HEIGHT</code></a> indicate how many pixels wide and tall the region to display is. If omitted, <a href="#LEFT" class="close"><code>LEFT</code></a> and <a href="#TOP" class="close"><code>TOP</code></a> each default to 0; <a href="#WIDTH" class="close"><code>WIDTH</code></a> defaults to the image width minus <a href="#LEFT" class="close"><code>LEFT</code></a>; and <a href="#HEIGHT" class="close"><code>HEIGHT</code></a> defaults to the image height minus <a href="#TOP" class="close"><code>TOP</code></a>.</p><p>If the superstructure links to a <a href="#MULTIMEDIA_RECORD" class="close"><code>MULTIMEDIA_RECORD</code></a> that includes multiple <a href="#FILE" class="close"><code>FILE</code></a> substructures, the <a href="#CROP" class="close"><code>CROP</code></a> applies to the first <a href="#FILE" class="close"><code>FILE</code></a> to which it can apply, namely the first external file with a defined pixel unit.</p><p>It is recommended that <a href="#CROP" class="close"><code>CROP</code></a> be used only with a single-FILE <a href="#MULTIMEDIA_RECORD" class="close"><code>MULTIMEDIA_RECORD</code></a>.</p><p>The following are errors:</p><ul><li><a href="#LEFT" class="close"><code>LEFT</code></a> or <a href="#LEFT" class="close"><code>LEFT</code></a> + <a href="#WIDTH" class="close"><code>WIDTH</code></a> exceed the image width.</li><li><a href="#TOP" class="close"><code>TOP</code></a> or <a href="#TOP" class="close"><code>TOP</code></a> + <a href="#HEIGHT" class="close"><code>HEIGHT</code></a> exceed the image height.</li><li><a href="#CROP" class="close"><code>CROP</code></a> applied to a non-image or image without a defined pixel unit.</li></ul></section><section id="CTRY" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CTRY</code> (Country) <code class="uri">g7:CTRY</code></h4><p>The name of the country that pertains to the associated address. See <a href="#ADDRESS_STRUCTURE"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></section><section id="DATA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATA</code> (Data) <code class="uri">g7:DATA</code></h4><p>A structure with no payload used to distinguish a description of something from metadata about it. For example, <a href="#SOUR"><code>SOUR</code></a> and its other substructures describe a source itself, while <a href="#SOUR-DATA" class="close"><code>SOUR</code>.<code>DATA</code></a> describes the content of the source.</p></section><section id="SOUR-DATA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATA</code> (Data) <code class="uri">g7:SOUR-DATA</code></h4><p>See <a href="#DATA" class="close"><code>g7:DATA</code></a>.</p></section><section id="HEAD-SOUR-DATA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATA</code> (Data) <code class="uri">g7:HEAD-SOUR-DATA</code></h4><p>The electronic data source or digital repository from which this dataset was exported. The payload is the name of that source, with substructures providing additional details about the source (not the export).</p></section><section id="DATE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:DATE</code></h4><p>The principal date of the subject of the superstructure. The payload is a <a href="#date"><code>DateValue</code></a>.</p><p>See <a href="#DATE_VALUE"><code>DATE_VALUE</code></a> for more details.</p></section><section id="DATE-exact" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:DATE-exact</code></h4><p>The principal date of the subject of the superstructure. The payload is a <a href="#date" class="close"><code>DateExact</code></a>.</p></section><section id="HEAD-DATE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:HEAD-DATE</code></h4><p>The <a href="#date" class="close"><code>DateExact</code></a> that this document was created.</p></section><section id="NO-DATE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:NO-DATE</code></h4><p>The <a href="#date" class="close"><code>DatePeriod</code></a> during which the event did not occur or the attribute did not apply.</p></section><section id="DATA-EVEN-DATE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:DATA-EVEN-DATE</code></h4><p>The <a href="#date" class="close"><code>DatePeriod</code></a> covered by the entire source; the period during which this source recorded events.</p></section><section id="DEAT" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DEAT</code> (Death) <code class="uri">g7:DEAT</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="DESI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DESI</code> (Descendant Interest) <code class="uri">g7:DESI</code></h4><p>Indicates an interest in research to identify additional descendants of this individual. See also <a href="#ANCI"><code>ANCI</code></a>.</p></section><section id="DEST" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DEST</code> (Destination) <code class="uri">g7:DEST</code></h4><p>An identifier for the system expected to receive this document. See <a href="#HEAD-SOUR"><code>HEAD</code>.<code>SOUR</code></a> for guidance on choosing identifiers.</p></section><section id="DIVF" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DIVF</code> (Divorce filing) <code class="uri">g7:DIVF</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="DIV" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DIV</code> (Divorce) <code class="uri">g7:DIV</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="DSCR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DSCR</code> (Description) <code class="uri">g7:DSCR</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="EDUC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EDUC</code> (Education) <code class="uri">g7:EDUC</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE" class="close"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="EMAIL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EMAIL</code> (Email) <code class="uri">g7:EMAIL</code></h4><p>An electronic mail address, as defined by any relevant standard such as <a href="https://www.rfc-editor.org/info/rfc3696">RFC 3696</a>, <a href="https://www.rfc-editor.org/info/rfc5321">RFC 5321</a>, or <a href="https://www.rfc-editor.org/info/rfc5322">RFC 5322</a>.</p><p>If an invalid email address is present upon import, it should be preserved as-is on export.</p><div class="note"><p>The version 5.5.1 specification contained a typo where this tag was sometimes written <code>EMAI</code> and sometimes written <a href="#EMAIL" class="close"><code>EMAIL</code></a>. <a href="#EMAIL" class="close"><code>EMAIL</code></a> should be used in version 7.0 and later.</p></div></section><section id="EMIG" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EMIG</code> (Emigration) <code class="uri">g7:EMIG</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="ENDL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ENDL</code> (Endowment, Latter-Day Saint) <code class="uri">g7:ENDL</code></h4><p>A <a href="#latter-day-saint-ordinances">Latter-Day Saint Ordinance</a>. See also <a href="#LDS_INDIVIDUAL_ORDINANCE"><code>LDS_INDIVIDUAL_ORDINANCE</code></a>.</p></section><section id="ENGA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ENGA</code> (Engagement) <code class="uri">g7:ENGA</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="FAM-EVEN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EVEN</code> (Event) <code class="uri">g7:FAM-EVEN</code></h4><p>See <a href="#INDI-EVEN" class="close"><code>g7:INDI-EVEN</code></a>.</p></section><section id="INDI-EVEN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EVEN</code> (Event) <code class="uri">g7:INDI-EVEN</code></h4><p>An event: a noteworthy happening related to an individual or family. If a specific event type exists, it should be used instead of a generic <code>EVEN</code> structure. Each <code>EVEN</code> must be classified by a subordinate use of the <a href="#TYPE"><code>TYPE</code></a> tag and may be further described in the structure’s payload.</p><div class="example"><p>A person that signed a lease for land dated October 2, 1837 and a lease for mining equipment dated November 4, 1837 would be written as:</p><div class="sourceCode" id="cb76"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb76-1"><a href="#cb76-1"></a><span class="dt">0 </span><span class="cf">@I1@ </span><span class="fu">INDI</span></span>
+<span id="cb74-2"><a href="#cb74-2"></a><span class="dt">2 </span><span class="fu">PLAC </span>Cove, Cache, Utah</span></code></pre></div></div></li><li><p>The event has a payload. A special payload <code>Y</code> can be used with some event types to indicate that the event is known to have occurred without providing any additional information about it.</p><div class="example"><div class="sourceCode" id="cb75"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb75-1"><a href="#cb75-1"></a><span class="dt">1 </span><span class="fu">DEAT </span>Y</span></code></pre></div></div></li></ul><p>If none of the above are true, the structure should be seen as a place for inconclusive research notes about the possibility of the event. An assertion that an event did not occur should be encoded using the <a href="#NO"><code>NO</code></a> structure.</p><section id="individual-events" data-number="3.3.1.1"><h4 data-number="3.3.1.1"><span class="header-section-number">3.3.1.1</span> Individual Events</h4><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>ADOP</code></td><td>adoption<br /><a href="#ADOP"><code>g7:ADOP</code></a></td><td>Creation of a legally approved child-parent relationship that does not exist biologically.</td></tr><tr class="even"><td><code>BAPM</code></td><td>baptism<br /><a href="#BAPM"><code>g7:BAPM</code></a></td><td>Baptism, performed in infancy or later. (See also <a href="#latter-day-saint-ordinances"><code>BAPL</code></a> and <code>CHR</code>.)</td></tr><tr class="odd"><td><code>BARM</code></td><td>Bar Mitzvah<br /><a href="#BARM"><code>g7:BARM</code></a></td><td>The ceremonial event held when a Jewish boy reaches age 13.</td></tr><tr class="even"><td><code>BASM</code></td><td>Bas Mitzvah<br /><a href="#BASM"><code>g7:BASM</code></a></td><td>The ceremonial event held when a Jewish girl reaches age 13, also known as “Bat Mitzvah.”</td></tr><tr class="odd"><td><code>BIRT</code></td><td>birth<br /><a href="#BIRT"><code>g7:BIRT</code></a></td><td>Entering into life.</td></tr><tr class="even"><td><code>BLES</code></td><td>blessing<br /><a href="#BLES"><code>g7:BLES</code></a></td><td>Bestowing divine care or intercession. Sometimes given in connection with a naming ceremony.</td></tr><tr class="odd"><td><code>BURI</code></td><td>depositing remains<br /><a href="#BURI"><code>g7:BURI</code></a></td><td>Depositing the mortal remains of a deceased person.</td></tr><tr class="even"><td><code>CENS</code></td><td>census<br /><a href="#INDI-CENS"><code>g7:INDI-CENS</code></a></td><td>Periodic count of the population for a designated locality, such as a national or state census.</td></tr><tr class="odd"><td><code>CHR</code></td><td>christening<br /><a href="#CHR"><code>g7:CHR</code></a></td><td>Baptism or naming events for a child.</td></tr><tr class="even"><td><code>CHRA</code></td><td>adult christening<br /><a href="#CHRA"><code>g7:CHRA</code></a></td><td>Baptism or naming events for an adult person.</td></tr><tr class="odd"><td><code>CONF</code></td><td>confirmation<br /><a href="#CONF"><code>g7:CONF</code></a></td><td>Conferring full church membership.</td></tr><tr class="even"><td><code>CREM</code></td><td>cremation<br /><a href="#CREM"><code>g7:CREM</code></a></td><td>The act of reducing a dead body to ashes by fire.</td></tr><tr class="odd"><td><code>DEAT</code></td><td>death<br /><a href="#DEAT"><code>g7:DEAT</code></a></td><td>Mortal life terminates.</td></tr><tr class="even"><td><code>EMIG</code></td><td>emigration<br /><a href="#EMIG"><code>g7:EMIG</code></a></td><td>Leaving one’s homeland with the intent of residing elsewhere.</td></tr><tr class="odd"><td><code>FCOM</code></td><td>first communion<br /><a href="#FCOM"><code>g7:FCOM</code></a></td><td>The first act of sharing in the Lord’s supper as part of church worship.</td></tr><tr class="even"><td><code>GRAD</code></td><td>graduation<br /><a href="#GRAD"><code>g7:GRAD</code></a></td><td>Awarding educational diplomas or degrees to individuals.</td></tr><tr class="odd"><td><code>IMMI</code></td><td>immigration<br /><a href="#IMMI"><code>g7:IMMI</code></a></td><td>Entering into a new locality with the intent of residing there.</td></tr><tr class="even"><td><code>NATU</code></td><td>naturalization<br /><a href="#NATU"><code>g7:NATU</code></a></td><td>Obtaining citizenship.</td></tr><tr class="odd"><td><code>ORDN</code></td><td>ordination<br /><a href="#ORDN"><code>g7:ORDN</code></a></td><td>Receiving authority to act in religious matters.</td></tr><tr class="even"><td><code>PROB</code></td><td>probate<br /><a href="#PROB"><code>g7:PROB</code></a></td><td>Judicial determination of the validity of a will. It may indicate several related court activities over several dates.</td></tr><tr class="odd"><td><code>RETI</code></td><td>retirement<br /><a href="#RETI"><code>g7:RETI</code></a></td><td>Exiting an occupational relationship with an employer after a qualifying time period.</td></tr><tr class="even"><td><code>WILL</code></td><td>will<br /><a href="#WILL"><code>g7:WILL</code></a></td><td>A legal document treated as an event, by which a person disposes of his or her estate. It takes effect after death. The event date is the date the will was signed while the person was alive. (See also <code>PROB</code>)</td></tr></tbody></table><p>In addition, <a href="#INDI-EVEN"><code>INDI</code>.<code>EVEN</code></a> is a structure for a generic individual event. It must have a <a href="#TYPE"><code>TYPE</code></a> substructure to define what kind of event is being provided.</p></section><section id="family-events" data-number="3.3.1.2"><h4 data-number="3.3.1.2"><span class="header-section-number">3.3.1.2</span> Family Events</h4><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>ANUL</code></td><td>annulment<br /><a href="#ANUL"><code>g7:ANUL</code></a></td><td>Declaring a marriage void from the beginning (never existed).</td></tr><tr class="even"><td><code>CENS</code></td><td>census<br /><a href="#FAM-CENS"><code>g7:FAM-CENS</code></a></td><td>Periodic count of the population for a designated locality, such as a national or state census.</td></tr><tr class="odd"><td><code>DIV</code></td><td>divorce<br /><a href="#DIV"><code>g7:DIV</code></a></td><td>Dissolving a marriage through civil action.</td></tr><tr class="even"><td><code>DIVF</code></td><td>divorce filed<br /><a href="#DIVF"><code>g7:DIVF</code></a></td><td>Filing for a divorce by a spouse.</td></tr><tr class="odd"><td><code>ENGA</code></td><td>engagement<br /><a href="#ENGA"><code>g7:ENGA</code></a></td><td>Recording or announcing an agreement between 2 people to become married.</td></tr><tr class="even"><td><code>MARB</code></td><td>marriage bann<br /><a href="#MARB"><code>g7:MARB</code></a></td><td>Official public notice given that 2 people intend to marry.</td></tr><tr class="odd"><td><code>MARC</code></td><td>marriage contract<br /><a href="#MARC"><code>g7:MARC</code></a></td><td>Recording a formal agreement of marriage, including the prenuptial agreement in which marriage partners reach agreement about the property rights of 1 or both, securing property to their children.</td></tr><tr class="even"><td><code>MARL</code></td><td>marriage license<br /><a href="#MARL"><code>g7:MARL</code></a></td><td>Obtaining a legal license to marry.</td></tr><tr class="odd"><td><code>MARR</code></td><td>marriage<br /><a href="#MARR"><code>g7:MARR</code></a></td><td>A legal, common-law, or customary event such as a wedding or marriage ceremony that joins 2 partners to create or extend a family unit.</td></tr><tr class="even"><td><code>MARS</code></td><td>marriage settlement<br /><a href="#MARS"><code>g7:MARS</code></a></td><td>Creating an agreement between 2 people contemplating marriage, at which time they agree to release or modify property rights that would otherwise arise from the marriage.</td></tr></tbody></table><p>In addition, <a href="#FAM-EVEN"><code>FAM</code>.<code>EVEN</code></a> is a structure for a generic family event. It must have a <a href="#TYPE" class="close"><code>TYPE</code></a> substructure to define what kind of event is being provided.</p></section></section><section id="attributes" data-number="3.3.2"><h3 data-number="3.3.2"><span class="header-section-number">3.3.2</span> Attributes</h3><p>Unlike events, the presence of an attribute is sufficient to assert the attribute applied to the individual, regardless of the attribute’s substructures and payload.</p><section id="individual-attributes" data-number="3.3.2.1"><h4 data-number="3.3.2.1"><span class="header-section-number">3.3.2.1</span> Individual Attributes</h4><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>CAST</code></td><td>caste<br /><a href="#CAST"><code>g7:CAST</code></a></td><td>The name of an individual’s rank or status in society which is sometimes based on racial or religious differences, or differences in wealth, inherited rank, profession, or occupation.</td></tr><tr class="even"><td><code>DSCR</code></td><td>physical description<br /><a href="#DSCR"><code>g7:DSCR</code></a></td><td>The physical characteristics of a person.</td></tr><tr class="odd"><td><code>EDUC</code></td><td>education<br /><a href="#EDUC"><code>g7:EDUC</code></a></td><td>Indicator of a level of education attained.</td></tr><tr class="even"><td><code>IDNO</code></td><td>identifying number<br /><a href="#IDNO"><code>g7:IDNO</code></a></td><td>A number or other string assigned to identify a person within some significant external system. It must have a <code>TYPE</code> substructure to define what kind of identification number is being provided.</td></tr><tr class="odd"><td><code>NATI</code></td><td>nationality<br /><a href="#NATI"><code>g7:NATI</code></a></td><td>An individual’s national heritage or origin, or other folk, house, kindred, lineage, or tribal interest.</td></tr><tr class="even"><td><code>NCHI</code></td><td>number of children<br /><a href="#INDI-NCHI"><code>g7:INDI-NCHI</code></a></td><td>The number of children that this person is known to be the parent of (all marriages).</td></tr><tr class="odd"><td><code>NMR</code></td><td>number of marriages<br /><a href="#NMR"><code>g7:NMR</code></a></td><td>The number of times this person has participated in a family as a spouse or parent.</td></tr><tr class="even"><td><code>OCCU</code></td><td>occupation<br /><a href="#OCCU"><code>g7:OCCU</code></a></td><td>The type of work or profession of an individual.</td></tr><tr class="odd"><td><code>PROP</code></td><td>property<br /><a href="#PROP"><code>g7:PROP</code></a></td><td>Pertaining to possessions such as real estate or other property of interest.</td></tr><tr class="even"><td><code>RELI</code></td><td>religion<br /><a href="#INDI-RELI"><code>g7:INDI-RELI</code></a></td><td>A religious denomination to which a person is affiliated or for which a record applies.</td></tr><tr class="odd"><td><code>RESI</code></td><td>residence<br /><a href="#INDI-RESI"><code>g7:INDI-RESI</code></a></td><td>An address or place of residence where an individual resided.</td></tr><tr class="even"><td><code>SSN</code></td><td>social security number<br /><a href="#SSN"><code>g7:SSN</code></a></td><td>A number assigned by the United States Social Security Administration, used for tax identification purposes. It is a type of <code>IDNO</code>.</td></tr><tr class="odd"><td><code>TITL</code></td><td>title<br /><a href="#INDI-TITL"><code>g7:INDI-TITL</code></a></td><td>A formal designation used by an individual in connection with positions of royalty or other social status, such as Grand Duke.</td></tr></tbody></table><p>In addition, <a href="#INDI-FACT"><code>INDI</code>.<code>FACT</code></a> is a structure for a generic individual attribute. It must have a <a href="#TYPE"><code>TYPE</code></a> substructure to define what kind of attribute is being provided.</p></section><section id="family-attributes" data-number="3.3.2.2"><h4 data-number="3.3.2.2"><span class="header-section-number">3.3.2.2</span> Family Attributes</h4><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>NCHI</code></td><td>number of children<br /><a href="#FAM-NCHI"><code>g7:FAM-NCHI</code></a></td><td>The number of children that belong to this family.</td></tr><tr class="even"><td><code>RESI</code></td><td>residence<br /><a href="#FAM-RESI"><code>g7:FAM-RESI</code></a></td><td>An address or place of residence where a family resided.</td></tr></tbody></table><p>In addition, <a href="#FAM-FACT"><code>FAM</code>.<code>FACT</code></a> is a structure for a generic family attribute. It must have a <a href="#TYPE" class="close"><code>TYPE</code></a> substructure to define what kind of attribute is being provided.</p></section></section><section id="latter-day-saint-ordinances" data-number="3.3.3"><h3 data-number="3.3.3"><span class="header-section-number">3.3.3</span> Latter-day Saint Ordinances</h3><p>The structures describing ordinances performed by The Church of Jesus Christ of Latter-day Saints are unlike regular events in that they might either be performed during life or by proxy on the behalf of a deceased individual.</p><p>Proxy ordinances on behalf of deceased persons were once requested and officially recorded using an earlier version of GEDCOM. This is no longer the case, but when it was the case the following principles held:</p><ul><li><a href="#PLAC"><code>PLAC</code></a> was used only for ordinances that were performed by the recipient in life.</li><li><a href="#TEMP"><code>TEMP</code></a> was used with all <a href="#ENDL"><code>ENDL</code></a>, <a href="#SLGC"><code>SLGC</code></a>, and <a href="#SLGS"><code>SLGS</code></a>, but only with posthumous proxy <a href="#BAPL"><code>BAPL</code></a> and <a href="#CONL"><code>CONL</code></a>.</li></ul><table><thead><tr class="header"><th>Tag</th><th>Name<br />URI</th><th>Description</th></tr></thead><tbody><tr class="odd"><td><code>BAPL</code></td><td>baptism<br /><a href="#BAPL" class="close"><code>g7:BAPL</code></a></td><td>The event of baptism performed at age 8 or later by priesthood authority of The Church of Jesus Christ of Latter-day Saints. (See also <a href="#individual-events"><code>BAPM</code></a>)</td></tr><tr class="even"><td><code>CONL</code></td><td>confirmation<br /><a href="#CONL" class="close"><code>g7:CONL</code></a></td><td>The religious event by which a person receives membership in The Church of Jesus Christ of Latter-day Saints. (See also <a href="#individual-events"><code>CONF</code></a>)</td></tr><tr class="odd"><td><code>INIL</code></td><td>initiatory<br /><a href="#INIL"><code>g7:INIL</code></a></td><td>A religious event where an initiatory ordinance for an individual was performed by priesthood authority in a temple of The Church of Jesus Christ of Latter-day Saints.</td></tr><tr class="even"><td><code>ENDL</code></td><td>endowment<br /><a href="#ENDL" class="close"><code>g7:ENDL</code></a></td><td>A religious event where an endowment ordinance for an individual was performed by priesthood authority in a temple of The Church of Jesus Christ of Latter-day Saints.</td></tr><tr class="odd"><td><code>SLGC</code></td><td>sealing child<br /><a href="#SLGC" class="close"><code>g7:SLGC</code></a></td><td>A religious event pertaining to the sealing of a child to his or her parents in a temple ceremony of The Church of Jesus Christ of Latter-day Saints.</td></tr><tr class="even"><td><code>SLGS</code></td><td>sealing spouse<br /><a href="#SLGS" class="close"><code>g7:SLGS</code></a></td><td>A religious event pertaining to the sealing of a husband and wife in a temple ceremony of The Church of Jesus Christ of Latter-day Saints. (See also <a href="#family-events"><code>MARR</code></a>)</td></tr></tbody></table></section><section id="structure-types" data-number="3.3.4"><h3 data-number="3.3.4"><span class="header-section-number">3.3.4</span> Structure types</h3><p>Structure types are listed in this section alphabetically by tag. When the same tag is used for different structure types in different contexts, they may be distinguished by their URI.</p><section id="ABBR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ABBR</code> (Abbreviation) <code class="uri">g7:ABBR</code></h4><p>A short name of a title, description, or name used for sorting, filing, and retrieving records.</p></section><section id="ADDR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADDR</code> (Address) <code class="uri">g7:ADDR</code></h4><p>The location of, or most relevant to, the subject of the superstructure. See <a href="#ADDRESS_STRUCTURE"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></section><section id="ADOP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADOP</code> (Adoption) <code class="uri">g7:ADOP</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="FAMC-ADOP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADOP</code> (Adoption) <code class="uri">g7:FAMC-ADOP</code></h4><p>An enumerated value from set <a href="#enumset-ADOP"><code>g7:enumset-ADOP</code></a> indicating which parent(s) in the family adopted this individual.</p></section><section id="ADR1" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADR1</code> (Address Line 1) <code class="uri">g7:ADR1</code></h4><p>The first line of the address, used for indexing. This structure’s payload should be a single line of text equal to the first line of the corresponding <a href="#ADDR" class="close"><code>ADDR</code></a>. See <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p><div class="deprecation"><p><a href="#ADR1" class="close"><code>ADR1</code></a> should not be added to new files; see <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></div></section><section id="ADR2" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADR2</code> (Address Line 2) <code class="uri">g7:ADR2</code></h4><p>The second line of the address, used for indexing. This structure’s payload should be a single line of text equal to the second line of the corresponding <a href="#ADDR" class="close"><code>ADDR</code></a>. See <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p><div class="deprecation"><p><a href="#ADR2" class="close"><code>ADR2</code></a> should not be added to new files; see <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></div></section><section id="ADR3" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ADR3</code> (Address Line 3) <code class="uri">g7:ADR3</code></h4><p>The third line of the address, used for indexing. This structure’s payload should be a single line of text equal to the third line of the corresponding <a href="#ADDR" class="close"><code>ADDR</code></a>. See <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p><div class="deprecation"><p><a href="#ADR3" class="close"><code>ADR3</code></a> should not be added to new files; see <a href="#ADDRESS_STRUCTURE" class="close"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></div></section><section id="AGE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>AGE</code> (Age at event) <code class="uri">g7:AGE</code></h4><p>The age of the individual at the time an event occurred, or the age listed in the document.</p></section><section id="AGNC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>AGNC</code> (Responsible agency) <code class="uri">g7:AGNC</code></h4><p>The organization, institution, corporation, person, or other entity that has responsibility for the associated context. Examples are an employer of a person of an associated occupation, or a church that administered rites or events, or an organization responsible for creating or archiving records.</p></section><section id="ALIA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ALIA</code> (Alias) <code class="uri">g7:ALIA</code></h4><p>A single individual may have facts distributed across multiple individual records, connected by <a href="#ALIA" class="close"><code>ALIA</code></a> pointers (named after “alias” in the computing sense, not the pseudonym sense).</p><div class="note"><p>This specification does not define how to connect <code>INDI</code> records with <a href="#ALIA" class="close"><code>ALIA</code></a>. Some systems organize <a href="#ALIA" class="close"><code>ALIA</code></a> pointers to create a tree structure, with the root <code>INDI</code> record containing the composite view of all facts in the leaf <code>INDI</code> records. Others distribute events and attributes between <code>INDI</code> records mutually linked by symmetric pairs of <a href="#ALIA" class="close"><code>ALIA</code></a> pointers. A future version of this specification may adjust the definition of <a href="#ALIA" class="close"><code>ALIA</code></a>.</p></div></section><section id="ANCI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ANCI</code> (Ancestor interest) <code class="uri">g7:ANCI</code></h4><p>Indicates an interest in additional research for ancestors of this individual. (See also <a href="#DESI"><code>DESI</code></a>).</p></section><section id="ANUL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ANUL</code> (Annulment) <code class="uri">g7:ANUL</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="ASSO" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ASSO</code> (Associates) <code class="uri">g7:ASSO</code></h4><p>A pointer to an associated individual. See <a href="#ASSOCIATION_STRUCTURE"><code>ASSOCIATION_STRUCTURE</code></a> for more details.</p></section><section id="AUTH" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>AUTH</code> (Author) <code class="uri">g7:AUTH</code></h4><p>The person, agency, or entity who created the record. For a published work, this could be the author, compiler, transcriber, abstractor, or editor. For an unpublished source, this may be an individual, a government agency, church organization, or private organization.</p></section><section id="BAPL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BAPL</code> (Baptism, Latter-Day Saint) <code class="uri">g7:BAPL</code></h4><p>A <a href="#latter-day-saint-ordinances">Latter-Day Saint Ordinance</a>. See also <a href="#LDS_INDIVIDUAL_ORDINANCE"><code>LDS_INDIVIDUAL_ORDINANCE</code></a>.</p></section><section id="BAPM" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BAPM</code> (Baptism) <code class="uri">g7:BAPM</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BARM" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BARM</code> (Bar Mitzvah) <code class="uri">g7:BARM</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BASM" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BASM</code> (Bas Mitzvah) <code class="uri">g7:BASM</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BIRT" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BIRT</code> (Birth) <code class="uri">g7:BIRT</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BLES" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BLES</code> (Blessing) <code class="uri">g7:BLES</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="BURI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>BURI</code> (Depositing remains) <code class="uri">g7:BURI</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p><p>Although defined as any depositing of remains since it was introduced in the first version of GEDCOM, this tag is a shortened form of the English word “burial” and has been interpreted to mean “depositing of remains by burial” by some applications and users. In the absence of a clarifying <a href="#TYPE"><code>TYPE</code></a> substructure it is likely, but not guaranteed, that a <a href="#BURI" class="close"><code>BURI</code></a> structure refers to a burial rather than another form of depositing remains.</p></section><section id="CALN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CALN</code> (Call number) <code class="uri">g7:CALN</code></h4><p>An identification or reference description used to file and retrieve items from the holdings of a repository. Despite the word “number” in the name, may contain any character, not just digits.</p></section><section id="CAST" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CAST</code> (Caste) <code class="uri">g7:CAST</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="CAUS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CAUS</code> (Cause) <code class="uri">g7:CAUS</code></h4><p>The reasons which precipitated an event. It is often used subordinate to a death event to show cause of death, such as might be listed on a death certificate.</p></section><section id="FAM-CENS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CENS</code> (Census) <code class="uri">g7:FAM-CENS</code></h4><p>An <a href="#family-events">Family Event</a>.</p></section><section id="INDI-CENS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CENS</code> (Census) <code class="uri">g7:INDI-CENS</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CHAN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CHAN</code> (Change) <code class="uri">g7:CHAN</code></h4><p>The most recent change to the superstructure. This is metadata about the structure itself, not data about its subject. See <a href="#CHANGE_DATE"><code>CHANGE_DATE</code></a> for more details.</p></section><section id="CHIL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CHIL</code> (Child) <code class="uri">g7:CHIL</code></h4><p>The child in a family, whether biological, adopted, foster, sealed, or other relationship.</p></section><section id="CHRA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CHRA</code> (Christening, adult) <code class="uri">g7:CHRA</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CHR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CHR</code> (Christening) <code class="uri">g7:CHR</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CITY" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CITY</code> (City) <code class="uri">g7:CITY</code></h4><p>The name of the city used in the address. See <a href="#ADDRESS_STRUCTURE"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></section><section id="CONF" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CONF</code> (Confirmation) <code class="uri">g7:CONF</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE" class="close"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CONL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CONL</code> (Confirmation, Latter-Day Saint) <code class="uri">g7:CONL</code></h4><p>A <a href="#latter-day-saint-ordinances">Latter-Day Saint Ordinance</a>. See also <a href="#LDS_INDIVIDUAL_ORDINANCE"><code>LDS_INDIVIDUAL_ORDINANCE</code></a>.</p></section><section id="CONT" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CONT</code> (Continued) <code class="uri">g7:CONT</code></h4><p>A pseudo-structure to indicate a line break. The <a href="#CONT" class="close"><code>CONT</code></a> tag is generated during serialization and is never present in parsed datasets. See <a href="#lines">Lines</a> for more details.</p></section><section id="COPR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>COPR</code> (Copyright) <code class="uri">g7:COPR</code></h4><p>A copyright statement, as appropriate for the copyright laws applicable to this data.</p></section><section id="CORP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CORP</code> (Corporate name) <code class="uri">g7:CORP</code></h4><p>The name of the business, corporation, or person that produced or commissioned the product.</p></section><section id="CREA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CREA</code> (Creation) <code class="uri">g7:CREA</code></h4><p>The initial creation of the superstructure. This is metadata about the structure itself, not data about its subject. See <a href="#CREATION_DATE"><code>CREATION_DATE</code></a> for more details.</p></section><section id="CREM" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CREM</code> (Cremation) <code class="uri">g7:CREM</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="CROP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CROP</code> (Crop) <code class="uri">g7:CROP</code></h4><p>A subregion of an image to display. It is only valid when the superstructure links to a <a href="#MULTIMEDIA_RECORD"><code>MULTIMEDIA_RECORD</code></a> with at least 1 <a href="#FILE"><code>FILE</code></a> substructure that refers to an external file with a defined pixel unit.</p><p><a href="#LEFT"><code>LEFT</code></a> and <a href="#TOP"><code>TOP</code></a> indicate the top-left corner of the region to display. <a href="#WIDTH"><code>WIDTH</code></a> and <a href="#HEIGHT"><code>HEIGHT</code></a> indicate how many pixels wide and tall the region to display is. If omitted, <a href="#LEFT" class="close"><code>LEFT</code></a> and <a href="#TOP" class="close"><code>TOP</code></a> each default to 0; <a href="#WIDTH" class="close"><code>WIDTH</code></a> defaults to the image width minus <a href="#LEFT" class="close"><code>LEFT</code></a>; and <a href="#HEIGHT" class="close"><code>HEIGHT</code></a> defaults to the image height minus <a href="#TOP" class="close"><code>TOP</code></a>.</p><p>If the superstructure links to a <a href="#MULTIMEDIA_RECORD" class="close"><code>MULTIMEDIA_RECORD</code></a> that includes multiple <a href="#FILE" class="close"><code>FILE</code></a> substructures, the <a href="#CROP" class="close"><code>CROP</code></a> applies to the first <a href="#FILE" class="close"><code>FILE</code></a> to which it can apply, namely the first external file with a defined pixel unit.</p><p>It is recommended that <a href="#CROP" class="close"><code>CROP</code></a> be used only with a single-FILE <a href="#MULTIMEDIA_RECORD" class="close"><code>MULTIMEDIA_RECORD</code></a>.</p><p>The following are errors:</p><ul><li><a href="#LEFT" class="close"><code>LEFT</code></a> or <a href="#LEFT" class="close"><code>LEFT</code></a> + <a href="#WIDTH" class="close"><code>WIDTH</code></a> exceed the image width.</li><li><a href="#TOP" class="close"><code>TOP</code></a> or <a href="#TOP" class="close"><code>TOP</code></a> + <a href="#HEIGHT" class="close"><code>HEIGHT</code></a> exceed the image height.</li><li><a href="#CROP" class="close"><code>CROP</code></a> applied to a non-image or image without a defined pixel unit.</li></ul></section><section id="CTRY" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>CTRY</code> (Country) <code class="uri">g7:CTRY</code></h4><p>The name of the country that pertains to the associated address. See <a href="#ADDRESS_STRUCTURE"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></section><section id="DATA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATA</code> (Data) <code class="uri">g7:DATA</code></h4><p>A structure with no payload used to distinguish a description of something from metadata about it. For example, <a href="#SOUR"><code>SOUR</code></a> and its other substructures describe a source itself, while <a href="#SOUR-DATA" class="close"><code>SOUR</code>.<code>DATA</code></a> describes the content of the source.</p></section><section id="SOUR-DATA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATA</code> (Data) <code class="uri">g7:SOUR-DATA</code></h4><p>See <a href="#DATA" class="close"><code>g7:DATA</code></a>.</p></section><section id="HEAD-SOUR-DATA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATA</code> (Data) <code class="uri">g7:HEAD-SOUR-DATA</code></h4><p>The electronic data source or digital repository from which this dataset was exported. The payload is the name of that source, with substructures providing additional details about the source (not the export).</p></section><section id="DATE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:DATE</code></h4><p>The principal date of the subject of the superstructure. The payload is a <a href="#date"><code>DateValue</code></a>.</p><p>When the superstructure is an event, the principal date indicates when the event took place.</p><p>When the superstructure is an attribute, the principal date indicates when the attribute was observed, asserted, or applied. A date period might put bounds on the attributes applicability, but other date forms assume that the attribute may have also applied on other dates too.</p><p>When the superstructure is a <a href="#SOUR-DATA"><code>g7:SOUR-DATA</code></a>, the principal date indicates when the data was entered into the source; or, for a source like a website that changes over time, a date on which the source contained the data.</p><p>See <a href="#DATE_VALUE"><code>DATE_VALUE</code></a> for more details.</p></section><section id="DATE-exact" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:DATE-exact</code></h4><p>The principal date of the subject of the superstructure. The payload is a <a href="#date" class="close"><code>DateExact</code></a>.</p></section><section id="HEAD-DATE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:HEAD-DATE</code></h4><p>The <a href="#date" class="close"><code>DateExact</code></a> that this document was created.</p></section><section id="NO-DATE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:NO-DATE</code></h4><p>The <a href="#date" class="close"><code>DatePeriod</code></a> during which the event did not occur or the attribute did not apply.</p></section><section id="DATA-EVEN-DATE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DATE</code> (Date) <code class="uri">g7:DATA-EVEN-DATE</code></h4><p>The <a href="#date" class="close"><code>DatePeriod</code></a> covered by the entire source; the period during which this source recorded events.</p></section><section id="DEAT" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DEAT</code> (Death) <code class="uri">g7:DEAT</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="DESI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DESI</code> (Descendant Interest) <code class="uri">g7:DESI</code></h4><p>Indicates an interest in research to identify additional descendants of this individual. See also <a href="#ANCI"><code>ANCI</code></a>.</p></section><section id="DEST" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DEST</code> (Destination) <code class="uri">g7:DEST</code></h4><p>An identifier for the system expected to receive this document. See <a href="#HEAD-SOUR"><code>HEAD</code>.<code>SOUR</code></a> for guidance on choosing identifiers.</p></section><section id="DIVF" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DIVF</code> (Divorce filing) <code class="uri">g7:DIVF</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="DIV" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DIV</code> (Divorce) <code class="uri">g7:DIV</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="DSCR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>DSCR</code> (Description) <code class="uri">g7:DSCR</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="EDUC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EDUC</code> (Education) <code class="uri">g7:EDUC</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE" class="close"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="EMAIL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EMAIL</code> (Email) <code class="uri">g7:EMAIL</code></h4><p>An electronic mail address, as defined by any relevant standard such as <a href="https://www.rfc-editor.org/info/rfc3696">RFC 3696</a>, <a href="https://www.rfc-editor.org/info/rfc5321">RFC 5321</a>, or <a href="https://www.rfc-editor.org/info/rfc5322">RFC 5322</a>.</p><p>If an invalid email address is present upon import, it should be preserved as-is on export.</p><div class="note"><p>The version 5.5.1 specification contained a typo where this tag was sometimes written <code>EMAI</code> and sometimes written <a href="#EMAIL" class="close"><code>EMAIL</code></a>. <a href="#EMAIL" class="close"><code>EMAIL</code></a> should be used in version 7.0 and later.</p></div></section><section id="EMIG" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EMIG</code> (Emigration) <code class="uri">g7:EMIG</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="ENDL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ENDL</code> (Endowment, Latter-Day Saint) <code class="uri">g7:ENDL</code></h4><p>A <a href="#latter-day-saint-ordinances">Latter-Day Saint Ordinance</a>. See also <a href="#LDS_INDIVIDUAL_ORDINANCE"><code>LDS_INDIVIDUAL_ORDINANCE</code></a>.</p></section><section id="ENGA" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ENGA</code> (Engagement) <code class="uri">g7:ENGA</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="FAM-EVEN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EVEN</code> (Event) <code class="uri">g7:FAM-EVEN</code></h4><p>See <a href="#INDI-EVEN" class="close"><code>g7:INDI-EVEN</code></a>.</p></section><section id="INDI-EVEN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>EVEN</code> (Event) <code class="uri">g7:INDI-EVEN</code></h4><p>An event: a noteworthy happening related to an individual or family. If a specific event type exists, it should be used instead of a generic <code>EVEN</code> structure. Each <code>EVEN</code> must be classified by a subordinate use of the <a href="#TYPE"><code>TYPE</code></a> tag and may be further described in the structure’s payload.</p><div class="example"><p>A person that signed a lease for land dated October 2, 1837 and a lease for mining equipment dated November 4, 1837 would be written as:</p><div class="sourceCode" id="cb76"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb76-1"><a href="#cb76-1"></a><span class="dt">0 </span><span class="cf">@I1@ </span><span class="fu">INDI</span></span>
 <span id="cb76-2"><a href="#cb76-2"></a><span class="dt">1 </span><span class="fu">EVEN</span></span>
 <span id="cb76-3"><a href="#cb76-3"></a><span class="dt">2 </span><span class="fu">TYPE </span>Land Lease</span>
 <span id="cb76-4"><a href="#cb76-4"></a><span class="dt">2 </span><span class="fu">DATE </span>2 OCT 1837</span>
@@ -1130,7 +1130,7 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb79-2"><a href="#cb79-2"></a><span class="dt">1 </span><span class="fu">DSCR </span>brown eyes, 5ft 10in, 198 pounds</span></code></pre></div></div></div></section><section id="HUSB" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>HUSB</code> (Husband) <code class="uri">g7:HUSB</code></h4><p>A container for information relevant to the subject of the superstructure specific to the individual described by the associated <code>FAM</code>’s <a href="#HUSB" class="close"><code>HUSB</code></a> substructure.</p></section><section id="FAM-HUSB" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>HUSB</code> (Husband) <code class="uri">g7:FAM-HUSB</code></h4><p>This is a partner in a <code>FAM</code> record. See <a href="#FAMILY_RECORD"><code>FAMILY_RECORD</code></a> for more details.</p></section><section id="IDNO" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>IDNO</code> (Identification number) <code class="uri">g7:IDNO</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE" class="close"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="IMMI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>IMMI</code> (Immigration) <code class="uri">g7:IMMI</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="record-INDI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>INDI</code> (Individual) <code class="uri">g7:record-INDI</code></h4><p>See <a href="#INDIVIDUAL_RECORD"><code>INDIVIDUAL_RECORD</code></a>.</p></section><section id="INIL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>INIL</code> (Initiatory, Latter-Day Saint) <code class="uri">g7:INIL</code></h4><p>A <a href="#latter-day-saint-ordinances">Latter-Day Saint Ordinance</a>. See also <a href="#LDS_INDIVIDUAL_ORDINANCE"><code>LDS_INDIVIDUAL_ORDINANCE</code></a>. Previously, GEDCOM versions 3.0 through 5.3 called this <code>WAC</code>; it was not part of 5.4 through 5.5.1. FamilySearch GEDCOM 7.0 reintroduced it with the name <a href="#INIL" class="close"><code>INIL</code></a> for consistency with <a href="#BAPL"><code>BAPL</code></a>, <a href="#CONL"><code>CONL</code></a>, and <a href="#ENDL"><code>ENDL</code></a>.</p></section><section id="LANG" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LANG</code> (Language) <code class="uri">g7:LANG</code></h4><p>The primary human language of the superstructure. The primary language in which the <a href="#text"><code>Text</code></a>-typed payloads of the superstructure and its substructures appear.</p><p>The payload of the <a href="#LANG" class="close"><code>LANG</code></a> structure is a language tag, as defined by <a href="https://www.rfc-editor.org/info/bcp47">BCP 47</a>. A <a href="https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry">registry of component subtags</a> is maintained publicly by the IANA.</p><p>In the absence of a <a href="#LANG" class="close"><code>LANG</code></a> structure, the language is assumed to be unspecified; that may also be recorded explicitly with language tag <code>und</code> (meaning “undetermined”). See <a href="#HEAD-LANG"><code>g7:HEAD-LANG</code></a> for information about applying language-specific algorithms to text in an unspecified language.</p><p>If the text is primarily in one language with a few parts in a different language, it is recommended that a language tag identifying the primary language be used. If no one language is primary, the language tag <code>mul</code> (meaning “multiple”) may be used, but most language-specific algorithms will treat <code>mul</code> the same way they do <code>und</code>.</p><div class="note"><p>Conversations are ongoing about adding part-of-payload language tagging in a future version of the specification to provide more fidelity for multilingual text.</p></div><p>If the text is not in any human language and should not be treated as lingual content, the language tag <code>zxx</code> (meaning “no linguistic content” or “not applicable”) may be used. An example of <code>zxx</code> text might be a diagram approximated using characters for their shape, not their meaning.</p><div class="note"><p>This specification does not permit <a href="#LANG" class="close"><code>LANG</code></a> in every place where human language text might appear. Conversations are ongoing about adding it in more places in a future version of the specification. Using the current specification, additional language tagging can be accomplished using a <a href="#extension-tags">documented extension tag</a> by including the following in the header:</p><div class="sourceCode" id="cb80"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb80-1"><a href="#cb80-1"></a><span class="dt">1 </span><span class="fu">SCHEMA</span></span>
 <span id="cb80-2"><a href="#cb80-2"></a><span class="dt">2 </span><span class="fu">TAG </span>_LANG https://gedcom.io/terms/v7/LANG</span></code></pre></div><p>and using the extension tag like so:</p><div class="sourceCode" id="cb81"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb81-1"><a href="#cb81-1"></a><span class="dt">2 </span><span class="fu">DATE </span>31 AUG 2018</span>
 <span id="cb81-2"><a href="#cb81-2"></a><span class="dt">3 </span><span class="fu">PHRASE </span>2018年8月31日</span>
-<span id="cb81-3"><a href="#cb81-3"></a><span class="dt">4 </span><span class="fu">_LANG </span>cmn</span></code></pre></div></div></section><section id="HEAD-LANG" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LANG</code> (Language) <code class="uri">g7:HEAD-LANG</code></h4><p>A default language which may be used to interpret any <a href="#text"><code>Text</code></a>-typed payloads that lack a specific language tag from a <a href="#LANG"><code>g7:LANG</code></a> structure. An application may choose to use a different default based on its knowledge of the language preferences of the user.</p><p>The payload of the <a href="#LANG" class="close"><code>LANG</code></a> structure is a language tag, as defined by <a href="https://www.rfc-editor.org/info/bcp47">BCP 47</a>.</p><div class="note"><p>Some algorithms on text are language-specific. Examples include sorting sequences, name comparison and phonetic name matching algorithms, spell-checking, computer-synthesized speech, Braille transcription, and language translation. When the language of the text is given through a <a href="#LANG" class="close"><code>g7:LANG</code></a>, that should be used. When <a href="#LANG" class="close"><code>g7:LANG</code></a> is not available, <a href="#HEAD-LANG" class="close"><code>g7:HEAD-LANG</code></a> provides the file creator’s suggested default language. For some language-specific algorithms, the user’s preferred language may be a more appropriate default than the file’s default language. User language preferences can be found in a variety of platform-specific places, such as the default language from operating system settings, user locales, Input Method Editors (IMEs), etc.</p></div></section><section id="SUBM-LANG" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LANG</code> (Language) <code class="uri">g7:SUBM-LANG</code></h4><p>A language the subject of that record understands.</p><p>The payload of the <a href="#LANG" class="close"><code>LANG</code></a> structure is a language tag, as defined by <a href="https://www.rfc-editor.org/info/bcp47">BCP 47</a>.</p></section><section id="LATI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LATI</code> (Latitude) <code class="uri">g7:LATI</code></h4><p>A latitudinal coordinate. The payload is either <code>N</code> (for a coordinate north of the equator) or <code>S</code> (for a coordinate south of the equator) followed by a decimal number of degrees. Minutes and seconds are not used and should be converted to fractional degrees prior to encoding.</p><div class="example"><p>18 degrees, 9 minutes, and 3.4 seconds North would be formatted as <code>N18.150944</code>.</p></div></section><section id="LEFT" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LEFT</code> (Left crop width) <code class="uri">g7:LEFT</code></h4><p>Left is a number of pixels to not display from the left side of the image. See <a href="#CROP"><code>CROP</code></a> for more details.</p></section><section id="LONG" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LONG</code> (Longitude) <code class="uri">g7:LONG</code></h4><p>A longitudinal coordinate. The payload is either <code>E</code> (for a coordinate east of the prime meridian) or <code>W</code> (for a coordinate west of the prime meridian) followed by a decimal number of degrees. Minutes and seconds are not used and should be converted to fractional degrees prior to encoding.</p><div class="example"><p>168 degrees, 9 minutes, and 3.4 seconds East would be formatted as <code>E168.150944</code>.</p></div></section><section id="MAP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MAP</code> (Map) <code class="uri">g7:MAP</code></h4><p>A representative point for a location, as defined by <a href="#LATI"><code>LATI</code></a> and <a href="#LONG" class="close"><code>LONG</code></a> substructures.</p><p>Note that <a href="#MAP" class="close"><code>MAP</code></a> provides neither a notion of accuracy (for example, the <a href="#MAP" class="close"><code>MAP</code></a> for a birth event may be some distance from the point where the birth occurred) nor a notion of region size (for example, the <a href="#MAP" class="close"><code>MAP</code></a> for a place “Belarus” may be anywhere within that nation’s 200,000 square kilometer area).</p></section><section id="MARB" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARB</code> (Marriage banns) <code class="uri">g7:MARB</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MARC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARC</code> (Marriage contract) <code class="uri">g7:MARC</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MARL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARL</code> (Marriage license) <code class="uri">g7:MARL</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MARR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARR</code> (Marriage) <code class="uri">g7:MARR</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MARS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARS</code> (Marriage settlement) <code class="uri">g7:MARS</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MEDI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MEDI</code> (Medium) <code class="uri">g7:MEDI</code></h4><p>An enumerated value from set <a href="#enumset-MEDI"><code>g7:enumset-MEDI</code></a> providing information about the media or the medium in which information is stored.</p><p>When <a href="#MEDI" class="close"><code>MEDI</code></a> is a substructure of a <a href="#CALN"><code>g7:CALN</code></a>, it is recommended that its payload describes the medium directly found at that call number rather than a medium from which it was derived.</p><div class="example"><p>Consider an asset in a repository that is a digital scan of a book of compiled newspapers; for this asset, the <code>CALN</code>.<code>MEDI</code> is recommended to be <code>ELECTRONIC</code> rather than <code>BOOK</code> or <code>NEWSPAPER</code>.</p></div></section><section id="MIME" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MIME</code> (Media type) <code class="uri">g7:MIME</code></h4><p>Indicates the <a href="#media-type">media type</a> of the payload of the superstructure.</p><p>As of version 7.0, only 2 media types are supported by this structure:</p><ul><li><p><code>text/plain</code> shall be presented to the user as-is, preserving all spacing, line breaks, and so forth.</p></li><li><p><code>text/html</code> uses HTML tags to provide presentation information. Applications should support at least the following:</p><ul><li><code>p</code> and <code>br</code> elements for paragraphing and line breaks.</li><li><code>b</code>, <code>i</code>, <code>u</code>, and <code>s</code> elements for bold, italic, underlined, and strike-through text (or corresponding display in other locales; see <a href="https://html.spec.whatwg.org/multipage/text-level-semantics.html">HTML §4.5</a> for more).</li><li><code>sup</code> and <code>sub</code> elements for super- and sub-script.</li><li>The 3 XML entities that appear in text: <code>&amp;amp;</code>, <code>&amp;lt;</code> <code>&amp;gt;</code>. Note that <code>&amp;quote;</code> and <code>&amp;apos;</code> are only needed in attributes. Other entities should be represented as their respective Unicode characters instead.</li></ul><p>Supporting more of HTML is encouraged. Unsupported elements should be ignored during display.</p></li></ul><div class="note"><p>Applications are welcome to support more XML entities or HTML character references in their user interface. However, exporting must only use the core XML entities, translating any other entities into their corresponding Unicode characters.</p></div><div class="note"><p>Applications are welcome to support additional HTML elements, but they should ensure that content is meaningful if those extra elements are ignored and only their content text is displayed.</p></div><div class="note"><p>Media types are also used by external files, as described under <a href="#FORM"><code>FORM</code></a>. External file media types are not limited to <code>text/plain</code> and <code>text/html</code>.</p></div><p>If needed, <code>text/html</code> can be converted to <code>text/plain</code> using the following steps:</p><ol type="1"><li>Replace any sequence of 1 or more spaces, tabs, and line breaks with a single space</li><li>Case-insensitively replace each <code>&lt;p</code>…<code>&gt;</code>, <code>&lt;/p</code>…<code>&gt;</code>, and <code>&lt;br</code>…<code>&gt;</code> with a line break</li><li>Remove all other <code>&lt;</code>…<code>&gt;</code> tags</li><li>Replace each <code>&amp;lt;</code> with <code>&lt;</code> and <code>&amp;gt;</code> with <code>&gt;</code></li><li>Replace each <code>&amp;amp;</code> with <code>&amp;</code></li></ol></section><section id="NAME" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NAME</code> (Name) <code class="uri">g7:NAME</code></h4><p>The name of the superstructure’s subject, represented as a simple string.</p></section><section id="INDI-NAME" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NAME</code> (Name) <code class="uri">g7:INDI-NAME</code></h4><p>A <a href="#PERSONAL_NAME_STRUCTURE"><code>PERSONAL_NAME_STRUCTURE</code></a> with parts, translations, sources, and so forth.</p></section><section id="NATI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NATI</code> (Nationality) <code class="uri">g7:NATI</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="NATU" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NATU</code> (Naturalization) <code class="uri">g7:NATU</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="FAM-NCHI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NCHI</code> (Number of children) <code class="uri">g7:FAM-NCHI</code></h4><p>A <a href="#family-attributes">Family Attribute</a>. See also <a href="#FAMILY_ATTRIBUTE_STRUCTURE"><code>FAMILY_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="INDI-NCHI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NCHI</code> (Number of children) <code class="uri">g7:INDI-NCHI</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE" class="close"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="NICK" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NICK</code> (Nickname) <code class="uri">g7:NICK</code></h4><p>A descriptive or familiar name that is used instead of, or in addition to, one’s proper name.</p></section><section id="NMR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NMR</code> (Number of marriages) <code class="uri">g7:NMR</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE" class="close"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="NO" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NO</code> (Did not happen) <code class="uri">g7:NO</code></h4><p>An enumerated value from set <a href="#enumset-EVEN"><code>g7:enumset-EVEN</code></a> identifying an event type which did not occur to the superstructure’s subject. A specific payload <code>NO XYZ</code> should only appear where <code>XYZ</code> would be legal.</p><p>See <a href="#NON_EVENT_STRUCTURE"><code>NON_EVENT_STRUCTURE</code></a> for more details.</p></section><section id="NOTE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NOTE</code> (Note) <code class="uri">g7:NOTE</code></h4><p>A <a href="#NOTE_STRUCTURE"><code>NOTE_STRUCTURE</code></a>, containing additional information provided by the submitter for understanding the enclosing data.</p><p>When a substructure of <a href="#HEAD"><code>HEAD</code></a>, it should describe the contents of the document in terms of “ancestors or descendants of” so that the person receiving the data knows what genealogical information the document contains.</p></section><section id="NPFX" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NPFX</code> (Name prefix) <code class="uri">g7:NPFX</code></h4><p>Text that appears on a name line before the given and surname parts of a name.</p></section><section id="NSFX" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NSFX</code> (Name suffix) <code class="uri">g7:NSFX</code></h4><p>Text which appears on a name line after or behind the given and surname parts of a name.</p></section><section id="OBJE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>OBJE</code> (Object) <code class="uri">g7:OBJE</code></h4><p>See <a href="#MULTIMEDIA_LINK" class="close"><code>MULTIMEDIA_LINK</code></a>.</p></section><section id="record-OBJE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>OBJE</code> (Object) <code class="uri">g7:record-OBJE</code></h4><p>See <a href="#MULTIMEDIA_RECORD"><code>MULTIMEDIA_RECORD</code></a>.</p></section><section id="OCCU" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>OCCU</code> (Occupation) <code class="uri">g7:OCCU</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="ORDN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ORDN</code> (Ordination) <code class="uri">g7:ORDN</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="PAGE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PAGE</code> (Page) <code class="uri">g7:PAGE</code></h4><p>A specific location within the information referenced. For a published work, this could include the volume of a multi-volume work and the page number or numbers. For a periodical, it could include volume, issue, and page numbers. For a newspaper, it could include a date, page number, and column number. For an unpublished source or microfilmed works, this could be a film or sheet number, page number, or frame number. A census record might have an enumerating district, page number, line number, dwelling number, and family number.</p><p>It is recommended that the data in this field be formatted comma-separated with label: value pairs</p><div class="example"><div class="sourceCode" id="cb82"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb82-1"><a href="#cb82-1"></a><span class="dt">2 </span><span class="fu">SOUR </span><span class="va">@S1@</span></span>
+<span id="cb81-3"><a href="#cb81-3"></a><span class="dt">4 </span><span class="fu">_LANG </span>cmn</span></code></pre></div></div></section><section id="HEAD-LANG" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LANG</code> (Language) <code class="uri">g7:HEAD-LANG</code></h4><p>A default language which may be used to interpret any <a href="#text"><code>Text</code></a>-typed payloads that lack a specific language tag from a <a href="#LANG"><code>g7:LANG</code></a> structure. An application may choose to use a different default based on its knowledge of the language preferences of the user.</p><p>The payload of the <a href="#LANG" class="close"><code>LANG</code></a> structure is a language tag, as defined by <a href="https://www.rfc-editor.org/info/bcp47">BCP 47</a>.</p><div class="note"><p>Some algorithms on text are language-specific. Examples include sorting sequences, name comparison and phonetic name matching algorithms, spell-checking, computer-synthesized speech, Braille transcription, and language translation. When the language of the text is given through a <a href="#LANG" class="close"><code>g7:LANG</code></a>, that should be used. When <a href="#LANG" class="close"><code>g7:LANG</code></a> is not available, <a href="#HEAD-LANG" class="close"><code>g7:HEAD-LANG</code></a> provides the file creator’s suggested default language. For some language-specific algorithms, the user’s preferred language may be a more appropriate default than the file’s default language. User language preferences can be found in a variety of platform-specific places, such as the default language from operating system settings, user locales, Input Method Editors (IMEs), etc.</p></div></section><section id="SUBM-LANG" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LANG</code> (Language) <code class="uri">g7:SUBM-LANG</code></h4><p>A language the subject of that record understands.</p><p>The payload of the <a href="#LANG" class="close"><code>LANG</code></a> structure is a language tag, as defined by <a href="https://www.rfc-editor.org/info/bcp47">BCP 47</a>.</p></section><section id="LATI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LATI</code> (Latitude) <code class="uri">g7:LATI</code></h4><p>A latitudinal coordinate. The payload is either <code>N</code> (for a coordinate north of the equator) or <code>S</code> (for a coordinate south of the equator) followed by a decimal number of degrees. Minutes and seconds are not used and should be converted to fractional degrees prior to encoding.</p><div class="example"><p>18 degrees, 9 minutes, and 3.4 seconds North would be formatted as <code>N18.150944</code>.</p></div></section><section id="LEFT" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LEFT</code> (Left crop width) <code class="uri">g7:LEFT</code></h4><p>Left is a number of pixels to not display from the left side of the image. See <a href="#CROP"><code>CROP</code></a> for more details.</p></section><section id="LONG" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>LONG</code> (Longitude) <code class="uri">g7:LONG</code></h4><p>A longitudinal coordinate. The payload is either <code>E</code> (for a coordinate east of the prime meridian) or <code>W</code> (for a coordinate west of the prime meridian) followed by a decimal number of degrees. Minutes and seconds are not used and should be converted to fractional degrees prior to encoding.</p><div class="example"><p>168 degrees, 9 minutes, and 3.4 seconds East would be formatted as <code>E168.150944</code>.</p></div></section><section id="MAP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MAP</code> (Map) <code class="uri">g7:MAP</code></h4><p>A representative point for a location, as defined by <a href="#LATI"><code>LATI</code></a> and <a href="#LONG" class="close"><code>LONG</code></a> substructures.</p><p>Note that <a href="#MAP" class="close"><code>MAP</code></a> provides neither a notion of accuracy (for example, the <a href="#MAP" class="close"><code>MAP</code></a> for a birth event may be some distance from the point where the birth occurred) nor a notion of region size (for example, the <a href="#MAP" class="close"><code>MAP</code></a> for a place “Belarus” may be anywhere within that nation’s 200,000 square kilometer area).</p></section><section id="MARB" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARB</code> (Marriage banns) <code class="uri">g7:MARB</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MARC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARC</code> (Marriage contract) <code class="uri">g7:MARC</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MARL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARL</code> (Marriage license) <code class="uri">g7:MARL</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MARR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARR</code> (Marriage) <code class="uri">g7:MARR</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MARS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MARS</code> (Marriage settlement) <code class="uri">g7:MARS</code></h4><p>A <a href="#family-events">Family Event</a>. See also <a href="#FAMILY_EVENT_STRUCTURE" class="close"><code>FAMILY_EVENT_STRUCTURE</code></a>.</p></section><section id="MEDI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MEDI</code> (Medium) <code class="uri">g7:MEDI</code></h4><p>An enumerated value from set <a href="#enumset-MEDI"><code>g7:enumset-MEDI</code></a> providing information about the media or the medium in which information is stored.</p><p>When <a href="#MEDI" class="close"><code>MEDI</code></a> is a substructure of a <a href="#CALN"><code>g7:CALN</code></a>, it is recommended that its payload describes the medium directly found at that call number rather than a medium from which it was derived.</p><div class="example"><p>Consider an asset in a repository that is a digital scan of a book of compiled newspapers; for this asset, the <code>CALN</code>.<code>MEDI</code> is recommended to be <code>ELECTRONIC</code> rather than <code>BOOK</code> or <code>NEWSPAPER</code>.</p></div><p>When <a href="#MEDI" class="close"><code>MEDI</code></a> is a substructure of a <a href="#FORM"><code>g7:FORM</code></a>, it is recommended that its payload describes the medium from which it was derived.</p><div class="example"><p>Consider a digital photo in a multimedia record; for this asset, the <code>FORM</code>.<code>MEDI</code> is recommended to be <code>PHOTO</code> rather than <code>ELECTRONIC</code>.</p></div></section><section id="MIME" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>MIME</code> (Media type) <code class="uri">g7:MIME</code></h4><p>Indicates the <a href="#media-type">media type</a> of the payload of the superstructure.</p><p>As of version 7.0, only 2 media types are supported by this structure:</p><ul><li><p><code>text/plain</code> shall be presented to the user as-is, preserving all spacing, line breaks, and so forth.</p></li><li><p><code>text/html</code> uses HTML tags to provide presentation information. Applications should support at least the following:</p><ul><li><code>p</code> and <code>br</code> elements for paragraphing and line breaks.</li><li><code>b</code>, <code>i</code>, <code>u</code>, and <code>s</code> elements for bold, italic, underlined, and strike-through text (or corresponding display in other locales; see <a href="https://html.spec.whatwg.org/multipage/text-level-semantics.html">HTML §4.5</a> for more).</li><li><code>sup</code> and <code>sub</code> elements for super- and sub-script.</li><li>The 3 XML entities that appear in text: <code>&amp;amp;</code>, <code>&amp;lt;</code> <code>&amp;gt;</code>. Note that <code>&amp;quote;</code> and <code>&amp;apos;</code> are only needed in attributes. Other entities should be represented as their respective Unicode characters instead.</li></ul><p>Supporting more of HTML is encouraged. Unsupported elements should be ignored during display.</p></li></ul><div class="note"><p>Applications are welcome to support more XML entities or HTML character references in their user interface. However, exporting must only use the core XML entities, translating any other entities into their corresponding Unicode characters.</p></div><div class="note"><p>Applications are welcome to support additional HTML elements, but they should ensure that content is meaningful if those extra elements are ignored and only their content text is displayed.</p></div><div class="note"><p>Media types are also used by external files, as described under <a href="#FORM"><code>FORM</code></a>. External file media types are not limited to <code>text/plain</code> and <code>text/html</code>.</p></div><p>If needed, <code>text/html</code> can be converted to <code>text/plain</code> using the following steps:</p><ol type="1"><li>Replace any sequence of 1 or more spaces, tabs, and line breaks with a single space</li><li>Case-insensitively replace each <code>&lt;p</code>…<code>&gt;</code>, <code>&lt;/p</code>…<code>&gt;</code>, and <code>&lt;br</code>…<code>&gt;</code> with a line break</li><li>Remove all other <code>&lt;</code>…<code>&gt;</code> tags</li><li>Replace each <code>&amp;lt;</code> with <code>&lt;</code> and <code>&amp;gt;</code> with <code>&gt;</code></li><li>Replace each <code>&amp;amp;</code> with <code>&amp;</code></li></ol></section><section id="NAME" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NAME</code> (Name) <code class="uri">g7:NAME</code></h4><p>The name of the superstructure’s subject, represented as a simple string.</p></section><section id="INDI-NAME" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NAME</code> (Name) <code class="uri">g7:INDI-NAME</code></h4><p>A <a href="#PERSONAL_NAME_STRUCTURE"><code>PERSONAL_NAME_STRUCTURE</code></a> with parts, translations, sources, and so forth.</p></section><section id="NATI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NATI</code> (Nationality) <code class="uri">g7:NATI</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="NATU" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NATU</code> (Naturalization) <code class="uri">g7:NATU</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="FAM-NCHI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NCHI</code> (Number of children) <code class="uri">g7:FAM-NCHI</code></h4><p>A <a href="#family-attributes">Family Attribute</a>. See also <a href="#FAMILY_ATTRIBUTE_STRUCTURE"><code>FAMILY_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="INDI-NCHI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NCHI</code> (Number of children) <code class="uri">g7:INDI-NCHI</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE" class="close"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="NICK" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NICK</code> (Nickname) <code class="uri">g7:NICK</code></h4><p>A descriptive or familiar name that is used instead of, or in addition to, one’s official or legal name.</p><div class="note"><p>The label “nickname” and description text of this structure were introduced with version 5.5 in 1996, but are understood differently by different users. Some use <a href="#NICK" class="close"><code>NICK</code></a> only for names that would be inappropriate in formal settings. Some use it for pseudonyms regardless of where they are used. Some use it for any variant of a name that is not the one used on legal documents. Because all of these uses, and likely others as well, are common in existing data, no further clarification of the meaning of the <a href="#NICK" class="close"><code>NICK</code></a> structure is possible without contradicting some existing data.</p></div></section><section id="NMR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NMR</code> (Number of marriages) <code class="uri">g7:NMR</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE" class="close"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="NO" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NO</code> (Did not happen) <code class="uri">g7:NO</code></h4><p>An enumerated value from set <a href="#enumset-EVEN"><code>g7:enumset-EVEN</code></a> identifying an event type which did not occur to the superstructure’s subject. A specific payload <code>NO XYZ</code> should only appear where <code>XYZ</code> would be legal.</p><p>See <a href="#NON_EVENT_STRUCTURE" class="close"><code>NON_EVENT_STRUCTURE</code></a> for more details.</p></section><section id="NOTE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NOTE</code> (Note) <code class="uri">g7:NOTE</code></h4><p>A <a href="#NOTE_STRUCTURE"><code>NOTE_STRUCTURE</code></a>, containing additional information provided by the submitter for understanding the enclosing data.</p><p>When a substructure of <a href="#HEAD"><code>HEAD</code></a>, it should describe the contents of the document in terms of “ancestors or descendants of” so that the person receiving the data knows what genealogical information the document contains.</p></section><section id="NPFX" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NPFX</code> (Name prefix) <code class="uri">g7:NPFX</code></h4><p>Text that appears on a name line before the given and surname parts of a name.</p></section><section id="NSFX" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>NSFX</code> (Name suffix) <code class="uri">g7:NSFX</code></h4><p>Text which appears on a name line after or behind the given and surname parts of a name.</p></section><section id="OBJE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>OBJE</code> (Object) <code class="uri">g7:OBJE</code></h4><p>See <a href="#MULTIMEDIA_LINK"><code>MULTIMEDIA_LINK</code></a>.</p></section><section id="record-OBJE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>OBJE</code> (Object) <code class="uri">g7:record-OBJE</code></h4><p>See <a href="#MULTIMEDIA_RECORD"><code>MULTIMEDIA_RECORD</code></a>.</p></section><section id="OCCU" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>OCCU</code> (Occupation) <code class="uri">g7:OCCU</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="ORDN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ORDN</code> (Ordination) <code class="uri">g7:ORDN</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="PAGE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PAGE</code> (Page) <code class="uri">g7:PAGE</code></h4><p>A specific location within the information referenced. For a published work, this could include the volume of a multi-volume work and the page number or numbers. For a periodical, it could include volume, issue, and page numbers. For a newspaper, it could include a date, page number, and column number. For an unpublished source or microfilmed works, this could be a film or sheet number, page number, or frame number. A census record might have an enumerating district, page number, line number, dwelling number, and family number.</p><p>It is recommended that the data in this field be formatted comma-separated with label: value pairs</p><div class="example"><div class="sourceCode" id="cb82"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb82-1"><a href="#cb82-1"></a><span class="dt">2 </span><span class="fu">SOUR </span><span class="va">@S1@</span></span>
 <span id="cb82-2"><a href="#cb82-2"></a><span class="dt">3 </span><span class="fu">PAGE </span>Film: 1234567, Frame: 344, Line: 28</span></code></pre></div></div><p>If the superstructure’s pointer is <code>@VOID@</code> then there is no information referenced and the <a href="#PAGE" class="close"><code>PAGE</code></a> may describe the entire source.</p><div class="example"><div class="sourceCode" id="cb83"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb83-1"><a href="#cb83-1"></a><span class="dt">1 </span><span class="fu">DSCR </span>Tall enough his head touched the ceiling</span>
 <span id="cb83-2"><a href="#cb83-2"></a><span class="dt">2 </span><span class="fu">SOUR </span><span class="va">@VOID@</span></span>
 <span id="cb83-3"><a href="#cb83-3"></a><span class="dt">3 </span><span class="fu">PAGE </span>His grand-daughter Lydia told me this in 1980</span></code></pre></div></div></section><section id="PEDI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PEDI</code> (Pedigree) <code class="uri">g7:PEDI</code></h4><p>An enumerated value from set <a href="#enumset-PEDI"><code>g7:enumset-PEDI</code></a> indicating the type of child-to-family relationship represented by the superstructure.</p></section><section id="PHON" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PHON</code> (Phone) <code class="uri">g7:PHON</code></h4><p>A telephone number. Telephone numbers have many regional variations and can contain non-digit characters. Users should be encouraged to use internationalized telephone numbers rather than local versions. As a starting point for this recommendation, there are international standards that use a “‘+’” shorthand for the international prefix (for example, in place of “011” in the US or “00” in the UK). Examples are <code>+1 (555) 555-1234</code> (US) or <code>+44 20 1234 1234</code> (UK).</p><p>See ITU standards <a href="https://www.itu.int/rec/T-REC-E.123">E.123</a> and <a href="https://www.itu.int/rec/T-REC-E.164">E.164</a> for more information.</p></section><section id="PHRASE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PHRASE</code> (Phrase) <code class="uri">g7:PHRASE</code></h4><p>Textual information that cannot be expressed in the superstructure due to the limitations of its data type. A <a href="#PHRASE" class="close"><code>PHRASE</code></a> may restate information contained in the superstructure, but doing so is not recommended unless it is needed for clarity.</p><div class="example"><p>A date interpreted from the phrase “The Feast of St John” might be</p><div class="sourceCode" id="cb84"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb84-1"><a href="#cb84-1"></a><span class="dt">2 </span><span class="fu">DATE </span>24 JUN 1852</span>
@@ -1143,7 +1143,7 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb88-4"><a href="#cb88-4"></a><span class="dt">4 </span><span class="fu">PHRASE </span>Maid of Honor</span></code></pre></div></div><div class="example"><p>A name given to a foundling orphan might be</p><div class="sourceCode" id="cb89"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb89-1"><a href="#cb89-1"></a><span class="dt">1 </span><span class="fu">NAME </span>Mary //</span>
 <span id="cb89-2"><a href="#cb89-2"></a><span class="dt">2 </span><span class="fu">GIVN </span>Mary</span>
 <span id="cb89-3"><a href="#cb89-3"></a><span class="dt">2 </span><span class="fu">TYPE </span>OTHER</span>
-<span id="cb89-4"><a href="#cb89-4"></a><span class="dt">3 </span><span class="fu">PHRASE </span>given by orphanage</span></code></pre></div></div></section><section id="PLAC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PLAC</code> (Place) <code class="uri">g7:PLAC</code></h4><p>The principal place in which the superstructure’s subject occurred, represented as a <a href="#list">List</a> of jurisdictional entities in a sequence from the lowest to the highest jurisdiction. As with other lists, the jurisdictions are separated by commas. Any jurisdiction’s name that is missing is still accounted for by an empty string in the list.</p><p>The type of each jurisdiction is given in the <a href="#PLAC-FORM"><code>PLAC</code>.<code>FORM</code></a> substructure, if present, or in the <a href="#HEAD-PLAC-FORM"><code>HEAD</code>.<code>PLAC</code>.<code>FORM</code></a> structure. If neither is present, the jurisdictional types are unspecified beyond the lowest-to-highest order noted above.</p></section><section id="HEAD-PLAC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PLAC</code> (Place) <code class="uri">g7:HEAD-PLAC</code></h4><p>This is a placeholder for providing a default <a href="#PLAC-FORM" class="close"><code>PLAC</code>.<code>FORM</code></a>, and must not have a payload.</p></section><section id="POST" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>POST</code> (Postal code) <code class="uri">g7:POST</code></h4><p>A code used by a postal service to identify an area to facilitate mail handling. See <a href="#ADDRESS_STRUCTURE"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></section><section id="PROB" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PROB</code> (Probate) <code class="uri">g7:PROB</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="PROP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PROP</code> (Property) <code class="uri">g7:PROP</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="PUBL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PUBL</code> (Publication) <code class="uri">g7:PUBL</code></h4><p>When and where the record was created. For published works, this includes information such as the city of publication, name of the publisher, and year of publication.</p><p>For an unpublished work, it includes the date the record was created and the place where it was created, such as the county and state of residence of a person making a declaration for a pension or the city and state of residence of the writer of a letter.</p></section><section id="QUAY" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>QUAY</code> (Quality of data) <code class="uri">g7:QUAY</code></h4><p>An enumerated value from set <a href="#enumset-QUAY"><code>g7:enumset-QUAY</code></a> indicating the credibility of a piece of information, based on its supporting evidence. Some systems use this feature to rank multiple conflicting opinions for display of most likely information first. It is not intended to eliminate the receivers’ need to evaluate the evidence for themselves.</p></section><section id="REFN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>REFN</code> (Reference) <code class="uri">g7:REFN</code></h4><p>A user-defined number or text that the submitter uses to identify the superstructure. For instance, it may be a record number within the submitter’s automated or manual system, or it may be a page and position number on a pedigree chart.</p><p>This is metadata about the structure itself, not data about its subject. Multiple structures describing different aspects of the same subject must not have the same <a href="#REFN" class="close"><code>REFN</code></a> value.</p></section><section id="RELI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RELI</code> (Religion) <code class="uri">g7:RELI</code></h4><p>A religious denomination associated with the event or attribute described by the superstructure.</p></section><section id="INDI-RELI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RELI</code> (Religion) <code class="uri">g7:INDI-RELI</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="RESN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RESN</code> (Restriction) <code class="uri">g7:RESN</code></h4><p>A <a href="#list">List</a> of enumerated values from set <a href="#enumset-RESN"><code>g7:enumset-RESN</code></a> signifying access to information may be denied or otherwise restricted.</p><p>The <a href="#RESN" class="close"><code>RESN</code></a> structure is provided to assist software in filtering data that should not be exported or otherwise used in a particular context. It is recommended that tools provide an interface to allow users to filter data on export such that certain <a href="#RESN" class="close"><code>RESN</code></a> structure payload entries result in the <a href="#RESN" class="close"><code>RESN</code></a> structure and its superstructure being removed from the export. Such removal must abide by some constraints: see <a href="#removing-data">Removing data</a> for more details.</p><p>This is metadata about the structure itself, not data about its subject.</p></section><section id="REPO" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>REPO</code> (Repository) <code class="uri">g7:REPO</code></h4><p>See <a href="#SOURCE_REPOSITORY_CITATION"><code>SOURCE_REPOSITORY_CITATION</code></a>.</p></section><section id="record-REPO" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>REPO</code> (Repository) <code class="uri">g7:record-REPO</code></h4><p>See <a href="#REPOSITORY_RECORD"><code>REPOSITORY_RECORD</code></a>.</p></section><section id="FAM-RESI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RESI</code> (Residence) <code class="uri">g7:FAM-RESI</code></h4><p>A <a href="#family-attributes">Family Attribute</a>. See also <a href="#FAMILY_ATTRIBUTE_STRUCTURE"><code>FAMILY_ATTRIBUTE_STRUCTURE</code></a>.</p><p>See <a href="#INDI-RESI" class="close"><code>g7:INDI-RESI</code></a> for comments on the use of payload strings in <a href="#family-attributes"><code>RESI</code></a> structures.</p></section><section id="INDI-RESI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RESI</code> (Residence) <code class="uri">g7:INDI-RESI</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p><p>Where possible, the residence should be identified in <a href="#PLAC"><code>PLAC</code></a> and/or <a href="#ADDR"><code>ADDR</code></a> substructures of the <a href="#family-attributes" class="close"><code>RESI</code></a> structure. The payload text should not duplicate <a href="#PLAC" class="close"><code>PLAC</code></a> or <a href="#ADDR" class="close"><code>ADDR</code></a> information, but may be used for residence information that cannot be expressed by those structures.</p><div class="example"><p>The following two examples show situations where a <a href="#family-attributes" class="close"><code>RESI</code></a> payload may be appropriate:</p><div class="sourceCode" id="cb90"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb90-1"><a href="#cb90-1"></a><span class="dt">1 </span><span class="fu">RESI </span>living with an aunt</span>
+<span id="cb89-4"><a href="#cb89-4"></a><span class="dt">3 </span><span class="fu">PHRASE </span>given by orphanage</span></code></pre></div></div></section><section id="PLAC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PLAC</code> (Place) <code class="uri">g7:PLAC</code></h4><p>The principal place in which the superstructure’s subject occurred, represented as a <a href="#list">List</a> of jurisdictional entities in a sequence from the lowest to the highest jurisdiction, where “jurisdiction” includes units in a political, ecclesiastical, and geographical hierarchies and may include units of any size, such as a continent, “at sea”, or a specific building, farm, or cemetery. As with other lists, the jurisdictions are separated by commas. Any jurisdiction’s name that is missing is still accounted for by an empty string in the list.</p><p>The type of each jurisdiction is given in the <a href="#PLAC-FORM"><code>PLAC</code>.<code>FORM</code></a> substructure, if present, or in the <a href="#HEAD-PLAC-FORM" class="close"><code>HEAD</code>.<code>PLAC</code>.<code>FORM</code></a> structure. If neither is present, the jurisdictional types are unspecified beyond the lowest-to-highest order noted above.</p></section><section id="HEAD-PLAC" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PLAC</code> (Place) <code class="uri">g7:HEAD-PLAC</code></h4><p>This is a placeholder for providing a default <a href="#PLAC-FORM" class="close"><code>PLAC</code>.<code>FORM</code></a>, and must not have a payload.</p></section><section id="POST" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>POST</code> (Postal code) <code class="uri">g7:POST</code></h4><p>A code used by a postal service to identify an area to facilitate mail handling. See <a href="#ADDRESS_STRUCTURE"><code>ADDRESS_STRUCTURE</code></a> for more details.</p></section><section id="PROB" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PROB</code> (Probate) <code class="uri">g7:PROB</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="PROP" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PROP</code> (Property) <code class="uri">g7:PROP</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="PUBL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>PUBL</code> (Publication) <code class="uri">g7:PUBL</code></h4><p>When and where the record was created. For published works, this includes information such as the city of publication, name of the publisher, and year of publication.</p><p>For an unpublished work, it includes the date the record was created and the place where it was created, such as the county and state of residence of a person making a declaration for a pension or the city and state of residence of the writer of a letter.</p></section><section id="QUAY" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>QUAY</code> (Quality of data) <code class="uri">g7:QUAY</code></h4><p>An enumerated value from set <a href="#enumset-QUAY"><code>g7:enumset-QUAY</code></a> indicating the credibility of a piece of information, based on its supporting evidence. Some systems use this feature to rank multiple conflicting opinions for display of most likely information first. It is not intended to eliminate the receivers’ need to evaluate the evidence for themselves.</p></section><section id="REFN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>REFN</code> (Reference) <code class="uri">g7:REFN</code></h4><p>A user-defined number or text that the submitter uses to identify the superstructure. For instance, it may be a record number within the submitter’s automated or manual system, or it may be a page and position number on a pedigree chart.</p><p>This is metadata about the structure itself, not data about its subject. Multiple structures describing different aspects of the same subject must not have the same <a href="#REFN" class="close"><code>REFN</code></a> value.</p></section><section id="RELI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RELI</code> (Religion) <code class="uri">g7:RELI</code></h4><p>A religious denomination associated with the event or attribute described by the superstructure.</p></section><section id="INDI-RELI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RELI</code> (Religion) <code class="uri">g7:INDI-RELI</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p></section><section id="RESN" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RESN</code> (Restriction) <code class="uri">g7:RESN</code></h4><p>A <a href="#list">List</a> of enumerated values from set <a href="#enumset-RESN"><code>g7:enumset-RESN</code></a> signifying access to information may be denied or otherwise restricted.</p><p>The <a href="#RESN" class="close"><code>RESN</code></a> structure is provided to assist software in filtering data that should not be exported or otherwise used in a particular context. It is recommended that tools provide an interface to allow users to filter data on export such that certain <a href="#RESN" class="close"><code>RESN</code></a> structure payload entries result in the <a href="#RESN" class="close"><code>RESN</code></a> structure and its superstructure being removed from the export. Such removal must abide by some constraints: see <a href="#removing-data">Removing data</a> for more details.</p><p>This is metadata about the structure itself, not data about its subject.</p></section><section id="REPO" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>REPO</code> (Repository) <code class="uri">g7:REPO</code></h4><p>See <a href="#SOURCE_REPOSITORY_CITATION" class="close"><code>SOURCE_REPOSITORY_CITATION</code></a>.</p></section><section id="record-REPO" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>REPO</code> (Repository) <code class="uri">g7:record-REPO</code></h4><p>See <a href="#REPOSITORY_RECORD" class="close"><code>REPOSITORY_RECORD</code></a>.</p></section><section id="FAM-RESI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RESI</code> (Residence) <code class="uri">g7:FAM-RESI</code></h4><p>A <a href="#family-attributes">Family Attribute</a>. See also <a href="#FAMILY_ATTRIBUTE_STRUCTURE"><code>FAMILY_ATTRIBUTE_STRUCTURE</code></a>.</p><p>See <a href="#INDI-RESI" class="close"><code>g7:INDI-RESI</code></a> for comments on the use of payload strings in <a href="#family-attributes"><code>RESI</code></a> structures.</p></section><section id="INDI-RESI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RESI</code> (Residence) <code class="uri">g7:INDI-RESI</code></h4><p>An <a href="#individual-attributes">Individual Attribute</a>. See also <a href="#INDIVIDUAL_ATTRIBUTE_STRUCTURE"><code>INDIVIDUAL_ATTRIBUTE_STRUCTURE</code></a>.</p><p>Where possible, the residence should be identified in <a href="#PLAC"><code>PLAC</code></a> and/or <a href="#ADDR"><code>ADDR</code></a> substructures of the <a href="#family-attributes" class="close"><code>RESI</code></a> structure. The payload text should not duplicate <a href="#PLAC" class="close"><code>PLAC</code></a> or <a href="#ADDR" class="close"><code>ADDR</code></a> information, but may be used for residence information that cannot be expressed by those structures.</p><div class="example"><p>The following two examples show situations where a <a href="#family-attributes" class="close"><code>RESI</code></a> payload may be appropriate:</p><div class="sourceCode" id="cb90"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb90-1"><a href="#cb90-1"></a><span class="dt">1 </span><span class="fu">RESI </span>living with an aunt</span>
 <span id="cb90-2"><a href="#cb90-2"></a><span class="dt">2 </span><span class="fu">DATE </span>ABT MAR 1894</span></code></pre></div><div class="sourceCode" id="cb91"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb91-1"><a href="#cb91-1"></a><span class="dt">1 </span><span class="fu">RESI </span>in a mobile caravan</span>
 <span id="cb91-2"><a href="#cb91-2"></a><span class="dt">2 </span><span class="fu">PLAC </span>, , Austro-Hungarian Empire</span>
 <span id="cb91-3"><a href="#cb91-3"></a><span class="dt">3 </span><span class="fu">FORM </span>City, County, Country</span></code></pre></div></div></section><section id="RETI" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>RETI</code> (Retirement) <code class="uri">g7:RETI</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="ROLE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>ROLE</code> (Role) <code class="uri">g7:ROLE</code></h4><p>An enumerated value from set <a href="#enumset-ROLE"><code>g7:enumset-ROLE</code></a> indicating what role this person played in an event or person’s life.</p><div class="example"><p>The following indicates a child’s birth record as the source of the mother’s name:</p><div class="sourceCode" id="cb92"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb92-1"><a href="#cb92-1"></a><span class="dt">0 </span><span class="cf">@I1@ </span><span class="fu">INDI</span></span>
@@ -1183,7 +1183,7 @@ <h2 id="toc-title">Contents</h2>
 <span id="cb97-6"><a href="#cb97-6"></a><span class="dt">2 </span><span class="fu">TRAN </span>media/transcript.vtt</span>
 <span id="cb97-7"><a href="#cb97-7"></a><span class="dt">3 </span><span class="fu">FORM </span>text/vtt</span></code></pre></div></div><p>Note that <a href="#FILE-TRAN"><code>FILE</code>.<code>TRAN</code></a> refers to translation to a different digital format, not to translation to a different human language. Files that differ in the human language of their content should each be given their own <a href="#FILE"><code>FILE</code></a> structure.</p></section><section id="TRLR" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>TRLR</code> (Trailer) <code class="uri">g7:TRLR</code></h4><p>A pseudo-structure marking the end of a dataset. See <a href="#the-header">The Header and Trailer</a> for more details.</p></section><section id="TYPE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>TYPE</code> (Type) <code class="uri">g7:TYPE</code></h4><p>A descriptive word or phrase used to further classify the superstructure.</p><p>When both a <a href="#NOTE"><code>NOTE</code></a> and free-text <a href="#TYPE" class="close"><code>TYPE</code></a> are permitted as substructures of the same structure, the displaying systems should always display the <a href="#TYPE" class="close"><code>TYPE</code></a> value when they display the data from the associated structure; <a href="#NOTE" class="close"><code>NOTE</code></a> will typically be visible only in a detailed view.</p><p><a href="#TYPE" class="close"><code>TYPE</code></a> must be used whenever the generic <code>EVEN</code>, <code>FACT</code> and <a href="#IDNO"><code>IDNO</code></a> tags are used. It may also be used for any other event or attribute.</p><p>Using the subordinate <a href="#TYPE" class="close"><code>TYPE</code></a> classification method provides a further classification of the superstructure but does not change its basic meaning.</p><div class="example"><p>A <a href="#ORDN"><code>ORDN</code></a> with a <a href="#TYPE" class="close"><code>TYPE</code></a> could clarify what kind of ordination was performed:</p><div class="sourceCode" id="cb98"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb98-1"><a href="#cb98-1"></a><span class="dt">0 </span><span class="cf">@I1@ </span><span class="fu">INDI</span></span>
 <span id="cb98-2"><a href="#cb98-2"></a><span class="dt">1 </span><span class="fu">ORDN</span></span>
-<span id="cb98-3"><a href="#cb98-3"></a><span class="dt">2 </span><span class="fu">TYPE </span>Bishop</span></code></pre></div><p>This classifies the entry as an ordination as a bishop, which is still a ordination event. The event could be further clarified with <a href="#RELI"><code>RELI</code></a>, <a href="#DATE"><code>DATE</code></a>, and other substructures.</p><p>Other descriptor values might include, for example,</p><ul><li>“Stillborn” as a qualifier to <a href="#BIRT"><code>BIRT</code></a> (birth)</li><li>“Civil” as a qualifier to <a href="#MARR"><code>MARR</code></a> (marriage)</li><li>“College” as a qualifier to <a href="#GRAD"><code>GRAD</code></a> (graduation)</li><li>“Oral” as a qualifier to <a href="#WILL"><code>WILL</code></a></li></ul><p>See also <code>FACT</code> and <code>EVEN</code> for additional examples.</p></div></section><section id="NAME-TYPE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>TYPE</code> (Type) <code class="uri">g7:NAME-TYPE</code></h4><p>An enumerated value from set <a href="#enumset-NAME-TYPE"><code>g7:enumset-NAME-TYPE</code></a> indicating the type of the name.</p></section><section id="EXID-TYPE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>TYPE</code> (Type) <code class="uri">g7:EXID-TYPE</code></h4><p>The authority issuing the <a href="#EXID"><code>EXID</code></a>, represented as a URI. It is recommended that this be a URL.</p><p>If the authority maintains stable URLs for each identifier it issues, it is recommended that the <a href="#TYPE"><code>TYPE</code></a> payload be selected such that appending the <a href="#EXID" class="close"><code>EXID</code></a> payload to it yields that URL. However, this is not required and a different URI for the set of issued identifiers may be used instead.</p><p>Registered URIs are listed in <a href="https://github.com/FamilySearch/GEDCOM/blob/main/exid-types.json">exid-types.json</a>, where fields include:</p><ul><li>“label”: a short string suitable for display in a user interface.</li><li>“type”: The URI representing the authority issuing the <a href="#EXID" class="close"><code>EXID</code></a>.</li><li>“description”: A description of the meaning of the <a href="#EXID" class="close"><code>EXID</code></a>.</li><li>“contact”: A contact email address for the person or organization registering the URI.</li><li>“change-controller”: The name or contact information for the person or organization authorized to update the registration.</li><li>“fragment”: If present, indicates a short string that can be used as a label for a fragment identifier appended to the URI. If absent, indicates that fragment identifiers are not used with the URI.</li><li>“reference”: A URL with more information about the meaning of the <a href="#EXID" class="close"><code>EXID</code></a>. Such information should explain the uniqueness and expected durability of the identifier.</li></ul><p>Additional type URIs can be registered by filing a <a href="https://github.com/FamilySearch/GEDCOM/pulls">GitHub pull request</a>.</p></section><section id="UID" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>UID</code> (Unique Identifier) <code class="uri">g7:UID</code></h4><p>A globally-unique identifier of the superstructure, to be preserved across edits. If a globally-unique identifier for the record already exists, it should be used without modification, not even whitespace or letter case normalization. New globally unique identifiers should be created and formatted as described in <a href="https://www.rfc-editor.org/info/rfc4122">RFC 4122</a>.</p><p>This is metadata about the structure itself, not data about its subject. Multiple structures describing different aspects of the same subject would have different <a href="#UID" class="close"><code>UID</code></a> values.</p><p>Because the <a href="#UID" class="close"><code>UID</code></a> identifies a structure, it can facilitate inter-tool collaboration by distinguishing between a structure being edited and a new structure being created. If an application allows structures to be edited in a way that completely changes their meaning (e.g., changing all the contents of an <code>INDI</code> record to have it describe a completely different person) then any <a href="#UID" class="close"><code>UID</code></a>s should also be changed.</p><div class="note"><p>Some systems used a 16-byte UUID with a custom 2-byte checksum for a total of 18 bytes:</p><ul><li>checksum byte 1 = (sum of (byte<sub><em>i</em></sub>) for <em>i</em> 1 through 16) mod 256</li><li>checksum byte 2 = (sum of ((16 − <em>i</em>) × (byte<sub><em>i</em></sub>)) for <em>i</em> 1 through 16) mod 256</li></ul><p>Use of checksums for UIDs is discouraged except in cases where error-prone input is expected and an appropriate action to take in case of an error is known.</p></div></section><section id="VERS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>VERS</code> (Version) <code class="uri">g7:VERS</code></h4><p>An identifier that represents the version level assigned to the associated product. It is defined and changed by the creators of the product.</p></section><section id="GEDC-VERS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>VERS</code> (Version) <code class="uri">g7:GEDC-VERS</code></h4><p>The version number of the official specification that this document’s data conforms to. This must include the major and minor version (for example, “<code>7.0</code>”); it may include the patch as well (for example, “<code>7.0.1</code>”), but doing so is not required. See <a href="#a-guide-to-version-numbers">A Guide to Version Numbers</a> for more details about version numbers.</p></section><section id="WIDTH" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WIDTH</code> (Width in pixels) <code class="uri">g7:WIDTH</code></h4><p>How many pixels to display horizontally for the image. See <a href="#CROP"><code>CROP</code></a> for more details.</p></section><section id="WIFE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WIFE</code> (Wife) <code class="uri">g7:WIFE</code></h4><p>A container for information relevant to the subject of the superstructure specific to the individual described by the associated <code>FAM</code>’s <a href="#WIFE" class="close"><code>WIFE</code></a> substructure.</p></section><section id="FAM-WIFE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WIFE</code> (Wife) <code class="uri">g7:FAM-WIFE</code></h4><p>A partner in a <code>FAM</code> record. See <a href="#FAMILY_RECORD"><code>FAMILY_RECORD</code></a> for more details.</p></section><section id="WILL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WILL</code> (Will) <code class="uri">g7:WILL</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="WWW" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WWW</code> (Web address) <code class="uri">g7:WWW</code></h4><p>A URL or other locator for a World Wide Web page, as defined by any relevant standard such as <a href="https://url.spec.whatwg.org/">whatwg/url</a>, <a href="https://www.rfc-editor.org/info/rfc3986">RFC 3986</a>, <a href="https://www.rfc-editor.org/info/rfc3987">RFC 3987</a>, and so forth.</p><p>If an invalid or no longer existing web address is present upon import, it should be preserved as-is on export.</p></section></section></section><section id="enumeration-values" data-number="3.4"><h2 data-number="3.4"><span class="header-section-number">3.4</span> Enumeration Values</h2><p>Unless otherwise specified in the enumeration description in this section, each enumeration value defined in this section has a URI constructed by concatenating <code>g7:enum-</code> to the enumeration value; for example, the <a href="#HUSB"><code>HUSB</code></a> enumeration value has the URI <code>http://gedcom.io/terms/v7/enum-HUSB</code>.</p><p>Each set of enumeration values has its own URI.</p><section id="enumset-ADOP" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-ADOP</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>HUSB</code></td><td style="text-align: left;">Adopted by the <code>HUSB</code> of the <code>FAM</code> pointed to by <code>FAMC</code>.<br />The URI of this value is <code>g7:enum-ADOP-HUSB</code></td></tr><tr class="even"><td style="text-align: left;"><code>WIFE</code></td><td style="text-align: left;">Adopted by the <code>WIFE</code> of the <code>FAM</code> pointed to by <code>FAMC</code>.<br />The URI of this value is <code>g7:enum-ADOP-WIFE</code></td></tr><tr class="odd"><td style="text-align: left;"><code>BOTH</code></td><td style="text-align: left;">Adopted by both <code>HUSB</code> and <code>WIFE</code> of the <code>FAM</code> pointed to by <code>FAMC</code></td></tr></tbody></table></section><section id="enumset-EVEN" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-EVEN</code></h3><p>An event-type tag name, but not the generic <code>EVEN</code> tag. See <a href="#events">Events</a>.</p><p>Most values in this enumeration set use the same tag and URI as the corresponding event, except for tags used with different URIs for <code>FAM</code> vs <code>INDI</code>; these are given generic definitions with URIs constructed by concatenating <code>g7:enum-</code> to the enumeration value:</p><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>CENS</code></td><td style="text-align: left;">A census event; either <a href="#INDI-CENS"><code>g7:INDI-CENS</code></a> or <a href="#FAM-CENS"><code>g7:FAM-CENS</code></a></td></tr></tbody></table></section><section id="enumset-EVENATTR" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-EVENATTR</code></h3><p>An event- or attribute-type tag name. See <a href="#events">Events</a> and <a href="#attributes">Attributes</a>.</p><p>Most values in this enumeration set use the same tag and URI as the corresponding event or attribute, except for tags used with different URIs for <code>FAM</code> vs <code>INDI</code>; these are given generic definitions with URIs constructed by concatenating <code>g7:enum-</code> to the enumeration value:</p><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>CENS</code></td><td style="text-align: left;">A census event; either <a href="#INDI-CENS" class="close"><code>g7:INDI-CENS</code></a> or <a href="#FAM-CENS" class="close"><code>g7:FAM-CENS</code></a></td></tr><tr class="even"><td style="text-align: left;"><code>NCHI</code></td><td style="text-align: left;">A count of children; either <a href="#INDI-NCHI"><code>g7:INDI-NCHI</code></a> or <a href="#FAM-NCHI"><code>g7:FAM-NCHI</code></a></td></tr><tr class="odd"><td style="text-align: left;"><code>RESI</code></td><td style="text-align: left;">A residence attribute; either <a href="#INDI-RESI"><code>g7:INDI-RESI</code></a> or <a href="#FAM-RESI"><code>g7:FAM-RESI</code></a></td></tr><tr class="even"><td style="text-align: left;"><code>FACT</code></td><td style="text-align: left;">A generic attribute; either <a href="#INDI-FACT"><code>g7:INDI-FACT</code></a> or <a href="#FAM-FACT"><code>g7:FAM-FACT</code></a></td></tr><tr class="odd"><td style="text-align: left;"><code>EVEN</code></td><td style="text-align: left;">A generic event; either <a href="#INDI-EVEN"><code>g7:INDI-EVEN</code></a> or <a href="#FAM-EVEN"><code>g7:FAM-EVEN</code></a></td></tr></tbody></table></section><section id="enumset-MEDI" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-MEDI</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>AUDIO</code></td><td style="text-align: left;">An audio recording</td></tr><tr class="even"><td style="text-align: left;"><code>BOOK</code></td><td style="text-align: left;">A bound book</td></tr><tr class="odd"><td style="text-align: left;"><code>CARD</code></td><td style="text-align: left;">A card or file entry</td></tr><tr class="even"><td style="text-align: left;"><code>ELECTRONIC</code></td><td style="text-align: left;">A digital artifact</td></tr><tr class="odd"><td style="text-align: left;"><code>FICHE</code></td><td style="text-align: left;">Microfiche</td></tr><tr class="even"><td style="text-align: left;"><code>FILM</code></td><td style="text-align: left;">Microfilm</td></tr><tr class="odd"><td style="text-align: left;"><code>MAGAZINE</code></td><td style="text-align: left;">Printed periodical</td></tr><tr class="even"><td style="text-align: left;"><code>MANUSCRIPT</code></td><td style="text-align: left;">Written pages</td></tr><tr class="odd"><td style="text-align: left;"><code>MAP</code></td><td style="text-align: left;">Cartographic map</td></tr><tr class="even"><td style="text-align: left;"><code>NEWSPAPER</code></td><td style="text-align: left;">Printed newspaper</td></tr><tr class="odd"><td style="text-align: left;"><code>PHOTO</code></td><td style="text-align: left;">Photograph</td></tr><tr class="even"><td style="text-align: left;"><code>TOMBSTONE</code></td><td style="text-align: left;">Burial marker or related memorial</td></tr><tr class="odd"><td style="text-align: left;"><code>VIDEO</code></td><td style="text-align: left;">Motion picture recording</td></tr><tr class="even"><td style="text-align: left;"><code>OTHER</code></td><td style="text-align: left;">A value not listed here; should have a <code>PHRASE</code> substructure</td></tr></tbody></table></section><section id="enumset-PEDI" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-PEDI</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>ADOPTED</code></td><td style="text-align: left;">Adoptive parents</td></tr><tr class="even"><td style="text-align: left;"><code>BIRTH</code></td><td style="text-align: left;">Family structure at time of birth</td></tr><tr class="odd"><td style="text-align: left;"><code>FOSTER</code></td><td style="text-align: left;">The child was included in a foster or guardian family</td></tr><tr class="even"><td style="text-align: left;"><code>SEALING</code></td><td style="text-align: left;">The child was sealed to parents other than birth parents</td></tr><tr class="odd"><td style="text-align: left;"><code>OTHER</code></td><td style="text-align: left;">A value not listed here; should have a <code>PHRASE</code> substructure</td></tr></tbody></table><div class="note"><p>It is known that some users have interpreted <code>BIRTH</code> to mean “genetic parent” and others to mean “social parent at time of birth”. Definitions differ in many circumstances (infidelity, surrogacy, sperm donation, and so on). Hence, applications should refrain from asserting it has either meaning in imported data.</p></div><div class="note"><p>The structures for foster children in particular, and family relationships in general, are known to have undesirable limitations and are likely to change in a future version of this specification.</p></div><div class="note"><p><code>SEALING</code> implies that a <a href="#SLGC"><code>SLGC</code></a> event was performed, and it is recommended that this enumeration value only be used when the <a href="#SLGC" class="close"><code>SLGC</code></a> event is present in the GEDCOM file. <code>ADOPTED</code>, on the other hand, only implies a social relationship which may or may not have any associated <a href="#ADOP" class="close"><code>ADOP</code></a> event.</p></div></section><section id="enumset-QUAY" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-QUAY</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>0</code></td><td style="text-align: left;">Unreliable evidence or estimated data</td></tr><tr class="even"><td style="text-align: left;"><code>1</code></td><td style="text-align: left;">Questionable reliability of evidence (interviews, census, oral genealogies, or potential for bias, such as an autobiography)</td></tr><tr class="odd"><td style="text-align: left;"><code>2</code></td><td style="text-align: left;">Secondary evidence, data officially recorded sometime after the event</td></tr><tr class="even"><td style="text-align: left;"><code>3</code></td><td style="text-align: left;">Direct and primary evidence used, or by dominance of the evidence</td></tr></tbody></table><p>Although the values look like integers, they do not have numeric meaning.</p><div class="note"><p>The structures for representing the strength of and confidence in various claims are known to be inadequate and are likely to change in a future version of this specification.</p></div></section><section id="enumset-RESN" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-RESN</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>CONFIDENTIAL</code></td><td style="text-align: left;">This data was marked as confidential by the user.</td></tr><tr class="even"><td style="text-align: left;"><code>LOCKED</code></td><td style="text-align: left;">Some systems may ignore changes to this data.</td></tr><tr class="odd"><td style="text-align: left;"><code>PRIVACY</code></td><td style="text-align: left;">This data is not to be shared outside of a trusted circle, generally because it contains information about living individuals. This definition is known to admit multiple interpretations, so use of the <code>PRIVACY</code> restriction notice is not recommended.</td></tr></tbody></table><p>It is recommended that applications allow users to chose how <code>CONFIDENTIAL</code> and/or <code>PRIVACY</code> data is handled when interfacing with other users or applications, for example by allowing them to exclude such data when exporting.</p><p>When a <a href="#list">List</a> of <a href="#RESN"><code>RESN</code></a> enumeration values are present, all apply.</p><div class="example"><p>The line <code>1 RESN CONFIDENTIAL, LOCKED</code> means the superstructure’s data is both considered confidential <em>and</em> read-only.</p></div><p>Since <a href="#RESN" class="close"><code>RESN</code></a> was introduced in version 5.5 the intent of the <code>PRIVACY</code> value has been interpreted differently by different applications. Known interpretations include</p><ul><li>Some assign <code>PRIVACY</code> by algorithm or policy, unlike the user-assigned <code>CONFIDENTIAL</code></li><li>Some use <code>PRIVACY</code> to mark records that have already had private data removed</li><li>Some use the English definitions of “privacy” and “confidential” to inform different restrictions for each</li></ul><p>There may also be applications using <code>PRIVACY</code> with interpretations not listed above.</p><p>Because these different interpretations became widespread before they were identified, determining which one is meant generally requires knowledge of which application applied the <code>PRIVACY</code> restriction notice. It is anticipated that a future version will deprecate the <code>PRIVACY</code> option and introduce new values for each of its current use cases.</p></section><section id="enumset-ROLE" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-ROLE</code></h3><table><thead><tr class="header"><th>Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td><code>CHIL</code></td><td style="text-align: left;">Child</td></tr><tr class="even"><td><code>CLERGY</code></td><td style="text-align: left;">Religious official in event; implies <code>OFFICIATOR</code></td></tr><tr class="odd"><td><code>FATH</code></td><td style="text-align: left;">Father; implies <code>PARENT</code></td></tr><tr class="even"><td><code>FRIEND</code></td><td style="text-align: left;">Friend</td></tr><tr class="odd"><td><code>GODP</code></td><td style="text-align: left;">Godparent or related role in other religions</td></tr><tr class="even"><td><code>HUSB</code></td><td style="text-align: left;">Husband; implies <code>SPOU</code></td></tr><tr class="odd"><td><code>MOTH</code></td><td style="text-align: left;">Mother; implies <code>PARENT</code></td></tr><tr class="even"><td><code>MULTIPLE</code></td><td style="text-align: left;">A sibling from the same pregnancy (twin, triplet, quadruplet, and so on). A <code>PHRASE</code> can be used to specify the kind of multiple birth.</td></tr><tr class="odd"><td><code>NGHBR</code></td><td style="text-align: left;">Neighbor</td></tr><tr class="even"><td><code>OFFICIATOR</code></td><td style="text-align: left;">Officiator of the event</td></tr><tr class="odd"><td><code>PARENT</code></td><td style="text-align: left;">Parent</td></tr><tr class="even"><td><code>SPOU</code></td><td style="text-align: left;">Spouse</td></tr><tr class="odd"><td><code>WIFE</code></td><td style="text-align: left;">Wife; implies <code>SPOU</code></td></tr><tr class="even"><td><code>WITN</code></td><td style="text-align: left;">Witness</td></tr><tr class="odd"><td><code>OTHER</code></td><td style="text-align: left;">A value not listed here; should have a <code>PHRASE</code> substructure</td></tr></tbody></table><p>These should be interpreted in the context of the recorded event and its primary participants. For example, if you cite a child’s birth record as the source of the mother’s name, the value for this field is “<code>MOTH</code>.” If you describe the groom of a marriage, the role is “<a href="#HUSB"><code>HUSB</code></a>.”</p></section><section id="enumset-SEX" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-SEX</code></h3><table><thead><tr class="header"><th>Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td><code>M</code></td><td style="text-align: left;">Male</td></tr><tr class="even"><td><code>F</code></td><td style="text-align: left;">Female</td></tr><tr class="odd"><td><code>X</code></td><td style="text-align: left;">Does not fit the typical definition of only Male or only Female</td></tr><tr class="even"><td><code>U</code></td><td style="text-align: left;">Cannot be determined from available sources</td></tr></tbody></table><p>This can describe an individual’s reproductive or sexual anatomy at birth. Related concepts of gender identity or sexual preference are not currently given their own tag. Cultural or personal gender preference may be indicated using the <code>FACT</code> tag.</p></section><section id="enumset-FAMC-STAT" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-FAMC-STAT</code></h3><table><thead><tr class="header"><th>Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td><code>CHALLENGED</code></td><td style="text-align: left;">Linking this child to this family is suspect, but the linkage has been neither proven nor disproven.</td></tr><tr class="even"><td><code>DISPROVEN</code></td><td style="text-align: left;">There has been a claim by some that this child belongs to this family, but the linkage has been disproven.</td></tr><tr class="odd"><td><code>PROVEN</code></td><td style="text-align: left;">Linking this child to this family has been proven.</td></tr></tbody></table><p>When these enumeration values were introduced in version 5.5.1 it was assumed, but never specified, that “proven” referred to <a href="https://www.familysearch.org/en/wiki/Genealogical_Proof_Standard">the definition provided by the Board for Certification of Genealogists</a>. Because that meaning was not specified and other definitions of “proven” exist, existing files might use these values in other ways.</p><div class="note"><p>The structures for representing the strength of and confidence in various claims are known to be inadequate and are likely to change in a future version of this specification.</p></div></section><section id="enumset-ord-STAT" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-ord-STAT</code></h3><p>These values were formerly used by The Church of Jesus Christ of Latter-day Saints for coordinating between temples and members. They are no longer used in that way, meaning their interpretation is subject to individual user interpretation</p><p>The definition of some of these values combined with the official policies of the church mean that some values only make sense under a subset of <a href="#latter-day-saint-ordinances">ordinance structures</a>. These contexts are identified in the “applies to” column below, and it is recommended that applications follow those guidelines. These recommendations were not present when these enumeration values were first introduced in version 5.3 so uses that do not conform to the “applies to” guidelines may be encountered; if so, they should be treated by applications like any other user-specified but semantically-strange data.</p><p>The definition of some of these values combined with the official policies of the church and the move of the church away from using GEDCOM for handling ordinance requests make them redundant and/or no longer relevant. If so, that is indicated in the “status” column below. Like the “applies to” column, the “status” column is a recommendation, not a requirement, and applications should be prepared to encounter non-current values.</p><table><thead><tr class="header"><th>Value</th><th>Applies to</th><th style="text-align: left;">Meaning</th><th style="text-align: left;">Status</th></tr></thead><tbody><tr class="odd"><td><code>BIC</code></td><td><code>SLGC</code></td><td style="text-align: left;">Born in the covenant, so child to parent sealing ordinance is not required.</td><td style="text-align: left;">Current</td></tr><tr class="even"><td><code>CANCELED</code></td><td><code>SLGS</code></td><td style="text-align: left;">Canceled and considered invalid.</td><td style="text-align: left;">Current</td></tr><tr class="odd"><td><code>CHILD</code></td><td>All but <code>SLGC</code></td><td style="text-align: left;">Died before 8 years old, so ordinances other than child to parent sealing are not required.</td><td style="text-align: left;">Current</td></tr><tr class="even"><td><code>COMPLETED</code></td><td>All</td><td style="text-align: left;">Completed, but the date is not known.</td><td style="text-align: left;">Deprecated, use <code>DATE BEF date</code> instead. This status was defined for use with <a href="https://www.churchofjesuschrist.org/study/ensign/1994/02/news-of-the-church/templeready-now-available">TempleReady</a> which is no longer in use.</td></tr><tr class="odd"><td><code>EXCLUDED</code></td><td>All</td><td style="text-align: left;">Patron excluded this ordinance from being cleared in this submission.</td><td style="text-align: left;">Deprecated. This status was defined for use with TempleReady which is no longer in use.</td></tr><tr class="even"><td><code>DNS</code></td><td><code>SLGC</code>, <code>SLGS</code></td><td style="text-align: left;">This ordinance is not authorized.</td><td style="text-align: left;">Current</td></tr><tr class="odd"><td><code>DNS_CAN</code></td><td><code>SLGS</code></td><td style="text-align: left;">This ordinance is not authorized, and the previous ordinance is cancelled.</td><td style="text-align: left;">Current</td></tr><tr class="even"><td><code>INFANT</code></td><td>All but <code>SLGC</code></td><td style="text-align: left;">Died before less than 1 year old, baptism or endowment not required.</td><td style="text-align: left;">Deprecated. Use <code>CHILD</code> instead.</td></tr><tr class="odd"><td><code>PRE_1970</code></td><td>All</td><td style="text-align: left;">Ordinance was likely completed because an ordinance for this person was converted from temple records of work completed before 1970.</td><td style="text-align: left;">Deprecated. Use <code>DATE BEF 1970</code> instead.</td></tr><tr class="even"><td><code>STILLBORN</code></td><td>All</td><td style="text-align: left;">Born dead, so no ordinances are required.</td><td style="text-align: left;">Current</td></tr><tr class="odd"><td><code>SUBMITTED</code></td><td>All</td><td style="text-align: left;">Ordinance was previously submitted.</td><td style="text-align: left;">Deprecated. This status was defined for use with TempleReady which is no longer in use.</td></tr><tr class="even"><td><code>UNCLEARED</code></td><td>All</td><td style="text-align: left;">Data for clearing the ordinance request was insufficient.</td><td style="text-align: left;">Deprecated. This status was defined for use with TempleReady which is no longer in use.</td></tr></tbody></table></section><section id="enumset-NAME-TYPE" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-NAME-TYPE</code></h3><table><thead><tr class="header"><th>Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td><code>AKA</code></td><td style="text-align: left;">Also known as, alias, etc.</td></tr><tr class="even"><td><code>BIRTH</code></td><td style="text-align: left;">Name given at or near birth.</td></tr><tr class="odd"><td><code>IMMIGRANT</code></td><td style="text-align: left;">Name assumed at the time of immigration.</td></tr><tr class="even"><td><code>MAIDEN</code></td><td style="text-align: left;">Maiden name, name before first marriage.</td></tr><tr class="odd"><td><code>MARRIED</code></td><td style="text-align: left;">Married name, assumed as part of marriage.</td></tr><tr class="even"><td><code>PROFESSIONAL</code></td><td style="text-align: left;">Name used professionally (pen, screen, stage name).</td></tr><tr class="odd"><td><code>OTHER</code></td><td style="text-align: left;">A value not listed here; should have a <code>PHRASE</code> substructure</td></tr></tbody></table></section></section></section><section id="gedzip" data-number="4"><h1 data-number="4"><span class="header-section-number">4</span> The FamilySearch GEDZIP file format</h1><p>It is often useful to transmit a dataset together with a set of external files. The FamilySearch GEDZIP 7.0 file format is provided for this purpose. Version 7.0 was the first version of GEDZIP released; the version number of a GEDZIP file is the same as the version number of the dataset it contains.</p><p>A GEDZIP file is a zip archive, as defined by <a href="http://www.pkware.com/appnote">the .ZIP File Format Specification</a> and standardized by <a href="http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=60101">ISO/IEC 21320-1:2015</a>.</p><p>Each GEDZIP file contains the following entries:</p><ul><li><p>An entry with name <code>gedcom.ged</code> containing a data stream.</p></li><li><p>An entry for each <em>local file</em> <code>g7:datatype-FilePath</code> payload in <code>gedcom.ged</code>, with the same zip <em>file name</em> as the payload. If there is a local file named <code>gedcom.ged</code>, it must be renamed to a new unused filename with the same extension prior to constructing the GEDZIP.</p></li></ul><p>All file names inside a GEDZIP are case-sensitive.</p><p>Many other zip-based file formats (such as jar, epub, docx, GEDCOM-X) assign special meaning to the zip directory <code>META-INF</code> and the zip file names <code>MANIFEST.MF</code> and <code>META-INF/MANIFEST.MF</code>. These have no special meaning in GEDZIP and it is recommended that they not be used in a GEDZIP file, both to avoid confusing systems that look inside zip archives to determine their file type, and to leave open the possibility of their addition in a future version of this specification.</p><p>When saved as a file, a GEDZIP should use the filename extension <code>.gdz</code>.</p><div class="note"><p>A few details about the zip archive format are useful to fully understand GEDZIP:</p><ul><li>An archive can contain 1 or more files.</li><li>Files within an archive can be added, removed, or updated individually without needing to re-process the rest of the archive. Libraries such as <a href="https://libzip.org">libzip</a> allow applications to operate directly on the zip archive as if it were a normal directory tree.</li><li>What the zip specification calls a “file name” is actually a local path and may contain directories.</li><li>Directory separators are <code>/</code> internally and are converted to the appropriate form by the zip processing tool during zipping and unzipping. Because of this, unzipping a GEDZIP in any local directory results in all GEDZIP file paths working as-is for the resulting <code>gedcom.ged</code> without the need for any additional processing.</li></ul></div></section><section id="contributors" data-number="5"><h1 data-number="5"><span class="header-section-number">5</span> Contributors</h1><p>This document was based on <em>The GEDCOM Standard Release 5.5.1</em>, and could not have existed without the contributors to that and previous versions of the specification. Appreciation is extended to all family history participants that have made FamilySearch GEDCOM the <em>de facto</em> standard for saving and transferring genealogical information.</p><p>New contributions in this edition benefited from the input of a large number of people:</p><dl><dt>Managing Editors</dt><dd><ul><li>Gordon Clarke, <strong>FamilySearch</strong></li><li>Luther Tychonievich, <strong>FHISO</strong> and <strong>University of Virginia</strong></li></ul></dd><dt>Taskforce</dt><dd><ul><li>David Pugmire, <strong>FamilySearch</strong></li><li>Jimmy Zimmerman, <strong>FamilySearch</strong></li><li>Larry Telford, <strong>FamilySearch</strong></li><li>Matt Misbach, <strong>FamilySearch</strong></li><li>Russell Lynch, <strong>FamilySearch</strong></li><li>Robert Raymond, <strong>FamilySearch</strong></li><li>Gaylon Findlay, <strong>Ancestral Quest</strong></li><li>Derek Maude, <strong>Ancestry</strong></li><li>Simon Orde, <strong>Family Historian</strong></li><li>James Tanner, <strong>The Family History Guide</strong></li><li>John Cardinal, <strong>Family History Hosting</strong></li><li>Albert Emmerich, <strong>GEDCOM-L</strong></li><li>Dave Berdan, <strong>Legacy Family Tree</strong></li><li>Evgen Zherebniy, <strong>Software Mackiev</strong></li><li>Jason Fletcher, <strong>Midlera Software</strong></li><li>Uri Gonen, <strong>MyHeritage</strong></li><li>Dallan Quass, <strong>OurRoots.org</strong></li><li>Tony Proctor, <strong>SVG Family-Tree Generator</strong></li><li>Bill Harten, <strong>Puzzilla</strong></li><li>Bruce Buzbee and Mike Booth, <strong>RootsMagic</strong></li></ul></dd><dt>Development Teams</dt><dd><ul><li><p><strong>Tags team</strong>: Luther Tychonievich, Albert Emmerich, Russell Lynch, Tony Proctor, John Cardinal</p></li><li><p><strong>Extensions team</strong>: Luther Tychonievich, Tony Proctor, Jimmy Zimmerman</p></li><li><p><strong>Notes team</strong>: Dallan Quass, David Pugmire, Jason Fletcher, Russell Lynch</p></li><li><p><strong>External Media team</strong>: Dallan Quass, Jason Fletcher, Derek Maude</p></li></ul></dd></dl></section><section id="A-calendars" data-number="6"><h1 data-number="6"><span class="header-section-number">6</span> Appendix A: Known Calendars and Dates</h1><section id="known-calendars" data-number="6.1"><h2 data-number="6.1"><span class="header-section-number">6.1</span> Known Calendars</h2><p>This specification defines 4 calendars: <a href="#GREGORIAN" class="close"><code>GREGORIAN</code></a>, <a href="#JULIAN"><code>JULIAN</code></a>, <a href="#FRENCH_R"><code>FRENCH_R</code></a>, and <a href="#HEBREW"><code>HEBREW</code></a>. Previous versions also provided for, but did not define the meaning of, <code>ROMAN</code> and <code>UNKNOWN</code> calendars.</p><p>Extension calendars should use the usual rules for extensions, including using <code>_</code> as the leading character of the calendar name. Month codes in extension calendars must either be already used for the same month name in another calendar or must start with <code>_</code>. Only upper case characters are allowed in month codes.</p><p>Each calendar must list its permitted epochs and their meaning.</p><p>Each month defined in this section has a URI constructed by concatenating <code>g7:month-</code> to the month code; for example, the month of Elul has the URI <code>http://gedcom.io/terms/v7/month-ELL</code>.</p><section id="GREGORIAN" class="unnumbered" data-number><h3 class="unnumbered" data-number><code>GREGORIAN</code></h3><p>The Gregorian calendar is the now-ubiquitous calendar introduced by Pope Gregory XIII in 1582 to correct the Julian calendar which was slowly drifting relative to the seasons.</p><p>Permitted months are</p><table><thead><tr class="header"><th style="text-align: left;">Code</th><th style="text-align: left;">Name</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>JAN</code></td><td style="text-align: left;">January</td></tr><tr class="even"><td style="text-align: left;"><code>FEB</code></td><td style="text-align: left;">February</td></tr><tr class="odd"><td style="text-align: left;"><code>MAR</code></td><td style="text-align: left;">March</td></tr><tr class="even"><td style="text-align: left;"><code>APR</code></td><td style="text-align: left;">April</td></tr><tr class="odd"><td style="text-align: left;"><code>MAY</code></td><td style="text-align: left;">May</td></tr><tr class="even"><td style="text-align: left;"><code>JUN</code></td><td style="text-align: left;">June</td></tr><tr class="odd"><td style="text-align: left;"><code>JUL</code></td><td style="text-align: left;">July</td></tr><tr class="even"><td style="text-align: left;"><code>AUG</code></td><td style="text-align: left;">August</td></tr><tr class="odd"><td style="text-align: left;"><code>SEP</code></td><td style="text-align: left;">September</td></tr><tr class="even"><td style="text-align: left;"><code>OCT</code></td><td style="text-align: left;">October</td></tr><tr class="odd"><td style="text-align: left;"><code>NOV</code></td><td style="text-align: left;">November</td></tr><tr class="even"><td style="text-align: left;"><code>DEC</code></td><td style="text-align: left;">December</td></tr></tbody></table><p>The epoch marker <code>BCE</code> is permitted in this calendar; year <em>y</em> BCE indicates a year <em>y</em> years before year 1. Thus, there is no year 0; year 1 BCE was followed by year 1.</p><p>The URI for this calendar is <code>g7:cal-GREGORIAN</code></p></section><section id="JULIAN" class="unnumbered" data-number><h3 class="unnumbered" data-number><code>JULIAN</code></h3><p>The Julian calendar was introduced by Julius Caesar in 45 BC and subsequently amended by Augustus in about 8 BC to correct an error in the application of its leap year rule during its first 3 decades. Years had been counted from various starting epochs during the Julian calendar’s use; the version specified by this specification uses the same starting epoch as the Gregorian calendar.</p><p>This calendar uses the same months as the Gregorian calendar, differing only in which years February has 29 days.</p><p>The epoch marker <code>BCE</code> is permitted in this calendar; year <em>y</em> BCE indicates a year <em>y</em> years before year 1. Thus, there is no year 0; year 1 BCE was followed by year 1.</p><p>The URI for this calendar is <code>g7:cal-JULIAN</code></p></section><section id="FRENCH_R" class="unnumbered" data-number><h3 class="unnumbered" data-number><code>FRENCH_R</code></h3><p>The French Republican calendar or French Revolutionary calendar are the names given to the new calendar adopted in 1794 by the French National Convention. This calendar was adopted on Gregorian day 22 September 1792, which was 1 Vendémiaire 1 in this calendar. It was abandoned 18 years later.</p><p>Permitted months are</p><table><thead><tr class="header"><th style="text-align: left;">Code</th><th style="text-align: left;">Name</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>VEND</code></td><td style="text-align: left;">Vendémiaire</td></tr><tr class="even"><td style="text-align: left;"><code>BRUM</code></td><td style="text-align: left;">Brumaire</td></tr><tr class="odd"><td style="text-align: left;"><code>FRIM</code></td><td style="text-align: left;">Frimaire</td></tr><tr class="even"><td style="text-align: left;"><code>NIVO</code></td><td style="text-align: left;">Nivôse</td></tr><tr class="odd"><td style="text-align: left;"><code>PLUV</code></td><td style="text-align: left;">Pluviôse</td></tr><tr class="even"><td style="text-align: left;"><code>VENT</code></td><td style="text-align: left;">Ventôse</td></tr><tr class="odd"><td style="text-align: left;"><code>GERM</code></td><td style="text-align: left;">Germinal</td></tr><tr class="even"><td style="text-align: left;"><code>FLOR</code></td><td style="text-align: left;">Floréal</td></tr><tr class="odd"><td style="text-align: left;"><code>PRAI</code></td><td style="text-align: left;">Prairial</td></tr><tr class="even"><td style="text-align: left;"><code>MESS</code></td><td style="text-align: left;">Messidor</td></tr><tr class="odd"><td style="text-align: left;"><code>THER</code></td><td style="text-align: left;">Thermidor</td></tr><tr class="even"><td style="text-align: left;"><code>FRUC</code></td><td style="text-align: left;">Fructidor</td></tr><tr class="odd"><td style="text-align: left;"><code>COMP</code></td><td style="text-align: left;">Jour Complémentaires</td></tr></tbody></table><p>No epoch marker is permitted in this calendar.</p><p>The URI for this calendar is <code>g7:cal-FRENCH_R</code></p></section><section id="HEBREW" class="unnumbered" data-number><h3 class="unnumbered" data-number><code>HEBREW</code></h3><p>The Hebrew calendar is the name given to the calendar used by Jewish peoples around the world which developed into its current form in the early ninth century. It traditionally marks new days at sunset, not midnight. Its first day (1 Tishrei 1) primarily overlapped with Gregorian 7 September 3761 BCE and Julian 7 October 3761 BCE (starting at sunset on the 6th day of those months).</p><table><thead><tr class="header"><th style="text-align: left;">Code</th><th style="text-align: left;">Name</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>TSH</code></td><td style="text-align: left;">Tishrei (תִּשְׁרֵי)</td></tr><tr class="even"><td style="text-align: left;"><code>CSH</code></td><td style="text-align: left;">Marcheshvan (מַרְחֶשְׁוָן) or Cheshvan (חֶשְׁוָן)</td></tr><tr class="odd"><td style="text-align: left;"><code>KSL</code></td><td style="text-align: left;">Kislev (כִּסְלֵו)</td></tr><tr class="even"><td style="text-align: left;"><code>TVT</code></td><td style="text-align: left;">Tevet (טֵבֵת)</td></tr><tr class="odd"><td style="text-align: left;"><code>SHV</code></td><td style="text-align: left;">Shevat (שְׁבָט)</td></tr><tr class="even"><td style="text-align: left;"><code>ADR</code></td><td style="text-align: left;">Adar I, Adar Rishon, First Adar, or Adar Aleph (אדר א׳)</td></tr><tr class="odd"><td style="text-align: left;"><code>ADS</code></td><td style="text-align: left;">Adar (אֲדָר); or Adar II, Adar Sheni, Second Adar, or Adar Bet (אדר ב׳)</td></tr><tr class="even"><td style="text-align: left;"><code>NSN</code></td><td style="text-align: left;">Nisan (נִיסָן)</td></tr><tr class="odd"><td style="text-align: left;"><code>IYR</code></td><td style="text-align: left;">Iyar (אִייָר)</td></tr><tr class="even"><td style="text-align: left;"><code>SVN</code></td><td style="text-align: left;">Sivan (סִיוָן)</td></tr><tr class="odd"><td style="text-align: left;"><code>TMZ</code></td><td style="text-align: left;">Tammuz (תַּמּוּז)</td></tr><tr class="even"><td style="text-align: left;"><code>AAV</code></td><td style="text-align: left;">Av (אָב)</td></tr><tr class="odd"><td style="text-align: left;"><code>ELL</code></td><td style="text-align: left;">Elul (אֱלוּל)</td></tr></tbody></table><p>To keep the lunar-based months synchronized with the solar-based years, some years have Adar I and others do not, instead proceeding from Shevat directly to Adar II. However, in common (non-leap) years, it is common to simply write “Adar” not “Adar II”, which users not aware of the distinction might incorrectly encode as <code>ADR</code> instead of <code>ADS</code>. It is recommended that systems knowing which years had Adar I and which did not replace <code>ADR</code> in common years with <code>ADS</code>.</p><p>No epoch marker is permitted in this calendar.</p><p>The URI for this calendar is <code>g7:cal-HEBREW</code></p></section></section><section id="dual-dates" data-number="6.2"><h2 data-number="6.2"><span class="header-section-number">6.2</span> Dual dates</h2><p>The day on which a new year began and the year number increased varied at different times and places during the use of the Gregorian and Julian calendars. For example, England measured the new year as 25 March until 1752, when it switched to 1 January as the new year. In periods of transition, or when writing after a change about dates occurring before a change, it was sometimes common to indicate 2 years with a slash, for example, “30 January 1648/49” meaning “1648 if you count the new year as coming after 30 January, 1649 if you count it as coming before 30 January”. Other notations, such as abbreviations for phrases like “new style” and “old style”, were also sometimes employed.</p><div class="sourceCode" id="cb99"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb99-1"><a href="#cb99-1"></a><span class="dt">2 </span><span class="fu">DATE </span>30 JAN 1649</span>
+<span id="cb98-3"><a href="#cb98-3"></a><span class="dt">2 </span><span class="fu">TYPE </span>Bishop</span></code></pre></div><p>This classifies the entry as an ordination as a bishop, which is still a ordination event. The event could be further clarified with <a href="#RELI"><code>RELI</code></a>, <a href="#DATE"><code>DATE</code></a>, and other substructures.</p><p>Other descriptor values might include, for example,</p><ul><li>“Stillborn” as a qualifier to <a href="#BIRT"><code>BIRT</code></a> (birth)</li><li>“Civil” as a qualifier to <a href="#MARR"><code>MARR</code></a> (marriage)</li><li>“College” as a qualifier to <a href="#GRAD"><code>GRAD</code></a> (graduation)</li><li>“Oral” as a qualifier to <a href="#WILL"><code>WILL</code></a></li></ul><p>See also <code>FACT</code> and <code>EVEN</code> for additional examples.</p></div></section><section id="NAME-TYPE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>TYPE</code> (Type) <code class="uri">g7:NAME-TYPE</code></h4><p>An enumerated value from set <a href="#enumset-NAME-TYPE"><code>g7:enumset-NAME-TYPE</code></a> indicating the type of the name.</p></section><section id="EXID-TYPE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>TYPE</code> (Type) <code class="uri">g7:EXID-TYPE</code></h4><p>The authority issuing the <a href="#EXID"><code>EXID</code></a>, represented as a URI. It is recommended that this be a URL.</p><p>If the authority maintains stable URLs for each identifier it issues, it is recommended that the <a href="#TYPE"><code>TYPE</code></a> payload be selected such that appending the <a href="#EXID" class="close"><code>EXID</code></a> payload to it yields that URL. However, this is not required and a different URI for the set of issued identifiers may be used instead.</p><p>Registered URIs are listed in <a href="https://github.com/FamilySearch/GEDCOM/blob/main/exid-types.json">exid-types.json</a>, where fields include:</p><ul><li>“label”: a short string suitable for display in a user interface.</li><li>“type”: The URI representing the authority issuing the <a href="#EXID" class="close"><code>EXID</code></a>.</li><li>“description”: A description of the meaning of the <a href="#EXID" class="close"><code>EXID</code></a>.</li><li>“contact”: A contact email address for the person or organization registering the URI.</li><li>“change-controller”: The name or contact information for the person or organization authorized to update the registration.</li><li>“fragment”: If present, indicates a short string that can be used as a label for a fragment identifier appended to the URI. If absent, indicates that fragment identifiers are not used with the URI.</li><li>“reference”: A URL with more information about the meaning of the <a href="#EXID" class="close"><code>EXID</code></a>. Such information should explain the uniqueness and expected durability of the identifier.</li></ul><p>Additional type URIs can be registered by filing a <a href="https://github.com/FamilySearch/GEDCOM/pulls">GitHub pull request</a>.</p></section><section id="UID" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>UID</code> (Unique Identifier) <code class="uri">g7:UID</code></h4><p>A globally-unique identifier of the superstructure, to be preserved across edits. If a globally-unique identifier for the record already exists, it should be used without modification, not even whitespace or letter case normalization. New globally unique identifiers should be created and formatted as described in <a href="https://www.rfc-editor.org/info/rfc4122">RFC 4122</a>.</p><p>This is metadata about the structure itself, not data about its subject. Multiple structures describing different aspects of the same subject would have different <a href="#UID" class="close"><code>UID</code></a> values.</p><p>Because the <a href="#UID" class="close"><code>UID</code></a> identifies a structure, it can facilitate inter-tool collaboration by distinguishing between a structure being edited and a new structure being created. If an application allows structures to be edited in a way that completely changes their meaning (e.g., changing all the contents of an <code>INDI</code> record to have it describe a completely different person) then any <a href="#UID" class="close"><code>UID</code></a>s should also be changed.</p><div class="note"><p>Some systems used a 16-byte UUID with a custom 2-byte checksum for a total of 18 bytes:</p><ul><li>checksum byte 1 = (sum of (byte<sub><em>i</em></sub>) for <em>i</em> 1 through 16) mod 256</li><li>checksum byte 2 = (sum of ((16 − <em>i</em>) × (byte<sub><em>i</em></sub>)) for <em>i</em> 1 through 16) mod 256</li></ul><p>Use of checksums for UIDs is discouraged except in cases where error-prone input is expected and an appropriate action to take in case of an error is known.</p></div></section><section id="VERS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>VERS</code> (Version) <code class="uri">g7:VERS</code></h4><p>An identifier that represents the version level assigned to the associated product. It is defined and changed by the creators of the product.</p></section><section id="GEDC-VERS" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>VERS</code> (Version) <code class="uri">g7:GEDC-VERS</code></h4><p>The version number of the official specification that this document’s data conforms to. This must include the major and minor version (for example, “<code>7.0</code>”); it may include the patch as well (for example, “<code>7.0.1</code>”), but doing so is not required. See <a href="#a-guide-to-version-numbers">A Guide to Version Numbers</a> for more details about version numbers.</p></section><section id="WIDTH" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WIDTH</code> (Width in pixels) <code class="uri">g7:WIDTH</code></h4><p>How many pixels to display horizontally for the image. See <a href="#CROP"><code>CROP</code></a> for more details.</p></section><section id="WIFE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WIFE</code> (Wife) <code class="uri">g7:WIFE</code></h4><p>A container for information relevant to the subject of the superstructure specific to the individual described by the associated <code>FAM</code>’s <a href="#WIFE" class="close"><code>WIFE</code></a> substructure.</p></section><section id="FAM-WIFE" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WIFE</code> (Wife) <code class="uri">g7:FAM-WIFE</code></h4><p>A partner in a <code>FAM</code> record. See <a href="#FAMILY_RECORD"><code>FAMILY_RECORD</code></a> for more details.</p></section><section id="WILL" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WILL</code> (Will) <code class="uri">g7:WILL</code></h4><p>An <a href="#individual-events">Individual Event</a>. See also <a href="#INDIVIDUAL_EVENT_STRUCTURE"><code>INDIVIDUAL_EVENT_STRUCTURE</code></a>.</p></section><section id="WWW" class="unnumbered" data-number><h4 class="unnumbered" data-number><code>WWW</code> (Web address) <code class="uri">g7:WWW</code></h4><p>A URL or other locator for a World Wide Web page of the subject of the superstructure, as defined by any relevant standard such as <a href="https://url.spec.whatwg.org/">whatwg/url</a>, <a href="https://www.rfc-editor.org/info/rfc3986">RFC 3986</a>, <a href="https://www.rfc-editor.org/info/rfc3987">RFC 3987</a>, and so forth.</p><p>Like other substructures, the <a href="#WWW" class="close"><code>WWW</code></a> structure provides details about the subject of its superstructure. For example, a <a href="#family-events"><code>MARR</code></a>.<code>WWW</code> is a world wide web page of the marriage event, not the personal website of the couple or an entry in an online database serving as a source documenting the marriage. However, the meaning of <a href="#WWW" class="close"><code>WWW</code></a> was only implicit when it was introduced in version 5.5.1 and many files were created that use <a href="#WWW" class="close"><code>WWW</code></a> to store a more tangentially-related web address, so applications are recommended to interpret the <a href="#WWW" class="close"><code>WWW</code></a> structure’s meaning cautiously.</p><p>If an invalid or no longer existing web address is present upon import, it should be preserved as-is on export.</p></section></section></section><section id="enumeration-values" data-number="3.4"><h2 data-number="3.4"><span class="header-section-number">3.4</span> Enumeration Values</h2><p>Unless otherwise specified in the enumeration description in this section, each enumeration value defined in this section has a URI constructed by concatenating <code>g7:enum-</code> to the enumeration value; for example, the <a href="#HUSB"><code>HUSB</code></a> enumeration value has the URI <code>http://gedcom.io/terms/v7/enum-HUSB</code>.</p><p>Each set of enumeration values has its own URI.</p><section id="enumset-ADOP" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-ADOP</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>HUSB</code></td><td style="text-align: left;">Adopted by the <code>HUSB</code> of the <code>FAM</code> pointed to by <code>FAMC</code>.<br />The URI of this value is <code>g7:enum-ADOP-HUSB</code></td></tr><tr class="even"><td style="text-align: left;"><code>WIFE</code></td><td style="text-align: left;">Adopted by the <code>WIFE</code> of the <code>FAM</code> pointed to by <code>FAMC</code>.<br />The URI of this value is <code>g7:enum-ADOP-WIFE</code></td></tr><tr class="odd"><td style="text-align: left;"><code>BOTH</code></td><td style="text-align: left;">Adopted by both <code>HUSB</code> and <code>WIFE</code> of the <code>FAM</code> pointed to by <code>FAMC</code></td></tr></tbody></table></section><section id="enumset-EVEN" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-EVEN</code></h3><p>An event-type tag name, but not the generic <code>EVEN</code> tag. See <a href="#events">Events</a>.</p><p>Most values in this enumeration set use the same tag and URI as the corresponding event, except for tags used with different URIs for <code>FAM</code> vs <code>INDI</code>; these are given generic definitions with URIs constructed by concatenating <code>g7:enum-</code> to the enumeration value:</p><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>CENS</code></td><td style="text-align: left;">A census event; either <a href="#INDI-CENS"><code>g7:INDI-CENS</code></a> or <a href="#FAM-CENS"><code>g7:FAM-CENS</code></a></td></tr></tbody></table></section><section id="enumset-EVENATTR" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-EVENATTR</code></h3><p>An event- or attribute-type tag name. See <a href="#events">Events</a> and <a href="#attributes">Attributes</a>.</p><p>Most values in this enumeration set use the same tag and URI as the corresponding event or attribute, except for tags used with different URIs for <code>FAM</code> vs <code>INDI</code>; these are given generic definitions with URIs constructed by concatenating <code>g7:enum-</code> to the enumeration value:</p><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>CENS</code></td><td style="text-align: left;">A census event; either <a href="#INDI-CENS" class="close"><code>g7:INDI-CENS</code></a> or <a href="#FAM-CENS" class="close"><code>g7:FAM-CENS</code></a></td></tr><tr class="even"><td style="text-align: left;"><code>NCHI</code></td><td style="text-align: left;">A count of children; either <a href="#INDI-NCHI"><code>g7:INDI-NCHI</code></a> or <a href="#FAM-NCHI"><code>g7:FAM-NCHI</code></a></td></tr><tr class="odd"><td style="text-align: left;"><code>RESI</code></td><td style="text-align: left;">A residence attribute; either <a href="#INDI-RESI"><code>g7:INDI-RESI</code></a> or <a href="#FAM-RESI"><code>g7:FAM-RESI</code></a></td></tr><tr class="even"><td style="text-align: left;"><code>FACT</code></td><td style="text-align: left;">A generic attribute; either <a href="#INDI-FACT"><code>g7:INDI-FACT</code></a> or <a href="#FAM-FACT"><code>g7:FAM-FACT</code></a></td></tr><tr class="odd"><td style="text-align: left;"><code>EVEN</code></td><td style="text-align: left;">A generic event; either <a href="#INDI-EVEN"><code>g7:INDI-EVEN</code></a> or <a href="#FAM-EVEN"><code>g7:FAM-EVEN</code></a></td></tr></tbody></table></section><section id="enumset-MEDI" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-MEDI</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>AUDIO</code></td><td style="text-align: left;">An audio recording</td></tr><tr class="even"><td style="text-align: left;"><code>BOOK</code></td><td style="text-align: left;">A bound book</td></tr><tr class="odd"><td style="text-align: left;"><code>CARD</code></td><td style="text-align: left;">A card or file entry</td></tr><tr class="even"><td style="text-align: left;"><code>ELECTRONIC</code></td><td style="text-align: left;">A digital artifact</td></tr><tr class="odd"><td style="text-align: left;"><code>FICHE</code></td><td style="text-align: left;">Microfiche</td></tr><tr class="even"><td style="text-align: left;"><code>FILM</code></td><td style="text-align: left;">Microfilm</td></tr><tr class="odd"><td style="text-align: left;"><code>MAGAZINE</code></td><td style="text-align: left;">Printed periodical</td></tr><tr class="even"><td style="text-align: left;"><code>MANUSCRIPT</code></td><td style="text-align: left;">Written pages</td></tr><tr class="odd"><td style="text-align: left;"><code>MAP</code></td><td style="text-align: left;">Cartographic map</td></tr><tr class="even"><td style="text-align: left;"><code>NEWSPAPER</code></td><td style="text-align: left;">Printed newspaper</td></tr><tr class="odd"><td style="text-align: left;"><code>PHOTO</code></td><td style="text-align: left;">Photograph</td></tr><tr class="even"><td style="text-align: left;"><code>TOMBSTONE</code></td><td style="text-align: left;">Burial marker or related memorial</td></tr><tr class="odd"><td style="text-align: left;"><code>VIDEO</code></td><td style="text-align: left;">Motion picture recording</td></tr><tr class="even"><td style="text-align: left;"><code>OTHER</code></td><td style="text-align: left;">A value not listed here; should have a <code>PHRASE</code> substructure</td></tr></tbody></table></section><section id="enumset-PEDI" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-PEDI</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>ADOPTED</code></td><td style="text-align: left;">Adoptive parents</td></tr><tr class="even"><td style="text-align: left;"><code>BIRTH</code></td><td style="text-align: left;">Family structure at time of birth</td></tr><tr class="odd"><td style="text-align: left;"><code>FOSTER</code></td><td style="text-align: left;">The child was included in a foster or guardian family</td></tr><tr class="even"><td style="text-align: left;"><code>SEALING</code></td><td style="text-align: left;">The child was sealed to parents other than birth parents</td></tr><tr class="odd"><td style="text-align: left;"><code>OTHER</code></td><td style="text-align: left;">A value not listed here; should have a <code>PHRASE</code> substructure</td></tr></tbody></table><div class="note"><p>It is known that some users have interpreted <code>BIRTH</code> to mean “genetic parent” and others to mean “social parent at time of birth”. Definitions differ in many circumstances (infidelity, surrogacy, sperm donation, and so on). Hence, applications should refrain from asserting it has either meaning in imported data.</p></div><div class="note"><p>The structures for foster children in particular, and family relationships in general, are known to have undesirable limitations and are likely to change in a future version of this specification.</p></div><div class="note"><p><code>SEALING</code> implies that a <a href="#SLGC"><code>SLGC</code></a> event was performed, and it is recommended that this enumeration value only be used when the <a href="#SLGC" class="close"><code>SLGC</code></a> event is present in the GEDCOM file. <code>ADOPTED</code>, on the other hand, only implies a social relationship which may or may not have any associated <a href="#ADOP" class="close"><code>ADOP</code></a> event.</p></div></section><section id="enumset-QUAY" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-QUAY</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>0</code></td><td style="text-align: left;">Unreliable evidence or estimated data</td></tr><tr class="even"><td style="text-align: left;"><code>1</code></td><td style="text-align: left;">Questionable reliability of evidence (interviews, census, oral genealogies, or potential for bias, such as an autobiography)</td></tr><tr class="odd"><td style="text-align: left;"><code>2</code></td><td style="text-align: left;">Secondary evidence, data officially recorded sometime after the event</td></tr><tr class="even"><td style="text-align: left;"><code>3</code></td><td style="text-align: left;">Direct and primary evidence used, or by dominance of the evidence</td></tr></tbody></table><p>Although the values look like integers, they do not have numeric meaning.</p><div class="note"><p>The structures for representing the strength of and confidence in various claims are known to be inadequate and are likely to change in a future version of this specification.</p></div></section><section id="enumset-RESN" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-RESN</code></h3><table><thead><tr class="header"><th style="text-align: left;">Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>CONFIDENTIAL</code></td><td style="text-align: left;">This data was marked as confidential by the user.</td></tr><tr class="even"><td style="text-align: left;"><code>LOCKED</code></td><td style="text-align: left;">Some systems may ignore changes to this data.</td></tr><tr class="odd"><td style="text-align: left;"><code>PRIVACY</code></td><td style="text-align: left;">This data is not to be shared outside of a trusted circle, generally because it contains information about living individuals. This definition is known to admit multiple interpretations, so use of the <code>PRIVACY</code> restriction notice is not recommended.</td></tr></tbody></table><p>It is recommended that applications allow users to chose how <code>CONFIDENTIAL</code> and/or <code>PRIVACY</code> data is handled when interfacing with other users or applications, for example by allowing them to exclude such data when exporting.</p><p>When a <a href="#list">List</a> of <a href="#RESN"><code>RESN</code></a> enumeration values are present, all apply.</p><div class="example"><p>The line <code>1 RESN CONFIDENTIAL, LOCKED</code> means the superstructure’s data is both considered confidential <em>and</em> read-only.</p></div><p>Since <a href="#RESN" class="close"><code>RESN</code></a> was introduced in version 5.5 the intent of the <code>PRIVACY</code> value has been interpreted differently by different applications. Known interpretations include</p><ul><li>Some assign <code>PRIVACY</code> by algorithm or policy, unlike the user-assigned <code>CONFIDENTIAL</code></li><li>Some use <code>PRIVACY</code> to mark records that have already had private data removed</li><li>Some use the English definitions of “privacy” and “confidential” to inform different restrictions for each</li></ul><p>There may also be applications using <code>PRIVACY</code> with interpretations not listed above.</p><p>Because these different interpretations became widespread before they were identified, determining which one is meant generally requires knowledge of which application applied the <code>PRIVACY</code> restriction notice. It is anticipated that a future version will deprecate the <code>PRIVACY</code> option and introduce new values for each of its current use cases.</p></section><section id="enumset-ROLE" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-ROLE</code></h3><table><thead><tr class="header"><th>Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td><code>CHIL</code></td><td style="text-align: left;">Child</td></tr><tr class="even"><td><code>CLERGY</code></td><td style="text-align: left;">Religious official in event; implies <code>OFFICIATOR</code></td></tr><tr class="odd"><td><code>FATH</code></td><td style="text-align: left;">Father; implies <code>PARENT</code></td></tr><tr class="even"><td><code>FRIEND</code></td><td style="text-align: left;">Friend</td></tr><tr class="odd"><td><code>GODP</code></td><td style="text-align: left;">Godparent or related role in other religions</td></tr><tr class="even"><td><code>HUSB</code></td><td style="text-align: left;">Husband; implies <code>SPOU</code></td></tr><tr class="odd"><td><code>MOTH</code></td><td style="text-align: left;">Mother; implies <code>PARENT</code></td></tr><tr class="even"><td><code>MULTIPLE</code></td><td style="text-align: left;">A sibling from the same pregnancy (twin, triplet, quadruplet, and so on). A <code>PHRASE</code> can be used to specify the kind of multiple birth.</td></tr><tr class="odd"><td><code>NGHBR</code></td><td style="text-align: left;">Neighbor</td></tr><tr class="even"><td><code>OFFICIATOR</code></td><td style="text-align: left;">Officiator of the event</td></tr><tr class="odd"><td><code>PARENT</code></td><td style="text-align: left;">Parent</td></tr><tr class="even"><td><code>SPOU</code></td><td style="text-align: left;">Spouse</td></tr><tr class="odd"><td><code>WIFE</code></td><td style="text-align: left;">Wife; implies <code>SPOU</code></td></tr><tr class="even"><td><code>WITN</code></td><td style="text-align: left;">Witness</td></tr><tr class="odd"><td><code>OTHER</code></td><td style="text-align: left;">A value not listed here; should have a <code>PHRASE</code> substructure</td></tr></tbody></table><p>These should be interpreted in the context of the recorded event and its primary participants. For example, if you cite a child’s birth record as the source of the mother’s name, the value for this field is “<code>MOTH</code>.” If you describe the groom of a marriage, the role is “<a href="#HUSB"><code>HUSB</code></a>.”</p></section><section id="enumset-SEX" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-SEX</code></h3><table><thead><tr class="header"><th>Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td><code>M</code></td><td style="text-align: left;">Male</td></tr><tr class="even"><td><code>F</code></td><td style="text-align: left;">Female</td></tr><tr class="odd"><td><code>X</code></td><td style="text-align: left;">Does not fit the typical definition of only Male or only Female</td></tr><tr class="even"><td><code>U</code></td><td style="text-align: left;">Cannot be determined from available sources</td></tr></tbody></table><p>This can describe an individual’s reproductive or sexual anatomy at birth. Related concepts of gender identity or sexual preference are not currently given their own tag. Cultural or personal gender preference may be indicated using the <code>FACT</code> tag.</p></section><section id="enumset-FAMC-STAT" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-FAMC-STAT</code></h3><table><thead><tr class="header"><th>Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td><code>CHALLENGED</code></td><td style="text-align: left;">Linking this child to this family is suspect, but the linkage has been neither proven nor disproven.</td></tr><tr class="even"><td><code>DISPROVEN</code></td><td style="text-align: left;">There has been a claim by some that this child belongs to this family, but the linkage has been disproven.</td></tr><tr class="odd"><td><code>PROVEN</code></td><td style="text-align: left;">Linking this child to this family has been proven.</td></tr></tbody></table><p>When these enumeration values were introduced in version 5.5.1 it was assumed, but never specified, that “proven” referred to <a href="https://www.familysearch.org/en/wiki/Genealogical_Proof_Standard">the definition provided by the Board for Certification of Genealogists</a>. Because that meaning was not specified and other definitions of “proven” exist, existing files might use these values in other ways.</p><div class="note"><p>The structures for representing the strength of and confidence in various claims are known to be inadequate and are likely to change in a future version of this specification.</p></div></section><section id="enumset-ord-STAT" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-ord-STAT</code></h3><p>These values were formerly used by The Church of Jesus Christ of Latter-day Saints for coordinating between temples and members. They are no longer used in that way, meaning their interpretation is subject to individual user interpretation</p><p>The definition of some of these values combined with the official policies of the church mean that some values only make sense under a subset of <a href="#latter-day-saint-ordinances">ordinance structures</a>. These contexts are identified in the “applies to” column below, and it is recommended that applications follow those guidelines. These recommendations were not present when these enumeration values were first introduced in version 5.3 so uses that do not conform to the “applies to” guidelines may be encountered; if so, they should be treated by applications like any other user-specified but semantically-strange data.</p><p>The definition of some of these values combined with the official policies of the church and the move of the church away from using GEDCOM for handling ordinance requests make them redundant and/or no longer relevant. If so, that is indicated in the “status” column below. Like the “applies to” column, the “status” column is a recommendation, not a requirement, and applications should be prepared to encounter non-current values.</p><table><thead><tr class="header"><th>Value</th><th>Applies to</th><th style="text-align: left;">Meaning</th><th style="text-align: left;">Status</th></tr></thead><tbody><tr class="odd"><td><code>BIC</code></td><td><code>SLGC</code></td><td style="text-align: left;">Born in the covenant, so child to parent sealing ordinance is not required.</td><td style="text-align: left;">Current</td></tr><tr class="even"><td><code>CANCELED</code></td><td><code>SLGS</code></td><td style="text-align: left;">Canceled and considered invalid.</td><td style="text-align: left;">Current</td></tr><tr class="odd"><td><code>CHILD</code></td><td>All but <code>SLGC</code></td><td style="text-align: left;">Died before 8 years old, so ordinances other than child to parent sealing are not required.</td><td style="text-align: left;">Current</td></tr><tr class="even"><td><code>COMPLETED</code></td><td>All</td><td style="text-align: left;">Completed, but the date is not known.</td><td style="text-align: left;">Deprecated, use <code>DATE BEF date</code> instead. This status was defined for use with <a href="https://www.churchofjesuschrist.org/study/ensign/1994/02/news-of-the-church/templeready-now-available">TempleReady</a> which is no longer in use.</td></tr><tr class="odd"><td><code>EXCLUDED</code></td><td>All</td><td style="text-align: left;">Patron excluded this ordinance from being cleared in this submission.</td><td style="text-align: left;">Deprecated. This status was defined for use with TempleReady which is no longer in use.</td></tr><tr class="even"><td><code>DNS</code></td><td><code>SLGC</code>, <code>SLGS</code></td><td style="text-align: left;">This ordinance is not authorized.</td><td style="text-align: left;">Current</td></tr><tr class="odd"><td><code>DNS_CAN</code></td><td><code>SLGS</code></td><td style="text-align: left;">This ordinance is not authorized, and the previous ordinance is cancelled.</td><td style="text-align: left;">Current</td></tr><tr class="even"><td><code>INFANT</code></td><td>All but <code>SLGC</code></td><td style="text-align: left;">Died before less than 1 year old, baptism or endowment not required.</td><td style="text-align: left;">Deprecated. Use <code>CHILD</code> instead.</td></tr><tr class="odd"><td><code>PRE_1970</code></td><td>All</td><td style="text-align: left;">Ordinance was likely completed because an ordinance for this person was converted from temple records of work completed before 1970.</td><td style="text-align: left;">Deprecated. Use <code>DATE BEF 1970</code> instead.</td></tr><tr class="even"><td><code>STILLBORN</code></td><td>All</td><td style="text-align: left;">Born dead, so no ordinances are required.</td><td style="text-align: left;">Current</td></tr><tr class="odd"><td><code>SUBMITTED</code></td><td>All</td><td style="text-align: left;">Ordinance was previously submitted.</td><td style="text-align: left;">Deprecated. This status was defined for use with TempleReady which is no longer in use.</td></tr><tr class="even"><td><code>UNCLEARED</code></td><td>All</td><td style="text-align: left;">Data for clearing the ordinance request was insufficient.</td><td style="text-align: left;">Deprecated. This status was defined for use with TempleReady which is no longer in use.</td></tr></tbody></table></section><section id="enumset-NAME-TYPE" class="unnumbered" data-number><h3 class="unnumbered" data-number><code class="uri">g7:enumset-NAME-TYPE</code></h3><table><thead><tr class="header"><th>Value</th><th style="text-align: left;">Meaning</th></tr></thead><tbody><tr class="odd"><td><code>AKA</code></td><td style="text-align: left;">Also known as, alias, etc.</td></tr><tr class="even"><td><code>BIRTH</code></td><td style="text-align: left;">Name given at or near birth.</td></tr><tr class="odd"><td><code>IMMIGRANT</code></td><td style="text-align: left;">Name assumed at the time of immigration.</td></tr><tr class="even"><td><code>MAIDEN</code></td><td style="text-align: left;">Maiden name, name before first marriage.</td></tr><tr class="odd"><td><code>MARRIED</code></td><td style="text-align: left;">Married name, assumed as part of marriage.</td></tr><tr class="even"><td><code>PROFESSIONAL</code></td><td style="text-align: left;">Name used professionally (pen, screen, stage name).</td></tr><tr class="odd"><td><code>OTHER</code></td><td style="text-align: left;">A value not listed here; should have a <code>PHRASE</code> substructure</td></tr></tbody></table></section></section></section><section id="gedzip" data-number="4"><h1 data-number="4"><span class="header-section-number">4</span> The FamilySearch GEDZIP file format</h1><p>It is often useful to transmit a dataset together with a set of external files. The FamilySearch GEDZIP 7.0 file format is provided for this purpose. Version 7.0 was the first version of GEDZIP released; the version number of a GEDZIP file is the same as the version number of the dataset it contains.</p><p>A GEDZIP file is a zip archive, as defined by <a href="http://www.pkware.com/appnote">the .ZIP File Format Specification</a> and standardized by <a href="http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=60101">ISO/IEC 21320-1:2015</a>.</p><p>Each GEDZIP file contains the following entries:</p><ul><li><p>An entry with name <code>gedcom.ged</code> containing a data stream.</p></li><li><p>An entry for each <em>local file</em> <code>g7:type-FilePath</code> payload in <code>gedcom.ged</code>, with the same zip <em>file name</em> as the payload. If there is a local file named <code>gedcom.ged</code>, it must be renamed to a new unused filename with the same extension prior to constructing the GEDZIP.</p></li></ul><p>All file names inside a GEDZIP are case-sensitive.</p><p>Many other zip-based file formats (such as jar, epub, docx, GEDCOM-X) assign special meaning to the zip directory <code>META-INF</code> and the zip file names <code>MANIFEST.MF</code> and <code>META-INF/MANIFEST.MF</code>. These have no special meaning in GEDZIP and it is recommended that they not be used in a GEDZIP file, both to avoid confusing systems that look inside zip archives to determine their file type, and to leave open the possibility of their addition in a future version of this specification.</p><p>When saved as a file, a GEDZIP should use the filename extension <code>.gdz</code>.</p><div class="note"><p>A few details about the zip archive format are useful to fully understand GEDZIP:</p><ul><li>An archive can contain 1 or more files.</li><li>Files within an archive can be added, removed, or updated individually without needing to re-process the rest of the archive. Libraries such as <a href="https://libzip.org">libzip</a> allow applications to operate directly on the zip archive as if it were a normal directory tree.</li><li>What the zip specification calls a “file name” is actually a local path and may contain directories.</li><li>Directory separators are <code>/</code> internally and are converted to the appropriate form by the zip processing tool during zipping and unzipping. Because of this, unzipping a GEDZIP in any local directory results in all GEDZIP file paths working as-is for the resulting <code>gedcom.ged</code> without the need for any additional processing.</li></ul></div></section><section id="contributors" data-number="5"><h1 data-number="5"><span class="header-section-number">5</span> Contributors</h1><p>This document was based on <em>The GEDCOM Standard Release 5.5.1</em>, and could not have existed without the contributors to that and previous versions of the specification. Appreciation is extended to all family history participants that have made FamilySearch GEDCOM the <em>de facto</em> standard for saving and transferring genealogical information.</p><p>New contributions in this edition benefited from the input of a large number of people:</p><dl><dt>Managing Editors</dt><dd><ul><li>Gordon Clarke, <strong>FamilySearch</strong></li><li>Luther Tychonievich, <strong>FHISO</strong> and <strong>University of Virginia</strong></li></ul></dd><dt>Taskforce</dt><dd><ul><li>David Pugmire, <strong>FamilySearch</strong></li><li>Jimmy Zimmerman, <strong>FamilySearch</strong></li><li>Larry Telford, <strong>FamilySearch</strong></li><li>Matt Misbach, <strong>FamilySearch</strong></li><li>Russell Lynch, <strong>FamilySearch</strong></li><li>Robert Raymond, <strong>FamilySearch</strong></li><li>Gaylon Findlay, <strong>Ancestral Quest</strong></li><li>Derek Maude, <strong>Ancestry</strong></li><li>Simon Orde, <strong>Family Historian</strong></li><li>James Tanner, <strong>The Family History Guide</strong></li><li>John Cardinal, <strong>Family History Hosting</strong></li><li>Albert Emmerich, <strong>GEDCOM-L</strong></li><li>Dave Berdan, <strong>Legacy Family Tree</strong></li><li>Evgen Zherebniy, <strong>Software Mackiev</strong></li><li>Jason Fletcher, <strong>Midlera Software</strong></li><li>Uri Gonen, <strong>MyHeritage</strong></li><li>Dallan Quass, <strong>OurRoots.org</strong></li><li>Tony Proctor, <strong>SVG Family-Tree Generator</strong></li><li>Bill Harten, <strong>Puzzilla</strong></li><li>Bruce Buzbee and Mike Booth, <strong>RootsMagic</strong></li></ul></dd><dt>Development Teams</dt><dd><ul><li><p><strong>Tags team</strong>: Luther Tychonievich, Albert Emmerich, Russell Lynch, Tony Proctor, John Cardinal</p></li><li><p><strong>Extensions team</strong>: Luther Tychonievich, Tony Proctor, Jimmy Zimmerman</p></li><li><p><strong>Notes team</strong>: Dallan Quass, David Pugmire, Jason Fletcher, Russell Lynch</p></li><li><p><strong>External Media team</strong>: Dallan Quass, Jason Fletcher, Derek Maude</p></li></ul></dd></dl></section><section id="A-calendars" data-number="6"><h1 data-number="6"><span class="header-section-number">6</span> Appendix A: Known Calendars and Dates</h1><section id="known-calendars" data-number="6.1"><h2 data-number="6.1"><span class="header-section-number">6.1</span> Known Calendars</h2><p>This specification defines 4 calendars: <a href="#GREGORIAN" class="close"><code>GREGORIAN</code></a>, <a href="#JULIAN"><code>JULIAN</code></a>, <a href="#FRENCH_R"><code>FRENCH_R</code></a>, and <a href="#HEBREW"><code>HEBREW</code></a>. Previous versions also provided for, but did not define the meaning of, <code>ROMAN</code> and <code>UNKNOWN</code> calendars.</p><p>Extension calendars should use the usual rules for extensions, including using <code>_</code> as the leading character of the calendar name. Month codes in extension calendars must either be already used for the same month name in another calendar or must start with <code>_</code>. Only upper case characters are allowed in month codes.</p><p>Each calendar must list its permitted epochs and their meaning.</p><p>Each month defined in this section has a URI constructed by concatenating <code>g7:month-</code> to the month code; for example, the month of Elul has the URI <code>http://gedcom.io/terms/v7/month-ELL</code>.</p><section id="GREGORIAN" class="unnumbered" data-number><h3 class="unnumbered" data-number><code>GREGORIAN</code></h3><p>The Gregorian calendar is the now-ubiquitous calendar introduced by Pope Gregory XIII in 1582 to correct the Julian calendar which was slowly drifting relative to the seasons.</p><p>Permitted months are</p><table><thead><tr class="header"><th style="text-align: left;">Code</th><th style="text-align: left;">Name</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>JAN</code></td><td style="text-align: left;">January</td></tr><tr class="even"><td style="text-align: left;"><code>FEB</code></td><td style="text-align: left;">February</td></tr><tr class="odd"><td style="text-align: left;"><code>MAR</code></td><td style="text-align: left;">March</td></tr><tr class="even"><td style="text-align: left;"><code>APR</code></td><td style="text-align: left;">April</td></tr><tr class="odd"><td style="text-align: left;"><code>MAY</code></td><td style="text-align: left;">May</td></tr><tr class="even"><td style="text-align: left;"><code>JUN</code></td><td style="text-align: left;">June</td></tr><tr class="odd"><td style="text-align: left;"><code>JUL</code></td><td style="text-align: left;">July</td></tr><tr class="even"><td style="text-align: left;"><code>AUG</code></td><td style="text-align: left;">August</td></tr><tr class="odd"><td style="text-align: left;"><code>SEP</code></td><td style="text-align: left;">September</td></tr><tr class="even"><td style="text-align: left;"><code>OCT</code></td><td style="text-align: left;">October</td></tr><tr class="odd"><td style="text-align: left;"><code>NOV</code></td><td style="text-align: left;">November</td></tr><tr class="even"><td style="text-align: left;"><code>DEC</code></td><td style="text-align: left;">December</td></tr></tbody></table><p>The epoch marker <code>BCE</code> is permitted in this calendar; year <em>y</em> BCE indicates a year <em>y</em> years before year 1. Thus, there is no year 0; year 1 BCE was followed by year 1.</p><p>The URI for this calendar is <code>g7:cal-GREGORIAN</code></p></section><section id="JULIAN" class="unnumbered" data-number><h3 class="unnumbered" data-number><code>JULIAN</code></h3><p>The Julian calendar was introduced by Julius Caesar in 45 BC and subsequently amended by Augustus in about 8 BC to correct an error in the application of its leap year rule during its first 3 decades. Years had been counted from various starting epochs during the Julian calendar’s use; the version specified by this specification uses the same starting epoch as the Gregorian calendar.</p><p>This calendar uses the same months as the Gregorian calendar, differing only in which years February has 29 days.</p><p>The epoch marker <code>BCE</code> is permitted in this calendar; year <em>y</em> BCE indicates a year <em>y</em> years before year 1. Thus, there is no year 0; year 1 BCE was followed by year 1.</p><p>The URI for this calendar is <code>g7:cal-JULIAN</code></p></section><section id="FRENCH_R" class="unnumbered" data-number><h3 class="unnumbered" data-number><code>FRENCH_R</code></h3><p>The French Republican calendar or French Revolutionary calendar are the names given to the new calendar adopted in 1794 by the French National Convention. This calendar was adopted on Gregorian day 22 September 1792, which was 1 Vendémiaire 1 in this calendar. It was abandoned 18 years later.</p><p>Permitted months are</p><table><thead><tr class="header"><th style="text-align: left;">Code</th><th style="text-align: left;">Name</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>VEND</code></td><td style="text-align: left;">Vendémiaire</td></tr><tr class="even"><td style="text-align: left;"><code>BRUM</code></td><td style="text-align: left;">Brumaire</td></tr><tr class="odd"><td style="text-align: left;"><code>FRIM</code></td><td style="text-align: left;">Frimaire</td></tr><tr class="even"><td style="text-align: left;"><code>NIVO</code></td><td style="text-align: left;">Nivôse</td></tr><tr class="odd"><td style="text-align: left;"><code>PLUV</code></td><td style="text-align: left;">Pluviôse</td></tr><tr class="even"><td style="text-align: left;"><code>VENT</code></td><td style="text-align: left;">Ventôse</td></tr><tr class="odd"><td style="text-align: left;"><code>GERM</code></td><td style="text-align: left;">Germinal</td></tr><tr class="even"><td style="text-align: left;"><code>FLOR</code></td><td style="text-align: left;">Floréal</td></tr><tr class="odd"><td style="text-align: left;"><code>PRAI</code></td><td style="text-align: left;">Prairial</td></tr><tr class="even"><td style="text-align: left;"><code>MESS</code></td><td style="text-align: left;">Messidor</td></tr><tr class="odd"><td style="text-align: left;"><code>THER</code></td><td style="text-align: left;">Thermidor</td></tr><tr class="even"><td style="text-align: left;"><code>FRUC</code></td><td style="text-align: left;">Fructidor</td></tr><tr class="odd"><td style="text-align: left;"><code>COMP</code></td><td style="text-align: left;">Jour Complémentaires</td></tr></tbody></table><p>No epoch marker is permitted in this calendar.</p><p>The URI for this calendar is <code>g7:cal-FRENCH_R</code></p></section><section id="HEBREW" class="unnumbered" data-number><h3 class="unnumbered" data-number><code>HEBREW</code></h3><p>The Hebrew calendar is the name given to the calendar used by Jewish peoples around the world which developed into its current form in the early ninth century. It traditionally marks new days at sunset, not midnight. Its first day (1 Tishrei 1) primarily overlapped with Gregorian 7 September 3761 BCE and Julian 7 October 3761 BCE (starting at sunset on the 6th day of those months).</p><table><thead><tr class="header"><th style="text-align: left;">Code</th><th style="text-align: left;">Name</th></tr></thead><tbody><tr class="odd"><td style="text-align: left;"><code>TSH</code></td><td style="text-align: left;">Tishrei (תִּשְׁרֵי)</td></tr><tr class="even"><td style="text-align: left;"><code>CSH</code></td><td style="text-align: left;">Marcheshvan (מַרְחֶשְׁוָן) or Cheshvan (חֶשְׁוָן)</td></tr><tr class="odd"><td style="text-align: left;"><code>KSL</code></td><td style="text-align: left;">Kislev (כִּסְלֵו)</td></tr><tr class="even"><td style="text-align: left;"><code>TVT</code></td><td style="text-align: left;">Tevet (טֵבֵת)</td></tr><tr class="odd"><td style="text-align: left;"><code>SHV</code></td><td style="text-align: left;">Shevat (שְׁבָט)</td></tr><tr class="even"><td style="text-align: left;"><code>ADR</code></td><td style="text-align: left;">Adar I, Adar Rishon, First Adar, or Adar Aleph (אדר א׳)</td></tr><tr class="odd"><td style="text-align: left;"><code>ADS</code></td><td style="text-align: left;">Adar (אֲדָר); or Adar II, Adar Sheni, Second Adar, or Adar Bet (אדר ב׳)</td></tr><tr class="even"><td style="text-align: left;"><code>NSN</code></td><td style="text-align: left;">Nisan (נִיסָן)</td></tr><tr class="odd"><td style="text-align: left;"><code>IYR</code></td><td style="text-align: left;">Iyar (אִייָר)</td></tr><tr class="even"><td style="text-align: left;"><code>SVN</code></td><td style="text-align: left;">Sivan (סִיוָן)</td></tr><tr class="odd"><td style="text-align: left;"><code>TMZ</code></td><td style="text-align: left;">Tammuz (תַּמּוּז)</td></tr><tr class="even"><td style="text-align: left;"><code>AAV</code></td><td style="text-align: left;">Av (אָב)</td></tr><tr class="odd"><td style="text-align: left;"><code>ELL</code></td><td style="text-align: left;">Elul (אֱלוּל)</td></tr></tbody></table><p>To keep the lunar-based months synchronized with the solar-based years, some years have Adar I and others do not, instead proceeding from Shevat directly to Adar II. However, in common (non-leap) years, it is common to simply write “Adar” not “Adar II”, which users not aware of the distinction might incorrectly encode as <code>ADR</code> instead of <code>ADS</code>. It is recommended that systems knowing which years had Adar I and which did not replace <code>ADR</code> in common years with <code>ADS</code>.</p><p>No epoch marker is permitted in this calendar.</p><p>The URI for this calendar is <code>g7:cal-HEBREW</code></p></section></section><section id="dual-dates" data-number="6.2"><h2 data-number="6.2"><span class="header-section-number">6.2</span> Dual dates</h2><p>The day on which a new year began and the year number increased varied at different times and places during the use of the Gregorian and Julian calendars. For example, England measured the new year as 25 March until 1752, when it switched to 1 January as the new year. In periods of transition, or when writing after a change about dates occurring before a change, it was sometimes common to indicate 2 years with a slash, for example, “30 January 1648/49” meaning “1648 if you count the new year as coming after 30 January, 1649 if you count it as coming before 30 January”. Other notations, such as abbreviations for phrases like “new style” and “old style”, were also sometimes employed.</p><div class="sourceCode" id="cb99"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb99-1"><a href="#cb99-1"></a><span class="dt">2 </span><span class="fu">DATE </span>30 JAN 1649</span>
 <span id="cb99-2"><a href="#cb99-2"></a><span class="dt">3 </span><span class="fu">PHRASE </span>30 January 1648/49</span></code></pre></div><p>Many nations transitioned from using the Julian calendar to using the Gregorian calendar. This transition caused a change in dates by several days, which (depending on the date in question) could change the month and year as well. In periods of transition, or when writing after a change about dates occurring before a change, it was sometimes common to indicate 2 dates with slashes, for example “23/6 November/December 1907” meaning “Julian 23 November 1907, Gregorian 6 December 1907”. Other notations, such as abbreviations for phrases like “new style” and “old style”, were also sometimes employed.</p><div class="sourceCode" id="cb100"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb100-1"><a href="#cb100-1"></a><span class="dt">2 </span><span class="fu">DATE </span>6 DEC 1907</span>
 <span id="cb100-2"><a href="#cb100-2"></a><span class="dt">3 </span><span class="fu">PHRASE </span>23/6 November/December 1907</span></code></pre></div><p>Some documents also used slashes to indicate approximate dates, such as writing a birth year as “1903/4” when it was computed from a year-granularity age at a given date.</p><div class="sourceCode" id="cb101"><pre class="sourceCode gedcom"><code class="sourceCode gedcom"><span id="cb101-1"><a href="#cb101-1"></a><span class="dt">2 </span><span class="fu">DATE </span>BET 1903 AND 1904</span>
 <span id="cb101-2"><a href="#cb101-2"></a><span class="dt">3 </span><span class="fu">PHRASE </span>1903/4</span></code></pre></div><p>Versions 5.3 through 5.5.1 had special syntax for recording the first of these 3 concepts with a slash in the year. However, because slashes appear in historical documents with all 3 of the above meanings, some users misused this notation to record the other 2 situations as well. The result is ambiguity in the intended meaning of the resulting data. Version 7.0 removed the year slash notation; a <a href="#PHRASE"><code>PHRASE</code></a> substructure should be used instead to clarify meaning.</p></section><section id="calendars-in-date-ranges-and-date-periods" data-number="6.3"><h2 data-number="6.3"><span class="header-section-number">6.3</span> Calendars in date ranges and date periods</h2><p>Calendars apply to the subsequent <a href="#date"><code>date</code></a> production, not to the entire <a href="#date" class="close"><code>DateValue</code></a>. Hence,</p><ul><li><code>DATE FROM 1670 TO 1800</code> means <code>DATE FROM GREGORIAN 1670 TO GREGORIAN 1800</code></li><li><code>DATE FROM 1670 TO JULIAN 1800</code> means <code>DATE FROM GREGORIAN 1670 TO JULIAN 1800</code></li><li><code>DATE FROM JULIAN 1670 TO 1800</code> means <code>DATE FROM JULIAN 1670 TO GREGORIAN 1800</code></li></ul><p>Because some systems may show dates as-is to users and because not all users understand the above rule, it is recommended that <a href="#date" class="close"><code>calendar</code></a> tags be included if any <a href="#date" class="close"><code>date</code></a> is non-<a href="#GREGORIAN"><code>GREGORIAN</code></a>. It is recommended that the <a href="#date" class="close"><code>calendar</code></a> tag be omitted if all <a href="#date" class="close"><code>date</code></a>s in a payload are in the Gregorian calendar. Hence, the recommended forms of the previous 3 dates are</p><ul><li><code>DATE FROM 1670 TO 1800</code></li><li><code>DATE FROM GREGORIAN 1670 TO JULIAN 1800</code></li><li><code>DATE FROM JULIAN 1670 TO GREGORIAN 1800</code></li></ul></section></section>
diff --git a/specifications/FamilySearchGEDCOMv7.pdf b/specifications/FamilySearchGEDCOMv7.pdf
index d618202..c764696 100644
Binary files a/specifications/FamilySearchGEDCOMv7.pdf and b/specifications/FamilySearchGEDCOMv7.pdf differ