The version number of the GEDCOM X project has just been increased from 0.36 to 1.0.0 M1.
The past week I've written about the recently released version 0.2 of the GEDCOM X Converter.
In Evaluating the GEDCOM X Converter, published only a day ago, I observed that
If you were to go by the numbering of the GEDCOM X Converter, you might think that release 1.0 of GEDCOM X is years away.
However, if you judge the readiness of the GEDCOM X project by the number of closed and open issues on GitHub,
it seems to be approaching a 1.0 release.
.
That observation was spot on…
The version number of the GEDCOM X project has just been increased from 0.36 to 1.0.0 M1.
The version number of GEDCOM X Java, FamilySearch's Java implementation of GEDCOM X, has been increased from 0.40.0 to 1.0.0 M1.
The version number of the GEDCOM X File Format Library has just been increased from 0.10.0 to 1.0.0 M1.
The version number of the GEDCOM X Converter has just been increased from 0.2 to 1.0.0 M1.
There have been few changes the past few days. The GEDCOM X Converter limitations I quoted from the GitHub GEDCOM X Converter home page still apply. The most significant change is that FamilySearch decided to change all those version numbers to 1.0.0 M1, about five years after the first code was written.
After many months of silence, there is another blog post on the GEDCOM X blog.
The A Bunch of Busy Developers post does not announce GEDCOM X 1.0 yet,
it merely promises that version 1.0 will be released soon, and that they'll write about it.
At the same time, the latest post on the FamilySearch Blog blog,
FamilySearch API (Application Programming Interface) For Software Developers,
informs readers that FamilySearch has released the new FamilySearch API.
The new FamilySearch Family Tree API replaces their earlier API. This is FamilySearch's proprietary API for FamilySearch Family Tree (FSFT), their Geni.com-like tree. The blog posts points to the FamilySearch Developer pages, which are similar in concept to MyHeritage's pages for their Family Graph API; there are samples with source code that you can run right from the page.
GEDCOM X is not related to GEDCOM, but to the FamilySearch Family Tree API.
The FAQ for the FamilySearch's API admits that their proprietary GEDCOM X specifications and FamilySearch API are related, but is less than open and honest about the nature of the relationship.
Referring to GEDCOM X, the FamilySearch FAQ claims that the FamilySearch API is built on these specifications
,
while it would be closer to the truth to state just the reverse, that the GEDCOM X specifications are based on the FamilySearch API.
The What is GEDCOM X? entry even claims that GEDCOM X is a major facelift to the standard
(GEDCOM), which it certainly isn't.
Despite the similarity in name, GEDCOM X is no update of GEDCOM.
GEDCOM X is not related to GEDCOM, but to the FamilySearch Family Tree API.
GEDCOM X is the format and protocol at the heart of the latest FamilySearch API.
The GEDCOM X blog has announced version 1.0 as milestone 1.
Copyright © Tamura Jones. All Rights reserved.