User:Gioto/Genealogy


 * http://en.wikipedia.org/wiki/Category:Genealogy
 * http://en.wikipedia.org/wiki/Category:Software_comparisons

TMG

 * http://en.wikipedia.org/wiki/User:Gioto/Genealogy/TMG_version_History

List of Old Genealogy Programs

 * http://en.wikipedia.org/wiki/User:Gioto/Genealogy/List_of_Old_Genealogy_Programs

GEDCOM

 * permanent link to a version of the GEDCOM page.

=20 This information will become part of the Frequently Asked Questions information available by anonymous ftp at gedcom.org. People still ask: why wasn't GEDCOM developed through a formal standards organization? GEDCOM was first proposed at the National Genealogical Society=20 (NGS) Conference held in Salt Lake City in July 1985. =20 Objectives and principles were outlined in a first draft of the standard (1.0). Discussion at that meeting centered around how to organize to accomplish it, although no conclusions were=20 reached. I contacted officials of ANSI (American National Standards=20 Institute) and NISO (National Information Standards=20 Organization--Z39) in Washington D.C., as well as participants=20 in ISO (International Standards Organization) standards, to=20 learn what it would take to establish GEDCOM through their=20 formal standards processes. I learned that these organizations require a minimum level of participation from a cross-section of=20 industry representatives. The cost of their participation=20 included fees, travel, and time. I also visited with the chair of the Computer Interest Group of the NGS in Washington D.C., and invited them to co-sponsor the=20 GEDCOM effort. This proposal was declined, partly because it=20 was closely associated with PAF, and NGS could not endorse=20 products. We hosted the first GEDCOM developers conference in Salt Lake=20 City in August 1987. About 30 invited guests attended,=20 representing several different genealogical software products,=20 user interests, and religious affiliations. Release 2.0 was=20 presented. The Family History department then proposed=20 establishing GEDCOM through the formal standards processes=20 sponsored by ANSI or NISO (U.S.), and eventually ISO. We=20 expressed our readiness to follow the formal approach, and asked=20 who of the other developers could make the necessary commitment of time and money. At the time, all of these were very small=20 organizations. None were prepared to participate in the formal process. As an alternative, we proposed following the approach used by=20 the U.S. Library of Congress in establishing the U.S. MARC=20 format (MAchine Readable Catalog) for bibliographic information,=20 now the dominant standard worldwide. Their approach was to=20 define and implement a standard on their own, and publish it for=20 others to follow if it was in their interest to do so. MARC=20 began deliberately as a de-facto standard. =20 Similarly, the FHD offered to develop and publish the standard=20 to meet our own needs, and to the extent possible, the needs of other independent developers and users. We agreed to add tags=20 and structures where necessary, even if our own programs did not=20 require them. We agreed that our FamilySearch programs would=20 follow the standard for exporting data from our databases. After considerable discussion, the GEDCOM developers raised=20 their hands in unanimous support of this proposal, with a =F4wait and see=F6 commitment to follow it if they liked it, and do=20 something else if they didn=C6t. Thus GEDCOM was born as a=20 deliberate, de facto standard, to be followed only by those who felt it was in their best interest to do so. The agreement=20 remains to this day. We have been pleased with the voluntary=20 results. The FHD has not pressured developers to follow GEDCOM. The user community, on the other hand, has consistently demanded GEDCOM=20 compatibility. Without their support, GEDCOM would not have=20 happened. In 1989 and again in 1991, at NGS conferences, I held meetings=20 with developers to gather input, inform them of progress, and to=20 review the agreement that held us together. Specifically, I=20 asked if we should continue the de facto approach, or whether=20 they were ready to join us in a more formal process. Both times,=20 the responses were the same as at first, and we continued with=20 the de facto approach. At the GENTECH conference in 1993, I expressed our continued=20 desire to involve more participants and to follow a more formal process. After this discussion, some mistakenly thought the FHD=20 wanted to give up this activity to others, but our desire is to include more participants in a proven process, through an=20 established standards organization, that has the staying power=20 and recognized discipline to ensure long-term success. In recent years, Jeri Steele and I independently asked the=20 GEDCOM-L group how we might organize to accomplish this. Only=20 one person responded. His suggestion was =F4Do it the way the=20 internet does it=F6.=20 Needing more explanation than that, I attended the IETF=20 (Internet Engineering Task Force) meetings in December of 1994=20 and 1995. This is where internet standards are hammered out.=20 I=20 attended the working sessions of the HTML group and others, and discussed GEDCOM and WWW genealogy databases with Tim Berners- Lee, of WWW fame. I met with John Klensin, director of the=20 applications group which created the email, WWW, and other=20 internet application standards, and which would preside over a=20 GEDCOM internet standard. At the last meeting, John and I agreed that the IETF would not=20 be a proper place to host a GEDCOM standards effort at this time=20 because the people who currently attend IETF meetings do not=20 possess the genealogical expertise to ensure an effective=20 standard. One approach might be to engage a representative set of people to attend IETF and go through their process. Or, John=20 suggested that we contact the Z39 committee again in Washington D.C. Several from his IETF group would be willing to=20 participate in a GEDCOM effort to contribute their standards=20 expertise. For the present, it has seemed best to finish the long-awaited=20 5.5 release under the current process, and continue looking for an improved process while waiting to begin on GEDCOM 6. Bill Harten, GEDCOM Product Manager, January 24, 1996 -->
 * Subject: GEDCOM and Formal Standards Organizations Date: Wed, 24 Jan 1996 11:53:52 -0700 From: Bill Harten - Organization: Brigham Young University "why wasn't GEDCOM developed through a formal standards organization?"<!--

History

 * Subject: LDS GEDCOM Report From: Bill Harten Date: Sat, 22 Oct 1994 16:17:38 -0600 - "I respond as the creator of GEDCOM and the current GEDCOM product manager for the Family History Department. My GEDCOM assignment has come and gone several times over the past 10 years. Jed Allen is currently the full-time day to day GEDCOM coordinator, and he reports to me in our organization."

"The principles behind GEDCOM were conceived starting in 1983 as we wrestled with fundamental problems caused by relational database technology." "All of our FamilySearch databases are stored in compressed GEDCOM format with a variety of indexes." "The name GEDCOM was applied to these concepts in 1985." ""
 * Database: GEDCOM s Genesis By Bill Harten


 * Re: GEDCOM Genesis - Bill Harten - "Our gedcom database program, called AIM"


 * My summary on why - "T.T.Wetmore"


 * "A Genealogy Program Adequacy Scale" published in "Computer Genealogy: A Guide to Research through High Technology" by Paul Andereck and Richard Pence, in 1985.


 * LDS usage of GEDCOM
 * Teamwork in family history - "New software helping stake members collaborate on common ancestral lines" - By R. Scott Lloyd (Church News staff writer) Published: Saturday, Dec. 4, 2004 LDS Church News
 * A century of progress in family history work By R. Scott Lloyd (Church News staff writer) Published: Saturday, June 26, 1999 - LDS Church News
 * Collaborative Genealogy The Genos Project
 * Genealogical Information Exchange (GIE). - GEDCOM was called this by the LDS
 * GIE Genealogy Information Exchange,  new GEDCOM version from LDS for PAF (see PERSONAL ANCESTRAL FILE).
 * BYU Studies v34 >> Number 2--1994 >> Chapter 8: Automating the Records


 * See margedos > GEDCOM files are somewhat similar to MARC, an interchange format for bibliographic data.
 * marc & gedcom

GEDCOM forms
From the introduction of the GEDCOM 5.5 Standard: ''This document discusses only one GEDCOM form: the Lineage-Linked GEDCOM Form. This is the form commercial software developers use to create genealogical software systems that can exchange compiled information about individuals with accompanying family, source, submitter, and note records with the Family History Department's FamilySearch Systems and with each other if desired.''


 * Bill Harten talks about "GEDCOM forms" and there being many types with "The Lineage-Linked GEDCOM Form" being one and that the FHD used 50 different GEDCOM forms for internal purposes. Lisp helped inspire GEDCOM I first used the form concept when learned that Kent Riggins adapted GEDCOM syntax for data conversion applications in the US Navy.


 * Rafal Prinke Subject: summary ?
 * From:Mike Parsons Subject:GEDCOM Standard Comments


 * Genealogy Software Standards- GEDCOM - RootsWeb: GENCMP-L

Robert D Foster
<!--
 * "He was on the initial core team that developed Personal Ancestral File, and he also designed the conceptual framework for GEDCOM - a program that enables various computer programs to share genealogical information"

Obituary: Robert D. Foster Published: Thursday, March 15, 2007 4:54 p.m. MDT deseretnews.com Robert D. Foster 1947 ~ 2007 Robert Dennis Foster, age 60, passed away March 11, 2007, from kidney cancer. Bob was born on March 2, 1947, in Nampa, Idaho, the son of John Ray and Ellafair Kendrick Foster. He grew up in Nampa and loved the rural feel of the community. After attending one year at Ricks College, Bob served an LDS mission to the Eastern States. Upon his return he attended BYU for two years before he "won" the Vietnam draft lottery and joined the army in 1970. Following basic training, Bob was assigned to Schweinfurt, Germany, with the troops patrolling the east-west border during the Cold War. While stationed there, he began to correspond with Tina Vilches. They were married in the LDS Temple on Jan. 22, 1972; later divorced. From this union were born three children whom he dearly loved: Rebecca Foster, Mishka Foster, and Micah Foster. Bob served a total of 10 years in the military. After returning from Germany he was stationed in the Washington, DC area. Through the military he was able to complete his bachelor's degree in computer science at BYU, after which he worked for four years at the Pentagon. Bob enjoyed his time in the service and was always grateful for the opportunity to serve his country. In 1980 Bob began to work for Ore-Ida Foods in Boise, Idaho. Two years later he moved to Utah to join the Family History Department of the LDS Church in developing new genealogy computer systems. He was on the initial core team that developed Personal Ancestral File, and he also designed the conceptual framework for GEDCOM - a program that enables various computer programs to share genealogical information. Later Bob led a team that developed portions of the LDS Church Internet site. He ended his career in data security, having completed the stringent requirements necessary to become certified as a data security engineer the week before his cancer diagnosis. On October 6, 1994, Bob married Marilyn M. Brown in the Salt Lake LDS Temple. He was a dear husband to her and became a wonderful influence in the lives of her family members, including children Bryan Brown, Becky Brown, Gregory and Elizabeth Grimshaw, Adriel and Deborah Burkholder, Mike Brown, James and Marianne Cone; and grandchildren Jason and Jared Brown; Meg and William Grimshaw; Allison, Isaac, Anna, and Jonathan Burkholder; and J.J. Cone. Bob was sincere in his commitments to his family and church, having participated in church service throughout his life. He had a gift for accepting people as they are but also nurturing their potential. A teacher once described him as "good, steady Bob," and he remained a man of honesty and integrity throughout his life. He loved science, the outdoors, and the world of nature and was committed to continued growth and learning in every aspect of his life. In addition to his wife, children, step-children, and grandchildren, Bob is survived by his brother John (Karen) Foster and sister Delores (Dee) Lowder, parents-in-law Gordon and Velma Miller, and in-laws Stephen (Karen) Miller, Richard (Jenae) Miller, and Francis Vassar. He was preceded in death by his parents, sister Jacqueline Vassar, and grandson Joshua Brown. Funeral services will be held Sat., March 17, 2007 at 11:00 a.m. in the Holladay North Stake Center, 4395 S. Albright Dr, Holladay, Utah. Viewings will take place Friday evening at Larkin Sunset Lawn, 2350 E. 1300 S., Salt Lake City, from 6-8 p.m., and Saturday at the church from 9:30-10:30 a.m. The family wishes to thank the caring, competent health care professionals who assisted Bob for the past year and a half, as well as the huge network of family, friends, neighbors, and work associates who have provided such great love and support throughout his illness. For those wishing to do so, Bob would be honored by donations made in his name to the Huntsman Cancer Foundation. -->

