Stransky Family Tree

Coming in 2010 we will separate much of this xml and genealogy stuff into three areas. My plan is to have the family tree itself, then an area about displaying genealogy with xml and example codes with passing parameters. And last my web based project to display family tree scripts, edit and modify genealogy database from your own website.

SFT 2010 Genealogy Project XML database driven by classic ASP..

GEDCOM standards, what ever happened to them?

   Actually no one can agree which way is better and everyone has their own approach to doing it. their is no guidelines how to get from point A to point B. Some like the scenic route while others just cut to the chase bypassing information.

  I am from both side of the coin, the most popular one which has been around the longest has the worst hierarchy structure. Why? because as time went on more data became available and the only place to put it is inside the person tag next to the name. Problem is, you will pass 40 people in a file and they will be just the basic data, then you hit a person who has child tags inside other child tags making the whole flow NOT uniform.

  Both sides are struggling for more data labels and tags such like shoe size?, and the other says why even include it? So I don't think there will be a standard any time soon. NOT unless someone can come up with a way to satisfy both sides.  

My past 2009 Genealogy website display scripts project

   This Version paused, a newer multi xml db is in progress beta version 4.0. information follows in next few paragraphs. all functions in pervious project with be incorporated in the new beta 4.0

   As above with GEDCOM many software's delete dump or do not show validated information. most times when exporting your files from one software platform to another, they only import or export what they want regardless the amount of work you have collected.
  That is why I started this project on the 25th Dec 2008. This Classic asp scripts hides the xml records from the public view. the script will only display non private info. only if a member or admin logins in will the displays then include contacts in the tree. Also allows permissions to add edit and update information when family members are logged in. Those permissions are set by the Owner who allows Administrators to set permissions to members and so on. By clicking on the image you will start off on my father.

 the displays are not elegant yet, I will replace the pink, blue and yellow boxes an stuff for bubbled tables, and other things which people might express an interest in.
  The future of this project will incorporate local file images offline and web based images.

Can Gedcom format be better, and by validated proof of facts to be displayed?

   Ok I gave it allot of thought and I am giving in a tad to both side while maintaining a easy xml database. I am looking to the future where genealogy databases will grow beyond even being able to open a file on your computer to edit it.

  Here is a thought I plan to have four separate xml files link to each other which will reduce the size of a file. So far this project will contain four main files as follows

Example you can have one single census image (ASID 546) with 6 family members. well when you look at the actual image you create an interpretation line for each person. Each AIID line will link back to the corresponding APID and all 6 AIID will link back the same source file ASID 546

  Think of it like the person being the family ID, and all the records are like children to that person. It is like having a double navigation inside the file structure.

Here is our 2010 project of the genealogy xml database driven by classic asp.

multi xml db is in progress beta version 4.0 this is work in progress and items have not been activated just yet!!!!!

Talking to a few IT professionals with interest in genealogy have also seen how past standards don't fit the ideal helpful software to enter, display or store ALL of the information. Such information like family photos, scanned documents, saved record images from the web where really never supported 100% by past software programs. An example of that is you could use a software upload or add a photo to a scrap book display. The moment you wish to use another program an export the data, the export file function dropped a large percentage of entered data and notes and 100% of images in a scrape book. Then when importing it to another program, that new program would exclude even more data because it  did not see the tag or data as important enough to add it.

   Now those out their like my self would love to have a system to cover all needs of the genealogist. This left people like myself to outright build our own. Even if other systems can not keep up, we know how xml is flexible enough to take this xml format and convert the data out to any other program via xslt.  And the same goes in the other direction but takes long to write such flat file converts to rewrite a file into a reasonable xml structure, then pass that new file through another xslt to display that information into the four separate xml files that I propose.