Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GEDCOM header version #515

Open
burtek opened this issue Nov 22, 2023 · 5 comments
Open

GEDCOM header version #515

burtek opened this issue Nov 22, 2023 · 5 comments
Assignees
Labels
discuss enhancement New feature or request question Further information is requested
Milestone

Comments

@burtek
Copy link
Contributor

burtek commented Nov 22, 2023

GEDKeeper uses 5.5.1 version header, but at the same time uses _LOC tag, and top-level predefined locations which were first introduced in 5.5.5. Shouldn't the VERS tag say 5.5.5 ?

1 GEDC
2 VERS 5.5.1
@Serg-Norseman
Copy link
Owner

Serg-Norseman commented Nov 22, 2023

Yes, it can be done. Although the locations are taken from GEDCOM 5.5EL.

See: https://wiki.genealogy.net/GEDCOM_5.5EL

https://www.tamurajones.net/DetectingGEDCOM5.5EL.xhtml

@burtek
Copy link
Contributor Author

burtek commented Nov 22, 2023

Ok. Was mostly asking just to know, rather to take any actions for this. Thanks for the links :)

@Serg-Norseman Serg-Norseman self-assigned this Nov 22, 2023
@Serg-Norseman Serg-Norseman added enhancement New feature or request question Further information is requested discuss labels Nov 22, 2023
@Serg-Norseman Serg-Norseman added this to the Next Versions milestone Nov 22, 2023
@Serg-Norseman Serg-Norseman modified the milestones: Next Versions, GK v2.30.0 / GK v3.6.0 Dec 1, 2023
@Serg-Norseman Serg-Norseman modified the milestones: GK v2.30.0 / GK v3.6.0, GK v2.29.0 / GK v3.5.0, Next Versions Dec 14, 2023
@cbettinger
Copy link

As described in the copyright notice of GEDCOM 5.5.5 and on https://wiki.genealogy.net/GEDCOM/Spezifikation555 the GEDCOM 5.5.5 specification is not published by the Latter-Day Saints and therefore somewhat "unofficial".

The same - of course - applies to GEDCOM_5.5EL, which is published by the Gedcom-L working group of Genealogy.net.

Because GEDCOM_5.5EL strictly uses the extension mechanisms of GEDCOM 5.5.1 I would recommend to keep the version header 5.5.1 - at least that is not errorneous. When changing to 5.5.5 I am not quite sure about that.

@burtek
Copy link
Contributor Author

burtek commented Apr 22, 2024

@cbettinger that's a good point. Again, from my pov it was just a question, rather than a call for action :)

@Serg-Norseman
Copy link
Owner

I've been thinking about creating a set of feature switches for a long time. So that experienced users can disable partially or completely non-standard features, it may also be worth adding a choice of the output version of the standard.

This would simplify a lot, IMHO. We can think together about a list of features to disable: additional types of records (tasks, communications, research), locations, additional types of events/facts, and everything else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants