[dan_linder]

As someone who's dealt with configuration files for many years in formats such as ini, xml, json, yaml, etc. not to mention all of the custom binary configuration file formats such as the Windows registry, or other system bespoke configuration file formats, in the end what works best for me and possibly most people is a configuration file format that is human readable and maintainable with a simple text editor or even basic command line tools.

I'm glad most of the industry has got away from the binary blob for configuration file, but I don't see great advances that the new configuration file formats such as TOML or others I'm not aware of provide above a basic yaml or json file.

my personal preference is yaml followed by jason, and from what I understand the ability to convert between those two formats is because both have feature parody with the other. I might be wrong, but as long as a system can ingest either of those I find it my preference to use that over something else. maybe if I had a third place file format it would be ini, but it has a lot of restrictions on the type of data structures it can convey.

[logicallee]

Thank you. I agree, I think yaml is the right choice for this application. Thanks for your thoughts in both comments you posted.