Version 7.0.11

changelog.md

@@ -1,3 +1,24 @@
+# Version 7.0.11
+
+- Correct error in `g7:NOTE-TRAN` cardinality.
+
+    Since 7.0.0, `g7:NOTE-TRAN` was listed with `{0:1}` in `g7:NOTE` but `{0:M}` in `g7:record-SNOTE` and defined in a way that assumed `{0:M}`. It has now been updated to `{0:M}` in `g7:NOTE-TRAN` too.
+
+- Correct error in `g7:type-Enum` definition.
+
+    Since 7.0.0, `g7:type-Enum` was listed as having the same payload as `Tag`, but `g7:QUAY` used enumeration values that did not match that. The definition of  `g7:type-Enum` has now been updated to permit integers, like `g7:QUAY` uses.
+
+- Clarify that the same tag can be used for multiple URIs in the schema provided the meanings are non-overlapping. Recommend tags only be reused for closely related concepts, similar to how standard tags are.
+
+- Recommend that `g7:type-DateExact` should use UTC time because it is used in places where exact machine-generated timestamps are expected.
+
+- Split shared rows in date definition table and reorder rows to be more logically organized.
+
+- Update ABNF to use `[ X ]` instead of `X / ""` to indicate `X` is optional. Both are legal ABNF, but some ABNF toolchains appear not to support the `X / ""` notation.
+
+- Various typo corrections.
+
+
 # Version 7.0.10
 
 - Collect information about structure types and present it explicitly in the document, including how tags define structure types, the limitations structure types impose on their structures, and what extensions can change. This information was all present in the text before, but in a diffuse and not very accessible way.

specification/gedcom-00-introduction.md

@@ -1,6 +1,6 @@
 ---
 title: The FamilySearch GEDCOM Specification
-subtitle: 7.0.10
+subtitle: 7.0.11
 email: [email protected]
 copyright: |
     :::{style="page-break-after: always;page-break-before: always;"}