Chris Markiewicz

To be clear, by "grouping entity", I mean one that can be varied without changing the overall meaning of the files. Different `part`s or `echo`s indicate multiple files that should...

Dismissing my review request, as I don't think this should be in the spec, and I don't have a suggestion to make that would get me to approve this. I...

Short term fix is to add selectors to only apply the mutex for BOLD images: https://github.com/bids-standard/bids-specification/blob/5fc3528fb9cad222cb4dadcedf218b2457fc2674/src/schema/rules/checks/func.yaml#L95-L106

> Even the DICOM definitions might not be ideal: > > * "Time in seconds needed to run the prescribed pulse sequence" is very MR-centric > > * "The time...

@yarikoptic Please see #1974, and a paired example (https://github.com/bids-standard/bids-examples/pull/499) that demonstrates backwards compatibility of this change.

This fails because TaskDescription is defined to be a string, not because extra fields are not permitted. Extra fields have been permitted for MRI data the entire time.

Just a note that the schema validator treats all sidecars uniformly, as we do not construct one omnibus JSON schema, but a collection of partial schemas. An additional check could...

I believe @yarikoptic had a proposal to reserve the `X-` prefix to permit nonstandard fields to be used with no possibility of clashing with future standardization. You could also imagine...

Niworkflows shouldn't be that large... Perhaps we just need to exclude test data from wheels? I'm also okay with splitting into a separate package.

Let me have a look server-side.