DOC: Revise guidance on file format selection and introduce downstream-oriented principles #670
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR revises the “Generic guidelines” section of the BEP Guidelines to clarify and expand the community's position on selecting file formats.
The original document presented a weak and somewhat outdated recommendation for format choices, including the
bvec/bvalformat as a positive example, despite its known limitations. This PR removes that example and introduces a new subsection: “Choosing file formats: downstream- vs upstream-looking”.Key changes:
These revisions aim to make BIDS more usable, accessible, and sustainable by encouraging choices aligned with open data science ecosystems and modern computational workflows.
No changes to the BIDS specification or schema are included in this PR; it solely updates guidance for BEP authors.