search

FamilySearch / gedcomx

An open data model and an open serialization format for exchanging genealogical data.
http://www.gedcomx.org
Apache License 2.0
355 stars 67 forks source link

What are the benifits of the fragmented XML structure #210

Closed joeflint closed 11 years ago

joeflint commented 11 years ago

I have a built a gedcomx file using the gedcom converter. I understand how the individual elements are saved as separate files and placed into appropriate folders. What I don't understand is why this project created the XML this way.

My day job is a developer in a corporate (insurance) IT shop. I work with an XML standard, ACORD which was developed by the insurance industry. Based on my experience I would have expected one file starting with a tag, ending with and all the other tags in between.

I do not mean this as criticism. I just would like to know the reasoning behind the decision. A list of issues where this was discussed or other documentation would be great.

stoicflame commented 11 years ago

Hi. Welcome. We're glad you're here.

I think most of your questions are addressed here:

http://familysearch.github.com/gedcomx//2012/07/03/file-format-jeers-cheers.html

If you'd like to weigh in on making adjustments to those decisions, please leave your comments at #183, #184, and #185 as appropriate.