Louis Kessler’s Behold Blog     The Behold User Forum

Okay, let me try another tack... What you propose is potentially dangerous, and here's why: * You create a data file using program A, A includes some non-standard attributes, which are exported as per the standard. * The user then imports this file into program B, which does not support, nor even ...

Louis, some programs _are_ islands. A program that imports a data file and prints a report or fancy poster-sized tree does not need to export any data. These programs don't necessarily generate any data. Other programs might import data and do something more intensive, such as providing data mining tools, where ...

(Apologies in advance - I'm on my iPad without a decent keyboard and this is mostly stream-of-consciousness stuff...) This is a very tricky (and potentially messy) area and I don't think there is one "right" way of doing this. To start with, the restrictions you want to place on software implenenting this ...

My tools? Well, seeing as I don't like the majority of the genealogical software I have seen to date I decided to try roll my own solution. When I was thinking about how to tackle such a large project, it seemed to make sense to break things down into a series of small, interconnectable tools that each focus on ...

While you are correct in how standardised APIs are generally created, I believe it can be done without so much chaos. FHISO has a great opportunity to be a key driver in this space, but the FHISO participants need to stop being distracted by the glare of their own brilliance. From what I can make out from the ...

I agree that APIs are the future of genealogy software, however some standardisation is still neded. The genealogy tools I am writing will expose REST APIs to allow for data interchange between different tools and that's great, but if you wanted to integrate Behold with my apps, we will still need to agree on ...

I'll be honest, when I was researching genealogical data standards I thought that FHISO and the BetterGEDCOM project were defunct. Sure, there seems to be some activity on the website, but nothing concrete and no real signs of life. I could see no reasons why I, as a software developer and genealogy enthusiast, ...