How SFT compares to GEDCOM

Welcome, I have created many large xml databases which store archives of text, images and pdf types. Also I have made them very efficient so the thought was to create a gedcom standard for myself and others to use if they wish.

GOALS:

1. compact tags.
2. compact reoccurring text in nodes.
3. compact various events and sources to a simplified node.

To start, lest view the GEDCOM house hold which is used for family groups and children. I will call it Simplified Family Tree xmls or "SFTxml"

So with a parser you have a household view to display from picking a short cut link with a INDI#6 say John Doe. With xpath you filter for (hid='2') husbandID. Note that there will be household matches
first loop matches
gid=2 sees a wid=7 and
then again gid=4 with 2nd wife=33.

the web base parse loop will the PID.xml and will grab and display each of there names and sort them by date order from birth for each marriage/bond date.

John Doe #6 (hyperlinked)
+1st Wife Name #7 (hyperlinked)
  1st childs name #26 (hyperlinked)
  2nd childs name#27 (hyperlinked)
  3rd childs name#28 (hyperlinked)
+2nd Wife (hyperlinked)
  1st childs name#45 (hyperlinked)
 
What does this PID.xml you speak of look like?

Next how to store Events and Source documents the best and most compact way....

If you followed so far how Household group xml links to the Person ID xml you will see how the EID.xml  eventID store various events in a person or persons lives.

Also many people have complained what to call an event, do we say Baptism or Christening or Jewish or Indian way and types, guess What IT DON'T MATTER with this method. 

The typical way gedcom tries to create a tag for every possible event out there. This makes a everyone suffer trying to create a Rosetta stone to export xml standards to other standards.

I guess I summed up the problem hitting people for years about standard making.

1. Everyone is creating various "tag named events" like immigration, baptism, birth, christening, and so on. This hinders religious beliefs, culture descriptions and so on.

I ask this, all the above are events, all one has to do is see if it happened at a place, time it was an EVENT. what people wish to call that or tag that has no importance at all on xml structure.

How is that, put you date in the node and place.
<date> </date><place></place><type>(select it)</type>

so look at it this way, your in a computer program or an online interface. Pull down a selection bar and pick Baptism, Birth, Immigration, Divorce, Murder, Land Purchase, Hair Color, DNA string, etc...

No Matter what, whatever it was was done at a time or place, we need to stop creating date and place tags INSIDE an untold limitless description of tag names.

Lets reverse that and create a list of events names that can be select which fit in the standard time and place of event.

If you read this fully feel free to share it with the others if this might be a big step to getting standardize quicker.

Simple

Image archive of documents, pictures, photos, census records, roll film and all. Take the last example above for a baptism Event record#92, the DID DocumentID attached is linked to a SourceID SID=453

So you can see there is still room to make changes. GID and PID work hand in hand for the navigation and display templates. This is really the genealogist navigation outline and quick view summary.

The EID and SID work hand in hand and can be used by archive sites as a stand alone system also.

You have all your documents in SID. And EID in the facts off the documents. Lest use a census

You see 8 people in a household, you will make 8 EID entries to describe each persons on the census but they will all point back at the same image or source document.

From either EID or PID you can link them or create new people when needed which will auto link to each other.

 "..**.." indicates other items need to be added and clarified, I hope you understand and feel this is simplified. I will next go into a detailed or expanded understanding of this format.
The above was to cover the very basic must have format. Next is to include all those various LABELS no one can agree on tagging the nodes in a selectable standard format.