FamilySearch · tychonievich · Feb 5, 2025 · Feb 4, 2025
@@ -17,21 +17,21 @@ specification:
 
     Permitted months are
 
-    | Code   | Name                 |
-    | :----- | :------------------- |
-    | `VEND` | Vendémiaire          |
-    | `BRUM` | Brumaire             |
-    | `FRIM` | Frimaire             |
-    | `NIVO` | Nivôse               |
-    | `PLUV` | Pluviôse             |
-    | `VENT` | Ventôse              |
-    | `GERM` | Germinal             |
-    | `FLOR` | Floréal              |
-    | `PRAI` | Prairial             |
-    | `MESS` | Messidor             |
-    | `THER` | Thermidor            |
-    | `FRUC` | Fructidor            |
-    | `COMP` | Jour Complémentaires |
+    | `stdTag` | Name                 |
+    | :------- | :------------------- |
+    | `VEND`   | Vendémiaire          |
+    | `BRUM`   | Brumaire             |
+    | `FRIM`   | Frimaire             |
+    | `NIVO`   | Nivôse               |
+    | `PLUV`   | Pluviôse             |
+    | `VENT`   | Ventôse              |
+    | `GERM`   | Germinal             |
+    | `FLOR`   | Floréal              |
+    | `PRAI`   | Prairial             |
+    | `MESS`   | Messidor             |
+    | `THER`   | Thermidor            |
+    | `FRUC`   | Fructidor            |
+    | `COMP`   | Jour Complémentaires |
 
     No epoch marker is permitted in this calendar.
 

@@ -16,20 +16,20 @@ specification:
 
     Permitted months are
 
-    | Code  | Name      |
-    | :---- | :-------- |
-    | `JAN` | January   |
-    | `FEB` | February  |
-    | `MAR` | March     |
-    | `APR` | April     |
-    | `MAY` | May       |
-    | `JUN` | June      |
-    | `JUL` | July      |
-    | `AUG` | August    |
-    | `SEP` | September |
-    | `OCT` | October   |
-    | `NOV` | November  |
-    | `DEC` | December  |
+    | `stdTag` | Name      |
+    | :------- | :-------- |
+    | `JAN`    | January   |
+    | `FEB`    | February  |
+    | `MAR`    | March     |
+    | `APR`    | April     |
+    | `MAY`    | May       |
+    | `JUN`    | June      |
+    | `JUL`    | July      |
+    | `AUG`    | August    |
+    | `SEP`    | September |
+    | `OCT`    | October   |
+    | `NOV`    | November  |
+    | `DEC`    | December  |
 
     The epoch marker `BCE` is permitted in this calendar; year *y* BCE indicates a
     year *y* years before year 1. Thus, there is no year 0; year 1 BCE was followed

@@ -16,21 +16,21 @@ 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 (כִּסְלֵו)                                                         |
-    | `TVT` | Tevet (טֵבֵת)                                                           |
-    | `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 (אָב)                                                               |
-    | `ELL` | Elul (אֱלוּל)                                                           |
+    | `stdTag` | Name                                                                  |
+    | :------- | :-------------------------------------------------------------------- |
+    | `TSH`    | Tishrei (תִּשְׁרֵי)                                                        |
+    | `CSH`    | Marcheshvan (מַרְחֶשְׁוָן) or Cheshvan (חֶשְׁוָן)                               |
+    | `KSL`    | Kislev (כִּסְלֵו)                                                         |
+    | `TVT`    | Tevet (טֵבֵת)                                                           |
+    | `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 (אָב)                                                               |
+    | `ELL`    | Elul (אֱלוּל)                                                           |
 
     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

@@ -21,8 +21,8 @@ specification:
 
     - A URL with scheme `file` refers to either a **local file** or a **non-local
       file**, as defined by [RFC 8089]. Local file URLs must not be used in
-      [FamilySearch GEDZIP] and should be avoided in datasets that are expected
-      to be shared on the web or with unknown parties, but may be appropriate for
+      [FamilySearch GEDZIP] and should be avoided in datasets that are expected to
+      be shared on the web or with unknown parties, but may be appropriate for
       close collaboration between parties with known similar file structures.
 
     - A URI reference with all of the following:

