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
Although some might overlap with CAUS, the CAUS tag has the same issue as TYPE which is that it's a human readable string (that may also vary by language) not a unique identifier like KIND is and so doesn't support high-fidelity matching like KIND would.
As far as “human readable”, at this point all tags and enum value are/should be in English, and all should be well defined so that any program can translate the English value to their native tongue. This is already done in the program I use for tags and v5.5.1 enum values. For cases when a concept is not directly translatable, the definitions could include these terms in the definition to ease translations, but also allow for other/phrase options.
Discussion in GEDCOM Steering Committee meeting 23 MAY 2024:
The KIND tag does not exist in any non-defunct branch. It was merged into the next-minor branch which was abandoned in favor of the v7.1 branch that does not have KIND.
Seeing the merge of #322 it seems if that is the direction please consider adding the following KIND enumeration sets:
For
BIRT
:For
DEAT
:The text was updated successfully, but these errors were encountered: