@simon if one wanted to maintain a mostly straightforward dataset in a GitHub repo, collaboratively with other people, potentially the public (i.e. โcrowdsourcingโ) โ would you suggest using CSV, JSON, or something else as the file format?
@avi @simon Just my .02โฆย Assuming you have a simple row/column structure and not something more complex you're trying to model) CSV is the "least common denominator" in terms of data, so it has the widest potential reach, as well as the least-likely to get mangled in conversion to whichever format needed for someone's particular usecase.
@avi either works great
I have a very loose preference for indented JSON because it diffs nicely and gives you integer/float/string/boolean types which you don't get with CSV
Edited 114d ago
@octothorpe @simon makes sense to me!