Louis Kessler’s Behold Blog The Behold User Forum
Search Entries, Comments and Posts
Results 11 - 20 of 48 total. 34 blog entries. 14 blog comments. 0 forum posts.
11.
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 ...
13.
Whither GEDCOM X? - Blog comment by lkessler - 8 Jun 2012
... place records, multimedia and other needed entities.
For those purists who want XML or JSON syntax, they are mappable 1-1 from the GEDCOM syntax and translators would be quick and easy. That's trivial.
I have not been convinced by anyone yet of any good reason to start over, which is what everyone's trying to do.
Louis
14.
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: ...
15.
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 ...
16.
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 ...
17.
One Serious Attempt at the Windows 7 Logo - Blog entry by lkessler - 16 Nov 2011
... at the "asInvoker" level. I researched into how to set up the manifest file (it's XML) and then how to embed it as a resource in Behold as required. So the problem must have been the request of an elevated run level, but it doesn't say what part of the program was requesting the elevated run level.
3. "Application did not pass multiuser session compliance check". ...
18.
Build a BetterGEDCOM or learn GEDCOMBetter? - Blog entry by lkessler - 5 Jan 2011
... in my view, and as I said a month ago, think it needs to be brought up-to-date (via XML and Unicode), and maybe could use a few improvements. I'm talking about tweaking - not a major overhaul, An evolution and not a rewrite.
But I think I found out what's going on and why the opinion is that GEDCOM is bad. Over at the BetterGEDCOM blog, a blog site run by some of the ...
19.
BetterGEDCOM - Blog comment by glamberson - 9 Dec 2010
... faithfully housing genealogy data as found in today's software applications in an XML-based file format, we'll simply delay addressing the research process if we cannot devise a resolution between the incongruent conclusion and evidence models.
Given how far along we are, I think we're doing fine. We are certainly focused on results, however, so stay tuned to see ...
20.
BetterGEDCOM - Blog comment by uwe - 8 Dec 2010
... is fierce nowadays. IMHO, it doesn't hurt to offer different options like GEDCOM, XML or JSON at the same time, even if some are not fully mature standards.
Prev 1-10
Whither GEDCOM X? - Blog comment by lkessler - 8 Jun 2012