Short description of overarching theme/goals behind BIDS 2.0 . To make BIDS
- more flexible as capable to accommodate new fields of neuroscience and use cases and possibly avoid breeding of "BIDS-like" offsprings
- more consistent:
- added from below by @tsalo: address any inconsistencies or inefficiencies that we had to incorporate into BIDS to maintain backwards compatibility. For example:
- dropping either IntendedFor or B0FieldIdentifier/B0FieldSource,
- removing deprecated elements like the phase suffix,
- and addressing how space is used inconsistently across modalities.
- see issues labeled with "deprecation" (most should get addressed)
- see issues labeled with "consistency" (many should get addressed)
- more modular
- more tools-friendly
- even more assumptions should migrate from human written documentation into machine-readable form (schema, and auxilary metadata, such as
DatasetType etc)
- more user-friendly
- largely via "more consistent"
- some rules could be relaxed or made more stringent to again reduce ambiguity
- easy to adopt/migrate to: analogy could be "python 2 to 3 migration" -
Some operating principles
- do not touch/modify supported data file types -- that would simplify migration (e.g. simply via their symlinks)
With that in mind, not all issues in this repository will be approached for 2.0. Please vote with 👍 or 👎 on existing issues
some items which were removed etc
Postponed/reconsidered from initial composition:
- make BIDS better "integrated" in the Web ecosystem, i.e. to become part of the linked web data
Removed/heavily rephrased:
- should either remain compatible with BIDS 1.0 as any BIDS 1.0 dataset would remain compatible with BIDS 2.0. (Exclusions might happen, should be weighted through usage)
Robert: What would be selling points for users to migrate to BIDS 2.0?
Ariel: User concern -- "should I now duplicate my dataset?"
- @yarikoptic: in dandi-cli (
dandi organize) we solved it in part via "symlinks"
- @effigies : git branches could be used as well if datalad is used
Short description of overarching theme/goals behind BIDS 2.0 . To make BIDS
DatasetTypeetc)Some operating principles
With that in mind, not all issues in this repository will be approached for 2.0. Please vote with 👍 or 👎 on existing issues
some items which were removed etc
Postponed/reconsidered from initial composition:
Removed/heavily rephrased:
Robert: What would be selling points for users to migrate to BIDS 2.0?
Ariel: User concern -- "should I now duplicate my dataset?"
dandi organize) we solved it in part via "symlinks"