RootsWeb.com Mailing Lists
Total: 1/1
    1. Re: [FHU] GEDCOM Compatibility
    2. Adrian Bruce
    3. <<snipped>> Overall it *seems* that FH data structures are far richer than in FTM, but an obvious question is whether the "FH way" is generally "acceptable" (there's probably nothing in the GEDCOM standard to arbitrate here). <<snipped>> 1. Simon is quite proud of his GEDCOM compatibility.... The "FH way" is, I think we agree, at least 99.999% compatible with the GEDCOM 5.5 standard. 2. Re: Census - I'd have to take a look at the precise forms but an event can have its note either "in line" or as a standalone note that is linked. So it may be legitimate GEDCOM. Just rather stupid - if it can keep other events' notes inline, why not this? 3. The sort of issues you mention possibly arise because FTM expects those items to be somewhere else - contrary to the GEDCOM standard. Or it can't be bothered to import them - which is kind of outside the standard. 4. "We ought to be worried if uploading data to Ancestry is incomplete". Here's the simple fact - uploading to just about any other app WILL be incomplete. Why? Well, as an ex-programmer I can say this - the majority of apps using GEDCOM are, with honourable exceptions such as FH, programmed incompetently. It's clear that their programmers have never read the GEDCOM standard, and can't be bothered to read it. No surprise imports and exports don't work well. 6. Is the FH way more acceptable? Well, it's more conformant to the standard. Much more. Whether or not you think that is acceptable is up to you - many people (not me) deliberately only use a fraction of the FH items because they want to load into another program that, basically, fouls up the import process. There is no point in my pedantically following the standard and exploiting everything I can in FH if I'm then going to complain when I can't load stuff into GenesReunited, etc. Standards are double edged swords. If you conform to them, you get the maximum benefit - but you may need to deal with those bits of software that don't conform, and so you may need to use a lowest common denominator. Sorry if this post displays a lot of cynicism about GEDCOM programmers but as an ex-programmer who actually read manuals, I get annoyed with those who don't. Basically - you need to think what you need, accept it's a jungle out there and that it's actually pointless to worry too much about acceptability and conformance to standard. Just ask whether it works... And yes - somehow you have to check! Adrian Bruce

    03/22/2012 05:24:15