Louis Kessler’s Behold Blog The Behold User Forum
Search Blog Entries
Results 1 - 10 of 34 blog entries. 14 blog comments. 0 forum posts. 48 total.
1.
Reading GEDCOM – A Guide for Programmers - Blog entry by lkessler - 12 Oct 2023
... can be used to define any data representation language. In that way, it is similar to XML and JSON. Why didn’t the developers of GEDCOM use XML or JSON for their standard? Well, they weren’t invented yet. So the developers of GEDCOM developed their own data representation language. Almost anything written with
2.
My Top Programming and Genealogy Q & As - Blog entry by lkessler - 27 Dec 2021
... answer. Why haven’t more programs adopted Gramps XML free format? My answer has 20 upvotes and was the accepted answer. What are the key points for a beginning genealogist to consider? My answer has 19 votes and was the accepted answer. Do you have your own Questions or Answers? As you can see, there are a wide range of ...
3.
GEDCOM 7.0, Official - Blog entry by lkessler - 7 Jun 2021
... release candidate. This version is called 7.0 and not 6.0 because there was a GEDCOM XML 6.0 draft issued on Oct 2, 2000, an updated draft on Dec 28, 2001, and a GEDCOM 6.0 XML Beta Version issued on Dec 6, 2002. The GEDCOM XML 6.0 specifications never became official and I don’t believe any program ...
4.
What to do When Your @FamilyTreeDNA Autosomal Results Come In - Blog entry by lkessler - 10 Jan 2017
... or Excel CSV is a comma delimited text format. Excel isn’t really Excel but is XML. It doesn’t matter which one you use. They both contain the same information. And Excel or any spreadsheet software can read them both. I usually use CSV, so hit the CSV button and download the file. It will be called something like: nnnnnn_Family_Finders_Matches_yyyymmdd.csv. ...
5.
Seven Years of Improvements - Blog entry by lkessler - 12 Jul 2015
... newer versions of Delphi include improved JSON low level processing and an improved XML engine. There were supposedly style improvements that take on the Theme of the O/S (Vista, Windows 7, WIndows 8), etc., but other than it adding a blue background to indicate that a toolbar item was selected, I haven’t noticed too much difference. It’s also touch-enabled. XE8 ...
6.
A Bit of History as GEDCOM Approaches Its 30th Year - Blog entry by lkessler - 18 Sep 2014
... was deployed fifteen years later. You would recognize this technology today as an XML-based DBMS, although AIM includes advanced indexing, search and compression concepts that are still unavailable in commercial DBMS products now 30 years later. GEDCOM 1.0 was published and delivered to about 30 attendees of the first GEDCOM Developers' Conference in 1985 in the ...
7.
Nine Necessities in a GEDCOM Replacement - Blog entry by lkessler - 5 Jun 2013
... Data Model Matters. Syntax Doesn’t. There has been too much discussion on whether XML or JSON or whatever be used instead of the GEDCOM syntax. But it doesn’t matter. As long as a basic tree-structure based data model is developed (Pauly, 2011), any syntax can easily and mechanically be translated into another. If so desired, the standard could even allow multiple ...
8.
Whither GEDCOM X? - Blog entry by lkessler - 7 Jun 2012
... on one file, and then unzipped the file to see that it made a thousand JSON XML files. There is no inherent difference between XML and the GEDCOM grammer. They are probably mappable back and forth. There are quite a number of JSON XML components for Delphi to choose from, e.g: ...
9.
My Feedback to GEDCOM X - Blog entry by lkessler - 29 Mar 2012
... Remember, we developers have to program that stuff. Produce a version of your XML using the GEDCOM syntax. It should be a simple mechanical translation. This will not only validate that the XML works, but will also show exactly where and how current GEDCOM differs with GEDCOM X. In addition, it will allow developers to convert into ...
10.
Ryan Heaton: GEDCOM X at RootsTech 2012 - Blog entry by lkessler - 6 Feb 2012
... GEDCOM X file. More choices are needed. Should be able to choose which you want, e.g. XML and JSON, or RDF. XML and JSON is already integrated into FamilySearch products. gedcomx.net and gedcomx.org and //github.com/FamilySearch/gedcomx The project to date has been all FamilySearch's doing. We now need your help. This is the first step. An ...
