As formulated on the GOALS page, we think it would help to offer a test suite of data for software programmers.
To show off the features and possibilities of Better GEDCOM, we should write/create separate files for various features. This way, it will be easier to see what the importing application did with the information in the BG-file.
What should be in a BetterGEDCOM Testsuite? (please edit / add your ideas!)
- A "sources and evidence only" BG file.
This should demonstrate how one can use BG to share sources and the directly derived evidence. It should include media files (like JPGs, PDFs, DjVu, TXT, MP3...), the transcriptions of the sources, and the evidence persons and events that one can extract from the sources. The sources should be given varying "surety/quality" assessment. There should be "primary" sources (or more likely copies of such) and "secondary" sources, down to simple notes of a conversation or similar. The sources should be organized in a tree so that a citation can be derived easily.
- A nested BG file
This should show that one can import a GEDCOM or another BG into a BG as a source, and that the imported file will not be changed. This could also show how UUIDs for persons work.
- A "straight from old GEDCOM" file
Showing how an example GEDCOM file will translate into BG if "assimilated" and not used as a source. This could show how a "conclusion only" way of working is still possible with BG.
The GEDCOM should also be provided. It should use all allowed tags and some user-defined tags. It should have all possible variations in structure (e.g. NOTEs inline and as records...)
- A simple demonstration of the handling of evidence-conclusion with reasoning
This would need only a few conclusion persons and events, but a few more (conflicting) evidence persons and events. There should probably be sources included for the evidence, but maybe a few unsourced/un-explained conclusions could be interesting.
- A demonstration of complex families and multi-role events
Showing adoptions, half-siblings, multiple marriages / divorces / re-marriages, non-married couples, missing persons, missing dates, names, PACTs and probably much more.
Other "groups" (ships?) could possibly go here, too.
- A "farm history"
Showing how people, groups, events and dates can be linked with a place
- A "places only" file
Showing how places can be linked (or not), and the way to record places over time.
I believe a really well thought-out test suite would be of enormous value for programmers and would help BG become successful.
I also think that building this suite will be an enormous task!
End-users should try and think of difficult real-life (and imagined) examples and just write them down. Try to "condense" as many difficulties into a few constructed "cases".
Techies would then build these examples into BG-files. The specification doesn't have to be finished for this. Working on examples while formulating the definitions of BG will help with finding and fixing problems.
- The mystery Aunt
- GJ Cases