These are chat archives for frictionlessdata/chat
. #thinkingoutloud re Using the JSON Table Schema with JSON data.
What happens when someone has their tabular data as json data. I’ve noticed this recently in many cases of vega sample data for their demos and I think it is a common pattern esp for inline data.
Strictly, these are not “tabular data resources” because the source data is not CSV. But in a sense they are just that tabular data already pre-processed to JSON. Now, I don’t think these should be considered Tabular Data Resources because JSON is not CSV and the CSV matters (think non-tech user with Excel - JSON does not work).
However, you can use the JTS for this JSON just like for the CSV. And, from the point of view of things like a graphing library, this is like CSV but even better - the casting of CSV to JSON is already done!
I’m wondering about how we handle this - if any ...
year is an integer with 4 digits. It feels like we're talking here about a string. I suppose it's because of overall lack in the spec strict concepts of data representation as a string and cast/typed/native/parsed values.
yearI suppose is something that (a) valid integer in spec terms (b) >= 0 and <= 9999
@roll TS = Table Schema. Yes, i wrote it so it does not require CSV :-)
But Data Resource does and that is what I was talking about …
Graph data packages, or “Universal Data Packages” that can encapsulate both tabular and graph data.
@jobarratt have you told them about data package views stuff and pointed them at the issue on that frictionlessdata/specs#77.
I’ve also got a huge update on views that i’ve been working on over the last few months that is nearly ready - i can paste it as a work in progress there.