Louis Kessler’s Behold Blog The Behold User Forum
Search Entries, Comments and Posts
Results 1 - 10 of 48 total. 34 blog entries. 14 blog comments. 0 forum posts.
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 ...
5.
Advancing the GEDCOM Standard - Blog comment by waynekurtz - 31 Aug 2018
Louis, a few years back I remember reading about an effort to create an XML based genealogy data tagging standard (I think its called a schema, but not sure). Have you ever heard of this? Any idea what happened to it?
6.
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. ...
7.
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 ...
8.
Complete Genealogy Data Transfer - Blog comment by arb - 9 Jun 2015
... some weird binary representation. Similarly, if I whose to use a network database, or XML files, or some NoSQL bigtable variant, that should be my decision and the standard(s) should have nothing to say on the matter. Some of my data is not being stored in a traditional database, let alone in a tabular format - why are you trying to tell me how to store my data, when all we ...
9.
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 ...
10.
A Recipe for GEDCOM - Blog comment by lkessler - 3 Aug 2013
... has adopted.
4. They feel GEDCOM's syntax needs to be replaced with XML or JSON or whatever, because all modern tools use those. GEDCOM's syntax can easily, mechanically and trivially be mapped to XML or JSON, and simple programs can be written to do that transfer. If that was so important, why aren't there any major ...
Advancing the GEDCOM Standard - Blog comment by lkessler - 2 Sep 2018