7. Anyone interested in MARC records might look at  *Genealogy & Computers* edited by Charles Clement (Chicago: American Library Assn, 1986) in which Keith H.  Strickland and Connie Lamb of Brigham Young University describe "MARGEDOS: a MARC-like Format for Genealogy." They cite an article in *Genealogical Journal* (Mar 1979) 34-42 "A Communications Format for Automated Documentation in  Genealogy" written by themselves. Also in *Genealogy & Computers* is "GEDCOM: A Format for  Genealogical Communications," by Robert D. Foster.
 * Subject: Random and naive comments/questions - From: George Waller - Date: Wed, 7 Sep 1994 16:53:49 EDT - GEDCOM-L Archives -- September 1994, week 1 (#59) "
 * (
 * 
 * 
 * Reference and Adult Services Division (RASD) Genealogy Committee, History Section Chicago
 * 

Paul Andereck

 * "Paul Andereck Ph.D." - ""Daddy" of genealogical computing"
 * GEDCOM (GEnealogical Data COMmunications) By Paul Arthur Andereck - Published by Data Transfer Associates, Inc., 1985  "Consist of information taken from various issues of Genealogical computing."
 * 
 * 
 * 
 * 
 * 
 * 
 * 
 * 
 * http://www.netins.net/showcase/andereck
 * paulaa @ netins . net
 * http://grm.net/~paulaa/

Extensions
Genealogy programs that create non standard(sic) GEDCOM's are using an undocumented proprietary extension that is only used by that program. When a group of Genealogy programmers decide on additional GEDCOM tags and how to use them though an agreed documented proprietary extension. (needs rewording)


 * Proprietary - documented
 * GEDCOM 5.5 EL (Extended Locations) - write how does it extends the GEDCOM and who supports it.

(need help on this one)
 * Proprietary - undocumented
 * List a couple of genealogy programs from wikipedia and how they extend the GEDCOM in an undocumented way eg; PAF at the very least

New Tags
From the GEDCOM standard:
 * In the Header the tag SOUR  appears and refers to.
 * APPROVED_SYSTEM_ID:= {Size=1:20} A system identification name which was obtained through the GEDCOM registration process. This name must be unique from any other product. Spaces within the name must be substituted with a 0x5F (underscore _) so as to create one word. Page 38

This is a "as of 9/94.... Brother's Keeper       {BROSKEEP} Cumberland Family Tree  {CFTREE} DISGEN                  {DISGEN} Everyone's Family Tree  {EFT} Family Heritage File    {FHF} Family Origins          {FamilyOrigins} Family Reunion          {FREUNION} Family Roots (TM)       {FAMROOTS} Family Ties             {FAMTIES} Family Treasures        {Family Treasures} Family Tree Genealogy   {FAMTREEAPPLE} Family Tree Maker       {FTM} Family Tree Print Util  {FTPRINTU} FTREE                   {FTREE} GAOPERSO                {GAOPERSO} Gen. Info. Management   {GIM} Gen. Data Manager       {GENIE} GENEASCOPE 2.2          {GENEASCOPE} Generation Gap          {GENGAP} Griot Alternative       {GRIOT} Pedigree Pursuit        {PedigreePursuit} Personal Ancestral File {PAF} Personal Dorot          {DOROT} Photo Family Tree       {PhotoGen} REUNION 3.0c            {REUNION} Roots III (TM)          {ROOTSIII} Roots IV (TM)          {ROOTSIV} The Family Edge Plus   {FamilyEdge}
 * Subject: List of Sources / Destinations in GEDCOM - From: Jed Allen - Organization: Brigham Young University - Date: Fri, 28 Oct 1994 17:19:32 -0600

In response to earlier questions, the following international GEDCOM-compatible products have been registered. The name in quotes is the reserved GEDCOM SOURce name for the header. DISGEN "DISGEN" LINGHEM, SWEDEN GAOPERSO "GAOPERSO" SEVRES, FRANCE GENEASCOPE "GENEASCOPE" CHAVILLE, FRANCE Griot Alternative "GRIOT" VILLERS-les-NANCY, FRANCE Personal Dorot "DOROT" Tel-Aviv, ISRAEL I have been in communication with the following but the registration process has not yet been completed. HAZADATA in Holland EDV-Genealogen in Germany Pedigree in the UK
 * Subject: International GEDCOM Products From: Bill Harten Date: Tue, 15 Nov 1994 10:03:47 -0700

And relates to: ''User-Defined Tags We do not encourage the use of user-defined GEDCOM tags. Applications requiring the use of non-standard tags should define them with a leading underscore so that they will not conflict with future GEDCOM standard tags. Systems that read user-defined tags must consider that they have meaning only with respect to a system contained in the HEAD.SOUR context. GEDCOM 5.5 page 59''

Other points to include
Other points to include:(from the GEDCOM-L archives)
 * When GEDCOM was created it was acknowledged (by the LDS) that TEXT format exchange between computers was in the process of being formalized. Unicode was added to GEDCOM in the 5.3 Draft, a lot of programs continue not to support this format due to technical issues eg: TMG due to its underlying Visual Fox Pro database
 * Was American Centric ( ANSEL /ASCII )
 * and XML was just begining


 * Includes a table of 11 Genealogy program and the versions of GEDCOM they support.Unofficial FAQ for Family Origins (Looks interesting still need to read)


 * ROOTS-L Resources: Family History Library News - News of the Family History Library was initially published six times yearly by the Family History Department of The Church of Jesus Christ of Latter-day Saints, then shifted to quarterly.


 * Announcing GEDCHK GEDCOM Syntax Check Program
 * Announcing GED2FIX GEDCOM Converter Program


 * GEDCOM utilities jan 1996


 * GEDCOM TEST - another one

GEDCOM info for other languages

 * Character sets
 * Character sets


 * GEDCOM 5.5 Standard(Modified with comments & notes.) "digested for my dog" - Formats Gedcom et GmC


 * Une étude comparative sur la transmission des données généalogiques à l'aide des fichiers au format gedcom 5.5.- "A comparative analysis on the transmission of the genealogical data using the files with the format gedcom 5.5."


 * http://www.dequidt.org/m1/gedcom55.pdf


 * mention GmC - variation on gedcom


 * GEDCOM & GRAMPS XML comment


 * tobtagxl - GEDCOM et ses dialectes - FAQ

History

 * http://web.archive.org/web/20030709025523/http://paf-review.com/

PAF history (unsourced material)
In terms of the Amiga version of the Personal Ancestral File software, I happen to know the software developer first hand who wrote the software and even took a copy of it to the LDS Church headquarters for review and to get it folded into the main distribution tree of the software. After a couple of weeks reviewing the software, it was ultimately rejected because the MIS department of the LDS Church didn't want to support yet another operation system and felt that the Amiga OS didn't have the market penetration necessary for the effort.

I don't know if this former co-worker later released his version under a different name as shareware, but he didn't spend a whole lot of time adding to the software after it was rejected as an official version.

As for the Apple II version, I remember an article about it in either the The Daily Universe or the Provo Daily Herald that talked about this subject, but that was many years ago. I also met with some of the people through the Utah Valley PAF User's Group that on an informal basis told me some of the very early history of PAF and went into some depth on the Apple II version. Most of the 1.0 version features with the exception of GEDCOM export functions were in that early version on the Apple II. Another possible source of information for this might also be the LDS Church News which has had several articles over the years about the Personal Ancestral File as well, including some historical notes. Unfortunately, all of the relevant articles are not on-line that I'm aware of, as it goes back to the early 1990's when I read this information.

The information is out there somewhere about this stuff, but trying to dig it up and find good sources for it is going to be hard work. I'm sorry that I can't help you out more, but I hope that this gives you a good start. Looking up the Utah Valley PAF User's Group might get you some contact information to make some e-mails if you want to try and contact some of the older members of that group. This certainly is one of the major hardcore groups associated with the PAF software. --Robert Horning (talk) 10:41, 16 February 2009 (UTC)
 * (moved from my talk page gioto (talk) 11:42, 16 February 2009 (UTC))

PAF Companion

 * http://www.ldschurchnews.com/articles/47382/PAF-Companion-prints-color-charts.html
 * http://www.ldschurchnews.com/articles/45367/Two-Popular-Family-History-Products-Now-Combined.html
 * http://www.ldschurchnews.com/articles/31560/2-new-products-to-aid-research-on-family-history.html

Reviews

 * http://www.ancestry.com/learn/library/article.aspx?article=3145
 * http://www.ancestry.com/learn/library/article.aspx?article=5643

Margedos
Should probably be a section or mentioned in the history of GEDCOM, mainframe usage


 * MARGEDOS: A MARC-like Format for Genealogy with Provision for Documentation By Connie Lamb - Published by Brigham Young University, 1976 (120 pages)


 * "A brief narrative description of the journal article, document, or resource.	The purpose of this project was to create a machine-readable format for genealogical data. The Library of Congress MARC (Machine Readable Cataloging) bibliographic system was used as the pattern in producing the format. Tags and codes were used to uniquely identify the components of the record for computer manipulation. The resultant structure, called MARGEDOS (Machine Readable Genealogy with Documentation of Sources), was established for use with an expanded Latter-day Saint (LDS) Family Group Record form that provides source information for each element of data. The inclusion of source documentation for every data element in a detailed and standardized manner was done to increase the credibility of genealogical records. The project was accomplished in three phases: the development of the machine-readable format, the conversion of a completed Family Group Record into that format, and the testing of the format through computer execution. An ALGOL program was constructed to recall the genealogical data with the sources and to display and print out the record in a particular arrangement. The format performed adequately for its intended purpose and the trial run on the computer was successful. Included in the document are a sample LDS Family Record form, a sample MARGEDOS Record, and the computer program. (Author/JAB)"

7. Anyone interested in MARC records might look at  *Genealogy & Computers* edited by Charles Clement (Chicago: American Library Assn, 1986) in which Keith H.  Strickland and Connie Lamb of Brigham Young University describe "MARGEDOS: a MARC-like Format for Genealogy." They cite an article in *Genealogical Journal* (Mar 1979) 34-42 "A Communications Format for Automated Documentation in  Genealogy" written by themselves. Also in *Genealogy & Computers* is "GEDCOM: A Format for  Genealogical Communications," by Robert D. Foster.
 * Subject: Random and naive comments/questions - From: George Waller - Date: Wed, 7 Sep 1994 16:53:49 EDT - GEDCOM-L Archives -- September 1994, week 1 (#59) "
 * (
 * 
 * 
 * Reference and Adult Services Division (RASD) Genealogy Committee, History Section Chicago
 * 


 * RootsWeb: GENCMP-L Genealogy Software Standards- GEDCOM

GRAMPS
To be incorporated
 * GRAMP XML is an open standard?. Documented where?


 * See the list of reviews on:
 * GRAMPS wiki
 * GENsoftreview user reviews? (can this be a source?)

History
gioto (talk) 08:42, 14 February 2009 (UTC)
 * Re: [Gramps-users Proposed evolution to web based software] From: Don Allingham  - 2003-12-05 18:37 "He liked my little program, convince me rename my little program from relativity (ever wonder where the Rel in RelLib.py came from?) to GRAMPS and to place it on SourceForge."
 * blog entry
 * History_of_GRAMPS - Wiki

Geneanet flash list (Format)

 * http://jfbaquet.free.fr/outils/fonc_en.html#list
 * http://gatheringleaves.org/content/view/276/95

BK

 * Release History
 * BBS of John Steed
 * Version 4.5 (06-28-90)
 * Version 5.0 (10-04-91)


 * old faq


 * Reviews:
 * Software Review of:Brother's Keeper version 5.2 for Windows From the November, 2000 issue of PC Alamode Magazine by Rose Lynn Saenger
 * Software Review of:Brother's Keeper From the February, 1999 issue of PC Alamode Magazine by Joseph V. Barth


 * Offline reviews (archers list)
 * Digest, Sept/Oct, 1989, pp. 13-15 (Version 4.3); Genealogical Computing
 * Jan/Feb/Mar 1990, pp. 25-27 (Version 4.5), Jan-Mar 1992, pp. 16-17 (Version 5.0), Jul-Sep 1992, pp. 16-17 (version 5.1) International PAF Users' Group
 * Quarterly, Fourth Quarter, 1990, Vol. 2, no 4. p. 81 (BKBOX and BKBOX4)
 * Genealogical Computing, Jul/Aug/Sep 1992, pp. 16-17 (Version 5.0b)
 * COMPU.GEN, Dec 1992, p. 80-81 (Mention of timeline and bar charts)
 * Genealogical Computing, Apr/May/Jun 1994, pp. 13-15
 * CGS-Computer Interest Mar/Arp, p. 5 (mention); May/Jun 1994, p. 3 (mention) and Sep/Oct 1994, p. 3 (mention).

Comparison of genealogy software
Ideas for improvement of the page
 * http://en.wikipedia.org/wiki/Comparison_of_genealogy_software
 * Link the title to the relevant articles/section or provide a generic example/image of each chart/report.


 * Separate into associated tables:
 * Features(eg: Research/Mapping)
 * Charts & Reports
 * Views/Interfaces/Displays


 * Interchange format
 * Be more descriptive and say what version if possible of GEDCOM (include ANSEL/ASCII) UTF-8 instead of just mentioning Unicode.
 * Up to what version of GEDCOM + variation or draft is supported (what exchange formats)
 * Include GRAMPS XML (phpgedview & gramps) as a interchange format (when I find the specification!)


 * Genealogical Program Summaries: lineage-linked data-base software

Other

 * A Historical Computing Bibliography > version 1.0 : 1993 > (c) AHC and Humanities Computing Centre, QMW (UK)


 * SpicyNodes,Early proof-of-concept as a genealogical browser of the Greek Gods