2 ms·

This is an API for very small datasets (daily time series data). The goal should be accessibility and readability over saving a few bytes. I'm not saying it's

by watty 10y ago

This is an API for very small datasets (daily time series data). The goal should be accessibility and readability over saving a few bytes. I'm not saying it's ideal, I just think the snark is unwarranted considering how common it is. I just checked InfluxDB and they follow a similar model (even more verbose). https://docs.influxdata.com/influxdb/v1.2/guides/querying_data/ https://docs.influxdata.com/influxdb/v1.2/guides/querying_da... Checked a few more and I believe they're the same - Microsoft IoT, Predix (GE), etc.

keredson 10y ago
that example you give does not follow a similar model. it defines the columns once (not repeated w/ every observation): "columns": [ "time", "value" ], and then the observations as a list of lists: "values": [ [ "2015-01-29T21:55:43.702900257Z", 2 ], [ "2015-01-29T21:55:43.702900257Z", 0.55 ], exactly as i suggested in the "even if they were wedded to JSON for some reason" section of my original explanation.