Add note about oddly formed age payloads (#432)

* Add note about oddly formed age payloads Signed-off-by: Dave Thaler <[email protected]> * Update specification/gedcom-2-data-types.md Co-authored-by: Luther Tychonievich <[email protected]> --------- Signed-off-by: Dave Thaler <[email protected]> Co-authored-by: Dave Thaler <[email protected]> Co-authored-by: Luther Tychonievich <[email protected]>
FamilySearch · Feb 1, 2024 · 667bcf2 · 667bcf2
1 parent f1fe039
commit 667bcf2
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/specification/gedcom-2-data-types.md b/specification/gedcom-2-data-types.md
@@ -225,6 +225,12 @@ Because numbers are rounded down, `>` effectively includes its endpoint; that is
 
 Different cultures count ages differently. Some increment years on the anniversary of birth and others at particular seasons. Some round to the nearest year, others round years down, others round years up. Because users may be unaware of these traditions or may fail to convert them to the round-down convention, errors in age of up to a year are common.
 
+:::note
+Because age payloads are intended to allow recording the age as it was recorded in records that could contain errors,
+odd ages such as `8w 30d`, `1y 400d`, `1y 30m`, etc. are permitted.  Some applications might convert these to more
+standard forms; if so, it is recommended that they use a `PHRASE` substructure to hold the original form.
+:::
+
 Age payloads may also be omitted entirely if no suitable form is known but a substructure (such as a `PHRASE`) is desired.
 
 :::note