This question pertains to processing GEDCOM files. Specifically, establishing the relationships between individuals: Fred is a child of Mary, Mary is married to John, John is a child of George, etc.
Which spouse/child reference in GEDCOM "wins"? INDI.FAMC/INDI.FAMS or FAM.HUSB/FAM.WIFE/FAM.CHIL? Ideally, I think, each INDI.FAMC is correctly paired with a matching FAM.CHIL, and likewise for INDI.FAMS and FAM.HUSB/FAM.WIFE. Could anyone offer guidance on how inconsistent references "should" be handled?
I have encountered GEDCOM files "in the wild" where the INDI.FAMC tags are not consistent with the FAM.CHIL tags. In other words, FAM records have CHIL references to INDI records without a matching FAMC reference. A pseudo-GEDCOM example:
0 @I1@ INDI 1 FAMC @F1@ 0 @I2@ INDI 0 @F1@ FAM 1 CHIL @I2@ 1 CHIL @I1@
Here, family F1 lists person I2 as a child in the family, yet person I2 doesn't have the corresponding FAMC reference. I believe the "correct" interpretation is person I2 is not a child of family F1. Am I wrong?
The reason for my concern is also illustrated with the above example: person I2 has become an "island", with no relationship within the forest. Using the FAM.CHIL link, person I2 is no longer an "island".
Does anyone have any data about specific genealogy programs with a history of writing GEDCOMs with these kinds of problems? E.g. I have a GEDCOM created by "Ftree for Linux" with a bunch of these issues.