>I would like a clearly documented YAML subset that left out some of the more complex stuff and avoided a few 'more than one way to do it' features. I looked f

>I would like a clearly documented YAML subset that left out some of the more complex stuff and avoided a few 'more than one way to do it' features. I looked for one some months ago and the closest I found was https://github.com/crdoconnor/dumbyaml https://github.com/crdoconnor/dumbyaml, which is a parser implementation, not a standard. Out of projects approaching the issue from the opposite angle ("smarter JSON"), I think HOCON (https://github.com/typesafehub/config/blob/master/HOCON.md https://github.com/typesafehub/config/blob/master/HOCON.md) is the most promising. Compared to Hjson (http://hjson.org/ http://hjson.org/), it is less likely to confuse the user with how trailing commas are treated in unquoted strings and generally appears to not compromise on strictness for convenience. That said, I agree with TillE: as soon as a configuration file format I work on needs any logic or expressions I will strongly consider an embedded scripting language like Lua or Tcl in order to avoid instantiating Greenspun's tenth rule for configuration.