691 paths removed from GEDCOM 5.5.1 - limited backward compatability. #428
-
|
stillthere = 2306 Attached is a list of paths that have been removed, and paths that are still there. looks like there is limited backward compatibility the conversion would be complex from GEDCOM 5 to GEDCOM7. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
You are correct; 7.0 is a major (not minor or patch) version, and hence not backwards compatible with earlier versions. A few of the removed paths are removed entirely (e.g. SUBN), but most are refactored into another structure (e.g. FONE → TRAN). We have a guide to conversion from 5.5.1 at https://gedcom.io/migrate/ and a few community-supplied example converters at https://gedcom.io/tools/#v551-to-v70-conversion-code FYI, saying "GEDCOM 5" is technically vague; 5.5.1, 5.5, 5.4, 5.3, and 5.0 were not backwards compatible either. We do not currently have a guide for conversion from 5.5 or earlier. |
Beta Was this translation helpful? Give feedback.
-
|
its actually Release 5.5.1 which I used for the comparison |
Beta Was this translation helpful? Give feedback.
You are correct; 7.0 is a major (not minor or patch) version, and hence not backwards compatible with earlier versions. A few of the removed paths are removed entirely (e.g. SUBN), but most are refactored into another structure (e.g. FONE → TRAN). We have a guide to conversion from 5.5.1 at https://gedcom.io/migrate/ and a few community-supplied example converters at https://gedcom.io/tools/#v551-to-v70-conversion-code
FYI, saying "GEDCOM 5" is technically vague; 5.5.1, 5.5, 5.4, 5.3, and 5.0 were not backwards compatible either. We do not currently have a guide for conversion from 5.5 or earlier.