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

[EASY/DOC] Document the reasoning around requirement levels in BIDS #1422

Closed
sappelhoff opened this issue Feb 20, 2023 · 0 comments · Fixed by #1444
Closed

[EASY/DOC] Document the reasoning around requirement levels in BIDS #1422

sappelhoff opened this issue Feb 20, 2023 · 0 comments · Fixed by #1444
Assignees
Milestone

Comments

@sappelhoff
Copy link
Member

          > Should we continue with the field being REQUIRED or change it to be OPTIONAL?

Why was it required in the first place? I don't know if we have this written anywhere, but here's what's in my head when making these decisions:

  • REQUIRED: Data can't be interpreted without this information (or the ambiguity is unacceptably high)
  • RECOMMENDED: Interpretation/utility would be dramatically improved with this information
  • OPTIONAL: People/tools might find it useful to have this information

Every required field is a barrier to somebody using the standard, and you're basically stating "Data without this field might as well not be shared".

Originally posted by @effigies in #981 (comment)

@sappelhoff sappelhoff changed the title Document the reasoning around requirement levels in BIDS [EASY/DOC] Document the reasoning around requirement levels in BIDS Mar 8, 2023
@sappelhoff sappelhoff self-assigned this Mar 16, 2023
@sappelhoff sappelhoff added this to the 1.9.0 milestone Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant