Stransky Family Tree

SFT 2009 Genealogy Projects XML in 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.

Genealogy website display scripts project?

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.

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.

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 seperate 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

	xml file#1	xml file#2	xml file#3	xml file#4
	Family Grouping	Person QuickView	Interpreted Data	Actual Sources
1	AFID>> auto# Family ID	<<APID>> auto# Person ID	AIID Auto number	<<ASID Auto source ID
2	HUSB fathers apid#>>	CHIL child of <<afid#	LPID linked to person <<apid#	TYPE type of source
3	WIFE mothers apid#>>	SEXX male or female	LSID Linked to source asid#>>	CLAS classification of type
4	-	GIVN given names	GIVN given name on source doc	TITL title on classification document/archive
5	-	SURN surnames	SURN surname read on source doc	REFT ref tagging number identify by...
6	MARD marriage date	BIRD birth date	STAD start date on source doc	RECD recorded date
7	MARP marriage place	BIRP birth place	STAP start place on source doc	RECP recorded place
8	DIVD divorce date	DEAD death date	ENDD end date on source doc	FILD filed date
9	DIVP divorce place	DEAP death place	ENDP end place on source doc	FILP filed place
10	NOTE	NOTE	NOTE	filename/location
	^^^^^	^^^^	^^^^^	^^^^^^
	This is the family bond group. the husband and wife fall under a FAMILY or group ID. listing children is not needed on this file	this is the genealogists quick navigation and guest view file. From this file it is a one click to navigate pedigrees or family groups. OR just one click and see and display all source documents collected on a person.	This file is to Strictly interpret the source files into text for each line per person. say you have that census with parents and 4 children. Each of the 6 people will have their own line.	This is strictly for gathering source documents and images. Say you have a census image for 1900 us NY. You would upload it, and selected proper pull downs which match the documents you gather

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.

multi xml db is in progress beta version 4.0