I completely agree. I gave it a decent amount of thought and pulled the trigger, and went with YAML. Not because I think YAML is the ideal end target for the d

I completely agree. I gave it a decent amount of thought and pulled the trigger, and went with YAML. Not because I think YAML is the ideal end target for the datasets. Likely it would be best represented in a database with a custom CMS and outputted in a more robust format such as XML. Though considering that the current archives for the indigenous languages are primitive in their documentation, I think YAML will get the project started. It is just ever so slightly easier to get contributors started. As the project matures (and before it gets to complex), I will convert all the YAML datasets to something more appropriate and build the tooling to handle it in tandem. Again, you are correct, and I will add my reasoning to the current documentation.