Our Gedcom XML
What would it look like?

For just a simple tree outline, or navigation of a family tree you only need simple INTERPETED INFORMATION. this navigation is strictly the genealogist FAMILY OUTLINE! this does not include Documents and fight over what was his real spelling of the name, THAT comes later in DOC sources.
  This file is strictly the navigation outline of the connections the only reason we might have birth and death dates is to navigate the tree outline structure and help put people in order has of births and deaths. this helps when you have five john smiths in your tree spanning over 300 years.                        

The lines above the ____________ These are mandatory to properly navigate display pedigree and minor dates to locate the person you are looking for in a name list.
  The lines BELOW are just optional at this moment to say link the genealogist <GG>ID</GG> in the outline who entered the info. when trees become so big it is hard to say who is who and what data maybe true or not so...
  I propose <HH></HH> as a caretaker in that part of the family tree who can be a contact in that part of the family and who can update and add info in that area of it. A Care taker can not modify other outlines if there is another taker already listed.
  WHY DO THIS? with all the fraud going on, you really don't know people (persons) 12 branches out? SO when they contact you wanting vital info, you send them to the caretaker in that area of the extended family tree.
  Say you have 4,500 people in your tree, you send them to caretaker ID736 who controls only 125 people records They say they know them and will work with them updating stuff. Because one caretaker can not EDIT MODIFY records of LIVING people under another caretakers watch.

Two ways let extended family take care of people near them in the tree, or have no caretakers and only the geneologist takes care of it all.

Ok from this point just the simple information of this xml can be shared as is with a public view on the web. Visitors will be able to view names, dates, pedigree and dates. They will also be able to navigate the family tree outline jumping from person to person.
  A visitor can click a name and contact the genealogist OWNER or the approved caretaker in the tree to comment on data, information or asks about details. This allows a limited amount of scanned documents like birth certs and papers regarding living people to be viewed by the public or shared openly with people who have NO NEED TO KNOW.

Ok I mentioned documents, how to get documents and events entered? Not every person has a marriage, or a divorce or baptism and immigration travels. But if anyone really comes down to agreeing that these are specific events that can effect more than one person. Would you really duplicate a ship record 10 times over in ten different peoples INDI records as nodes inflating the size of you DB more than it needs to be? No.

Lets look at it this way

an eventID is a key number entered into a database.

then you need a Date maybe a place. and maybe what roll the person took at that event.

Lets say a marriage certificate you have shows the Bride, Groom and witnesses that are in your family.

This is only to link events to people, they effected if you noticed The the there are two events ID # 32 and 33, 32 points to person #14 who is John Smith and #35 who points to Jane Hallaway. But both records are linked to SOURID#14

You said cut down the number of repeats inside a person INDI area, but this does it also? Yes but it is less text because the real repeated into is in the SOUR document file. Say you want to view photos, scans, or documents that document say in this case #14 sees that two people in the tree are linked such as # 14 and 35 and can display the names and rolls they played. From there you can navigate back to the events or people outline.

Fine, Fine, what About census reports and all that info. Great that covers that.

So you can find everything you need that I can think of. If it were a census your have a doc type, title number of census, place in census, in description you can give roll and film information and other input text.

Lets look back at where we are, Say you have 8 people in a family Census, that means there will be

8 X person ID's in the navigation xml
8 X Events ID's showing rolls each person ID played
1 SOUR doc ID showing an image record of such.

That images is on a computer or website like so

C:/xGedcomarchive/14/4653.jpg
root/xGedcomarchive/14/4653.jpg

Only in the software the setup you choose C drive or web based.