Consider replacing TSV files with a fileformat that supports built in metadata

bids-standard / bids-2-devel

Discussions and suggestions of backwards incompatible changes to BIDS

https://bids.neuroimaging.io/

Creative Commons Attribution 4.0 International

11 stars 1 forks source link

Consider replacing TSV files with a fileformat that supports built in metadata #19

Open tsalo opened 4 years ago

tsalo commented 4 years ago

Contestants:

ECSV - https://github.com/astropy/astropy-APEs/blob/master/APE6.rst
CSVY - http://csvy.org/
See also - https://twitter.com/hadleywickham/status/946836547097251840

Original authors: Unknown

jbteves commented 4 years ago

What is the motivation for adding additional metadata?

tsalo commented 4 years ago

@jbteves could you clarify what you mean? The original proposal is a little light on information, but I think that the goal is to do the same thing as #25, but for TSV files.

jbteves commented 4 years ago

I see, so to use a format which allows both the tab-separated information as a table, and metadata for that table? The comparison to #25 makes things a bit clearer to me, thanks.

tsalo commented 4 years ago

I'm leaning against this (and #25). The data file/metadata file pairing works pretty well, and we'd have to either limit ourselves to supporting only file formats that support builtin metadata, which is not feasible across modalities, or have a mix of single-file and dual-file setups varying by modality, which is confusing.