-
Notifications
You must be signed in to change notification settings - Fork 24
Draft v8.0 TEMPLATE, STICKY, FLEX, ASSET, GROUP, PROOF, alongside V7 #679
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
Draft
mother10
wants to merge
11
commits into
FamilySearch:main
Choose a base branch
from
mother10:v8.0
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR models new structures for GEDCOM V8, to try and take that to a higher level. It is based on TEMPLATEs and STICKYs. They describe the evidence in documents, on gravestones, in a census, and any other evidence "entity" that can hold genealogical information. It has 3 huge enumtables so it becomes a bit "Data driven". It is structured alongside GEDCOM 7.x (for now) to help users and developers get used to this new system. But before implementation the group might decide to totally disconnect it from V7.x and start a new direction. In that case changes have to be applied to make this draft work. While designing, time and effort have been spend to make it extendable, reliable, easily changeable, logical, solid and easy for users and developers. It needs polishing, refinements, help from the group to find missing ends. It has a huge extra file with examples, they are not there for fun (although some have some fun inside) but they are there as a testbed. I heavily used that to make sure things would fit. But I now want to show it all, I can hardly wait.😁
dthaler
reviewed
Aug 15, 2025
Sorry for the typo Co-authored-by: Dave Thaler <dthaler1968@gmail.com>
Agreed! Co-authored-by: Dave Thaler <dthaler1968@gmail.com>
Ok i'll do the others too. Co-authored-by: Dave Thaler <dthaler1968@gmail.com>
Added comma where needed.
Trying to get the linktable working.
Linktable corrected and some errors in example
Links still not working
Another try on the links
next try on 13:14
This was referenced Aug 22, 2025
Correct table link
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR models new structures for GEDCOM V8, to try and take that to a higher level. It is based on TEMPLATEs and STICKYs. They describe the evidence in documents, on gravestones, in a census, and any other evidence "entity" that can hold genealogical information. It has 3 huge enumtables so it becomes a bit "Data driven". It is structured alongside GEDCOM 7.x (for now) to help users and developers get used to this new system. But before implementation the group might decide to totally disconnect it from V7.x and start a new direction. In that case changes have to be applied to make this draft work.
While designing, time and effort have been spend to make it extendable, reliable, easily changeable, logical, solid and easy for users and developers.
It needs polishing, refinements, help from the group to find missing ends. It has a huge extra file with examples, they are not there for fun (although some have some fun inside) but they are there as a testbed. I heavily used that to make sure things would fit.
But I now want to show it all, I can hardly wait.😁