Prev
5.5.1 compliant GEDCOM file - Categorized in: 
General Discussion
6 posts.
Started 10 Mar 2012 by brett. Latest reply 11 Mar 2012 by lkessler.
RSS
5.5.1 compliant GEDCOM file - Categorized in:
6 posts. Started 10 Mar 2012 by brett. Latest reply 11 Mar 2012 by lkessler. RSS
Leave your Reply
You must login to post your reply.
Joined: Mon, 12 Jan 2009
35 blog comments, 52 forum posts
Posted: Sat, 10 Mar 2012
After several years, much assistance from Behold's great GEDCOM validation, advice from Louis and support from Darrin and the User Group of The Next Generation of Genealogy Sitebuilding (TNG), I now have a GEDCOM exported file which meets 5.5.1.
What a pleasure it was to see
'No problems to report.'
in the File Information section of The Everything Report and
'Summary of all GEDCOM Messages
No problems to report.'
in the log file.
Thanks all for the assistance.
Brett
Joined: Sun, 9 Mar 2003
119 blog comments, 176 forum posts
Posted: Sat, 10 Mar 2012
Brett:
Don't jump for joy just yet. Behold won't do complete GEDCOM checking until Version 1.5 and right now it lets a few things go.
You should also try a couple of other validators: VGedX at http://ancestorsnow.com/tools/vgedx.php and GED-inline at http://ged-inline.elasticbeanstalk.com/validate
I wouldn't mind hearing what they catch that Behold didn't.
Louis
Joined: Mon, 12 Jan 2009
35 blog comments, 52 forum posts
Posted: Sat, 10 Mar 2012
OK, so I did jump too early.
I have validated through the above and also Genealogica Grafica and GenMatcher.
I will report all errors in an email.
In the meantime, the one error of most interest is:
Invalid content for DATE tag: '28 APR 1997' is not a valid <DATE_VALUE>
This does not error in Behold. Note the 2 spaces between APR and 1997.
Thanks
Brett
Joined: Sun, 9 Mar 2003
119 blog comments, 176 forum posts
Posted: Sun, 11 Mar 2012
Brett:
Good catch. Behold was not reporting extra spaces between date parts. Next version will.
Comparing the GED-inline and VGedX reports you sent me, I see that GED-inline reports all 7 problems that VGedX does but with better messages, and then finds 17 more problems, most of which are CONT tags where they are not allowed.
Darrin won't like the first error though. "Invalid content for SOUR tag: 'The Next Generation of Genealogy Sitebuilding' is not a valid <APPROVED_SYSTEM_ID>". It is not checking against a list, but is simply reporting that the maximum length allowed for <APPROVED_SYSTEM_ID> is 20 characters.
I have a similar issue with the Version_Number, where I'd like to put both the Behold version number and the date in that field, but only 15 characters are allowed.
Behold in Version 1.5 should catch all the errors that Ged-inline and VGedX report and maybe more. And then Behold will convert the invalid GEDCOM input into valid GEDCOM output.
The warning that VGedX gives that record 0 @I1884@ INDI is not referenced is already handled by Behold - not as a message - but it is places in the Unconnected Individuals section of the Everything Report.
Louis
Joined: Mon, 12 Jan 2009
35 blog comments, 52 forum posts
Posted: Sun, 11 Mar 2012
Louis
Does the GEDCOM character limit include the TAG?
If no, would this be suitable for vs and date?
VERS xx.x.x mm-dd-yy
Brett
Joined: Sun, 9 Mar 2003
119 blog comments, 176 forum posts
Posted: Sun, 11 Mar 2012
What I'll probably do is:
0 HEAD
1 SOUR Behold
2 VERS 1.0.4
2 NAME Behold version 1.0.4, 23 Jan 2012