Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generalize BIDS common principles as a "data structure standard (DSS)" #66

Open
yarikoptic opened this issue Mar 19, 2024 · 0 comments
Open

Comments

@yarikoptic
Copy link
Contributor

Yet another idea from a recent road trip with @effigies which I am trying to put to bytes before it is forgotten.

BIDS itself was built on some original principles in how to organize/name files and what metadata to extract and where to place it. We already have a good number of common principles defined in https://github.com/bids-standard/bids-specification/blob/master/src/common-principles.md but they

  • hardcode some specific decisions (sub-*/ folders at top level)
  • do not provide a generic guidance for how metadata is "summarized" in {entities}.tsv etc.
  • mix generic principles with some "BIDS or neuroimaging specifics" through examples or explicitly listing some specific entities
  • some (Inheritance) are still subject to debate

So the idea is potentially to see redefining/extending Common principles as generic rules to produce BIDS itself or any other BIDS-like (#62) standard which would potentially have different entities, metadata fields, file formats, default folder levels from some entities. So pretty much would be a different src/schema to drive it.

Initial suggested codename could be DSS: Data Structure Standard, so BIDS is just a Brain Imaging instance of the DS.

Here is some of the common principles aspects with some of the issues discussed in the scope of BIDS-2.0. I think that if we decide on generalization of common principles so they do not carry any specifics (formats, specific entities etc) in them, and formalize some missing (e.g. specification/decision on what goes into an {entity}-{value}/ folder) ones, it would be great to develop even more generic rules which might later be adopted by other communities, but also might simplify tooling by separating principles from specifics (which we already kinda doing with schema)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: BIDS 3.0
Development

No branches or pull requests

1 participant