Add a compulsory header to every JSON file

[tsalo]

https://groups.google.com/forum/#!topic/bids-discussion/TjxOKEB1DD4

add a 'header' block to every JSON file that specifies the type of parameter file that it is and a spec version. This makes it a bit easier to verify that the file is what you think it is. This is particularly useful due to the very few mandatory keys in the files.

Original authors: @ccraddock

[jbteves]

Hey @tsalo if you're not part of the group you unfortunately can't see the discussion.

[tsalo]

I don't think that's a fixable issue, unfortunately. But the BIDS google group should be open-join. I know it's not optimal to require people join a google group to access the original discussion, but it's best route available, I think.

[robertoostenveld]

add a 'header' block to every JSON file that specifies the type of parameter file that it is

How would this be different than using the information that is present in the JSON file name and especially the suffix, i.e. T1w or eeg, just before the extension.

... and a spec version

Would this open the possibility for having filees within one dataset complying to different versions of the specification?

[sappelhoff]

Hey @tsalo if you're not part of the group you unfortunately can't see the discussion.

@jbteves

I just tried in a private browser (not logged in or anything) and I could see the discussion :thinking: the settings for the bids-discussion google group are "open", so I don't know what went wrong

Screenshots:

[jbteves]

Hm, today I don't get the same error. Weird. Thanks for checking on it.