Genealogy Gedcom
XML standard suggestion

Understand the structure of a gedcom file. This is a flat file layout so.

Well how would you control the files and convert them  to gedcom or another standard? EASY

By using an xslt a person can loop through each of the files

There are gedcom converters and I have made one myself. So if you have a GEDCOM you would convert it to a xGedcom.xml

This xgedcom.xml would be a pure xml structure as the Gedcom file itself. BUT now it is in xml format. Here is the tricking part is having to collect all the node that any particular software uses.

xgedcom.xml >>>xslt>>> FTM

xgedcom.xml >>>xslt>>> Ancestry

xgedcom.xml >>>xslt>>> Gramps

xgedcom.xml >>>xslt>>> or other typs

 What about all the dropped info and information that is snipped.
EASY, the developer of the xslt WOULD know say one platform does NOT use say "Shoe Size" so this is not a standard with other formats. They would command the node <ShoeSize>12</ShoeSize> like so.

Read shoe size >>>> output text under the INDI as a note:

<Note>ShoeSize: 12</Note>

So now when a xslt convert is done, a person can look in the notes/conc  tags and find all the non standard info like Blood type, shoe size, hair color, and favorite foods?
 
 What ever the data is or was it is not lost, but a genealogist can look there and move it to a new location or reenter information by looking at the notes or say call it "x-tags".

The next thing to explain the horrid long tag names like baptism, immigration, burial, marriage, divorce, land purchase, and so on.

** this has been the biggest hurdle for all genealogy software's claiming what names to use as the tags. AND it really is not the names that cause all the problems it is that many don't see that they are all "EVENTS, DATE, PLACE, NOTE, DOCs"
All we have to do is link them to who was involved by personID.

Why keep repeating immigration information 10x for each of those people in a family migration? There is ONE document event, link the people to the ONE event document.

Or even a marriage Doc, why repeat groom, bride, witness1, witness2, etc... in every persons block of info? Just list all the person to the ONE event Document and there roll.

Not every person has them all and some get more cluttered INDI area of data. Lets back up an examine a possible better way.

If one could agree that these are EVENTS that take place at a certain time in a persons life.

From the INDI xml Doc a person has a unique KEYID and and all known events would be like child nodes
<INDI>
   <FName></FName><SName></SName>
         ...... more nodes......
       <Event>456<Event>
       <Event>627<Event>
       <Event>76<Event>
          ...... more nodes......
</INDI>
------------------------------------
Now when the events have been link a second sweep can put all that persons chronological information in order from
Birth
Baptism
Marriage
Immigration
divorce
Death
Burial

YET next to each name will show an ICON that a document is on hand as a source record from the 4.xml

Birth            1901 (icon)
Baptism       1901
Marriage     1922(icon)
Immigration 1924
Photo            1927 (icon)
divorce          1935 (icon)
Death            1944 (icon)
Burial            1944

Another nice things is if you have family photos in your document control and all the multimedia files. say like so.......

Each INDI record would be link to the photo OR just by looking a the source records and you see a photo and want to know more the photo(DOCID) reference the EVENTID KEY and then displays all the people who are link to the event in there INDI child nodes to the event.