4 ms·
The proposed format is reasonably same, but you really want to prevent people from writing them by hand, and adding a bit of metadata to describe the column dat
by webmaven 5y ago
The proposed format is reasonably same, but you really want to prevent people from writing them by hand, and adding a bit of metadata to describe the column data types at a minimum, and ideally more information such as allowed values, semantics, etc.
To that end, I suggest that putting the tabular data file, along with a metadata descriptor file, inside an archive format (zip, tarball, etc.); that would put just the right size speed-bump to encourage accessing the data through tools and libraries (though if someone is just a bit determined, reading and editing the contained data directly isn't actually impossible or forbidden).
All that said, if you want a better tabular data interchange format badly enough that you're considering devising one, you should probably look at using something even more featureful, like SQLite:
https://www.sqlite.org/appfileformat.html https://www.sqlite.org/appfileformat.html
- LeonB 5y agoI put some work into creating a standard, csvz, for putting csv files and their metadata, into a zip file. https://github.com/secretGeek/csvz https://github.com/secretGeek/csvz It’s a pretty powerful concept. SimonW’s preferred technique of using sqlite as the means of exchange is also very powerful. Particularly when combined with all of the utils he maintains.
- hermitcrab 5y agoBeing able to create small tabular datasets by hand is incredibly useful to me (doing support for data wrangling software). Having an optional associated meta data file would be useful though.
- webmaven 5y agoAre you really typing the data directly into a csv file, or are you exporting csv data from something like a spreadsheet?