@@ -19,21 +19,8 @@ specification:
     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.
 
-    Registered URIs are listed in [exid-types.json], where fields include:
-
-    - "label": a short string suitable for display in a user interface.
-    - "type": The URI representing the authority issuing the `EXID`.
-    - "description": A description of the meaning of the `EXID`.
-    - "contact": A contact email address for the person or organization registering
-      the URI.
-    - "change-controller": The name or contact information for the person or
-      organization authorized to update the registration.
-    - "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.
-    - "reference": A URL with more information about the meaning of the `EXID`.
-      Such information should explain the uniqueness and expected durability of the
-      identifier.
+    Registered URIs are listed in the [exid-types registry], where fields are
+    defined using the [YAML file format].
 
     Additional type URIs can be registered by filing a [GitHub pull request].
 

@@ -10,8 +10,7 @@ standard tag: 'FILE'
 
 specification:
   - File reference
-  - A reference to an external file. See the [File Path datatype] for more
-    details.
+  - A reference to an external file. See the [File Path datatype] for more details.
 
 label: 'File reference'
 

@@ -16,8 +16,7 @@ specification:
     structure. An application may choose to use a different default based on its
     knowledge of the language preferences of the user.
 
-    The payload of the `LANG` structure is a language tag, as defined by [BCP
-    47].
+    The payload of the `LANG` structure is a language tag, as defined by [BCP 47].
 
     <div class="note">
 

@@ -14,8 +14,8 @@ specification:
     The primary human language of the superstructure. The primary language in which
     the `Text`-typed payloads of the superstructure and its substructures appear.
 
-    The payload of the `LANG` structure is a language tag, as defined by [BCP
-    47]. A [registry of component subtags] is maintained publicly by the IANA.
+    The payload of the `LANG` structure is a language tag, as defined by [BCP 47].
+    A [registry of component subtags] is maintained publicly by the IANA.
 
     In the absence of a `LANG` structure, the language is assumed to be
     unspecified; that may also be recorded explicitly with language tag `und`

@@ -11,8 +11,8 @@ standard tag: 'TRAN'
 specification:
   - Translation
   - |
-    A type of `TRAN` substructure specific to [Personal Names]. Each
-    `NAME`.`TRAN` must have a `LANG` substructure. See also `INDI`.`NAME`.
+    A type of `TRAN` substructure specific to [Personal Names]. Each `NAME`.`TRAN`
+    must have a `LANG` substructure. See also `INDI`.`NAME`.
 
     <div class="example">
 

@@ -13,8 +13,7 @@ specification:
   - |
     A language the subject of that record understands.
 
-    The payload of the `LANG` structure is a language tag, as defined by [BCP
-    47].
+    The payload of the `LANG` structure is a language tag, as defined by [BCP 47].
 
 label: 'Language'
 

@@ -12,8 +12,8 @@ specification:
   - Web address
   - |
     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.
+    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

@@ -47,7 +47,9 @@ specification:
     `HUSB` and `WIFE` as layout hints, for example, by consistently displaying the
     `HUSB` on the same side of the `WIFE` in a tree view. Family structures with
     more than 2 partners may either use several `FAM` records or use
-    `ASSOCIATION_STRUCTURE`s to indicate additional partners.
+    `ASSOCIATION_STRUCTURE`s to indicate additional partners. `ASSO` should not be
+    used for relationships that can be expressed using `HUSB`, `WIFE`, or `CHIL`
+    instead.
 
     <div class="note">
 

@@ -28,7 +28,8 @@ specification:
     Other associations or relationships are represented by the `ASSO` (association)
     tag. The person's relation or associate is the person being pointed to. The
     association or relationship is stated by the value on the subordinate `ROLE`
-    line.
+    line. `ASSO` should not be used for relationships that can be expressed using
+    `FAMS` or `FAMC` instead.
 
     <div class="example">