You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# enums.setdefault(key, []).extend(_ for _ in ['g7:'+_2.replace('INDI-','enum-').replace('FAM-','enum-') for _2 in tagsets[k]] if _ not in enums.get(key,[]))
Copy file name to clipboardExpand all lines: changelog.md
+43Lines changed: 43 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,46 @@
1
+
# Version 7.0.17
2
+
3
+
- Add URI, Latitude, Longitude, and Tag definition data types.
4
+
5
+
Previously the formats permitted for these were specified in plain text with the corresponding structure types.
6
+
Those definitions have been moved to the data types section to better match how other data types are defined in the specification.
7
+
8
+
- Clarify the deprecation of older extensions that use non-underscore tags.
9
+
10
+
These violated the standard in both 7.0 and 5.5.1, but exist in the wild and there was unclear text "deprecating" them when they were never supported to begin with. That has been changed to be more clear about when it is an extension-defined substructure and when it violates the specification.
11
+
12
+
- Clarify how file paths encode non-ASCII characters.
13
+
14
+
- Clarify rules for pointer-based cycles:
15
+
16
+
- A cycle asserting someone is their own ancestor (such as being both the `CHIL` and `FAMS` of the same person) is unlikely to be correct, but is permitted by GEDCOM.
17
+
18
+
- A self-referential `ALIA` is (`INDI`.`AILA` pointing to the `INDI`) is meaningless and prohibited.
19
+
20
+
- A `SOUR`-`OBJE` cycle (the source of an image is the image itself) is meaningless and prohibited.
21
+
22
+
- Clarify that extension media types for notes (such as `text/markdown` that several applications are known to employ) do not require extension tags, being covered by the existing standard.
23
+
24
+
- Clarify the wording of the `ELECTRONIC` enumerated value.
25
+
26
+
- Clarify the wording of the `AGE` structure generally and `HUSB`.`AGE` and `WIFE`.`AGE` in particular.
27
+
28
+
- Add example of `PHRASE` used with a non-`OTHER` enumeration value.
29
+
30
+
- Update UUID defintion from RFC 4122 to RFC 9562
31
+
32
+
- Remove redundant and confusing references to RFC 3986, which were subsumed by existing references to WHATWG URL.
33
+
34
+
- Note that `FILE` payloads and GEDZIP file paths follow distinct standards, with the former using percent-escaping but the latter not.
35
+
36
+
- Note that GEDZIP inherits from zip the ability to have multiple levels of compression, with some suggestions on performance implications of the chosen compression level.
37
+
38
+
- Note that GEDZIP inherits from zip the ability to encrypt file contents, but not file names or sizes.
39
+
40
+
- Note how `ALIA` is known to be used by existing applications and users.
41
+
42
+
- Various typo corrections.
43
+
1
44
# Version 7.0.16
2
45
3
46
- Recommend that `ASSO` not be used to replicate other standard structures.
0 commit comments