Validation questions #260
Replies: 6 comments 2 replies
-
|
Dug in a bit and decided I didn't really need anything from the I published a new repository with an early version of what I'm working on. Still a lot of work to do but it currently does a few things.
If anyone is interested in taking a peek, it's at https://github.com/funwithbots/go-gedcom |
Beta Was this translation helpful? Give feedback.
-
|
We need another parser. Is go-gedcom ready to be listed at: You or I can add it if you like. Gordon |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hi Gordon, The software is a bit fresh but based on the testing I've done, I feel like it could be listed. More functionality is still being added but it does indeed parsed GEDCOM 7 files and makes them usable in golang programs. Bill |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Gordon, I opened a pull request and tagged you with the change. Bill |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
That information wasn't previously available, but I've now added a README in the extracted-files directory that hopefully provides the information you wanted. If there is something missing there, please let me know.
That's my doing. When drafting chapter 1 of the 7.0.0 spec, HEAD, TRLR, and CONT kept being exceptions to rules (such as reordering rules, Xref identifier rules, and extension substructure rules) and it was easier to just say "these three are special" than worry that I'd overlooked some place where they were special. The rest of the 7.0.0 drafting team pushed back on this, as it seemed strange to have this "pseudostructure" idea, but the alternative was putting "except HEAD, TRLR, and CONT" in various places throughout that chapter and that seemed less readable, so the pseudostructure idea made it into 7.0.
A good question. I've created #263 to track this. Technically the substructures of HEAD are present in the extracted_files (e.g. https://gedcom.io/terms/v7/GEDC has a |
Beta Was this translation helpful? Give feedback.
-
I'm working on a golang validator for gedcom 7 files. Mostly, I'm doing this as an exercise for my own benefit but I would like to add some cli features down the road to manipulate the various gedcom files I have laying around.
I plan to ingest the
extracted-filesfolder to implement the validation rules. This will let me update the validation rules any time a new gedcom version is released. I currently parse the yaml files in thetagsdirectory. I'm wondering is there is any additional information from the TSV files that I would also require to properly validate a file.I'm also curious why HEAD are TRLR are defined as
pseudostructureand don't have yaml files. I get that they are something of a special case because they can only occur once and must be the first/last records in a gedcom file. I am handling them with small hacks to load the abnf rules and allowed substructures for HEAD but it would be nice if this could also be automatic when I parse the contents ofextracted-files.Beta Was this translation helpful? Give feedback.
All reactions