As an aside if we want a human-readable configuration format that's more flexible than JSON I would personally prefer YAML. It's much more standard than any of the JSON variants and can encode all the necessary structures.
-- Michael Mior michael.m...@gmail.com 2016-06-06 16:51 GMT-04:00 Michael Mior <mm...@uwaterloo.ca>: > Right now none of the examples are strictly JSON anyway. There are several > different JSON supersets that we could potentially use. It might be nice to > pick one so there's at least some kind of standard. > > https://hjson.org/ > https://github.com/timjansen/hanson > http://json5.org/ > > -- > Michael Mior > michael.m...@gmail.com > > 2016-06-06 15:27 GMT-04:00 Julian Hyde <jh...@apache.org>: > >> HOCON is a superset of JSON that makes it easier for humans to edit JSON >> files. For example, it supports multi-line strings, file inclusion, >> comments. >> >> Should Calcite support HOCON in addition to strict JSON for model files >> any other config files? What should be the suffix of such files? >> >> https://github.com/typesafehub/config < >> https://github.com/typesafehub/config> >> >> Julian >> >> >
