Louis Kessler’s Behold Blog The Behold User Forum
Search Blog Comments
Results 1 - 10 of 14 blog comments. 34 blog entries. 0 forum posts. 48 total.
2.
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?
3.
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 ...
4.
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 ...
5.
Whither GEDCOM X? - Blog comment by lkessler - 8 Jun 2012
... far as data formats go, GEDCOM is not too wasteful on space. It is better than XML, but not as good as a database. It's the addition of all the "standards" stuff into the XML and the repetition of declarations for each entity that causes the real bloat.
Most of these updates to GEDCOM would not add significant size to the file. ...
6.
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
7.
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 ...
8.
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.
9.
BetterGEDCOM - Blog comment by lkessler - 8 Dec 2010
Uwe: It's not just a matter of converting GEDCOM to XML. For years, there are many that have said that GEDCOM needs to be improved. This is their chance to do that. The real challenge will be to give the 200 or so authors of genealogy programs a good reason to adopt the new standard and implement it.
10.
BetterGEDCOM - Blog comment by uwe - 8 Dec 2010
... wondering, Louis. What holds you back to implement the conversion of GEDCOM data into XML or even JSON format yourself? From a programmer's perspective, it should be fairly easy.
http://www.progdigy.com/?page_id=6
http://xml.coverpages.org/genealogy.html#gedML
Advancing the GEDCOM Standard - Blog comment by lkessler - 2 Sep 2018