-
Notifications
You must be signed in to change notification settings - Fork 45
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
Add options to disable non-standard features #515
Comments
Yes, it can be done. Although the locations are taken from GEDCOM 5.5EL. |
Ok. Was mostly asking just to know, rather to take any actions for this. Thanks for the links :) |
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. |
@cbettinger that's a good point. Again, from my pov it was just a question, rather than a call for action :) |
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. |
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 theVERS
tag say 5.5.5 ?The text was updated successfully, but these errors were encountered: