4 ms·
Why not just define your schema using Protocol Buffers and use the [proto3 JSON mapping](https://developers.google.com/protocol-buffers/docs/proto3#json https:/
by int_handler 10y ago
Why not just define your schema using Protocol Buffers and use the [proto3 JSON mapping](https://developers.google.com/protocol-buffers/docs/proto3#json https://developers.google.com/protocol-buffers/docs/proto3#j...)?
On a similar note, text protos actually work very well as configuration files and are used by SyntaxNet/Parsey McParseface [1] and Bazel's CROSSTOOL config [2].
[1] https://github.com/tensorflow/models/blob/master/syntaxnet/syntaxnet/context.pbtxt https://github.com/tensorflow/models/blob/master/syntaxnet/s...
[2] https://github.com/bazelbuild/bazel/blob/master/tools/cpp/CROSSTOOL https://github.com/bazelbuild/bazel/blob/master/tools/cpp/CR...
- habitue 10y ago"just" sort of implies this is the most obvious thing to do, and for some reason he's eschewed this solution
- int_handler 10y agoBy "just" I mean this is a simpler solution (compared to JSONSchema), not that it is an obvious solution. I'm pretty sure the author does not know about this solution since using Protocol Buffers for configs is not a well-known use case outside of Google.