<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 3, 2017 at 11:25 AM, Byron Jeff <span dir="ltr"><<a href="mailto:byronjeff@clayton.edu" target="_blank">byronjeff@clayton.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
</span>Chris,<br>
<br>
I too took a tour of config file formats specifically for an IoT project.<br>
Specifically connecting Google Home to home built RasPi Zero endpoints<br>
using MQTT as the data transport. I just added 433Mhz remote outlets to the<br>
mix too. Upshot is that the endpoints need to be configured to know which<br>
MQTT topics to monitor for updates.<br>
<br>
The two I took a look at are YAML (<a href="http://yaml.org" rel="noreferrer" target="_blank">http://yaml.org</a>) and TOML<br>
(<a href="https://github.com/toml-lang/toml" rel="noreferrer" target="_blank">https://github.com/toml-lang/<wbr>toml</a>). Both have a design goal in mind to be<br>
human readable/writable while also being machine parsable. While JSON is<br>
great for machine to machine transactions, the others are better when you<br>
need to hand write a config in a text file. For me TOML looks like the<br>
winner.<br>
<br>
BAJ<br>
<span class="gmail-HOEnZb"><font color="#888888"><br><br>
</font></span></blockquote></div><br><br>While it doesn't meet your human readable need, unless you have the code, the Google SRE document talked about their Protocol Buffers which is supposed to be much smaller and faster than XML.</div><div class="gmail_extra"><br><a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a><br clear="all"><div><br></div><div>Leam</div><div><br></div>-- <br><div class="gmail_signature"><div><a href="http://leamhall.blogspot.com/" target="_blank">Mind on a Mission</a></div></div>
</div></div>