Open fire-eggs opened 6 years ago
The user only wanted Name, Sex, Birthday and (IsDead?) info for INDIs, and the family connection (child/parent) in a family. For their purpose, the FAM connections were sufficient (though I've found some genealogy programs inconsistent in their FAM/INDI connections). They did not take into account BIRT/CHR/BAPM for birthday, nor date formatting.
Yes, any full-gedcom-support class structure is complex. For a "simple" application, I could see wanting to access a limited data set. On the parsing side, skipping other records/sub-records could make reading really fast. A naive programmer would not be aware of the complexities of GEDCOM and would fail to take many subtleties into account.
A casual genealogist may only be interested in people, families, and basic events (birth, death, marriage). Consider a "simple" parsing mode where other records, and other data, are simply ignored by the parser.
The "time line" project is one. Also motivated by a post in Stack Overflow where the author found Gedcom.Net to be "too complex", and was only interested in people/families to generate a tree.
Should have the option of skipping some validation.