Chris Markiewicz

If you're not using any other derivatives entities, there should be no difference.

Hi all, this is just a note that I've got a package I can't build with `uv` because data filenames get truncated between the sdist and the wheel. If there's...

I can confirm this is resolved for my case as well.

We do check whether someone has both `.nii` and `.nii.gz` files, as this is a somewhat common issue. https://github.com/bids-standard/bids-validator/blob/932c782a556afea34346e994f655e03cf3e171fe/bids-validator/validators/nifti/duplicateFiles.js#L3-L34 A similar thing could be written for other formats, although it...

No, but it does create ambiguity about the data and frequently problems for tools expecting to retrieve a unique data file for a collection of entities. I would support making...

To save other reviewers time: [link](https://bids-specification--2019.org.readthedocs.build/en/2019/common-principles.html#examples) 

The issue is for channel enums, where it's generally permissible to use any of these in any `channels.tsv`, but many are mainly relevant to particular modalities, and have been listed...

cc @tsalo in case you remember things differently.

Just to add a related issue in the validator: * https://github.com/bids-standard/bids-validator/issues/85 Brain dump: * Schema publication * In-document: The schema.json file is bundled into every build (e.g., https://bids-specification.readthedocs.io/en/latest/schema.json) via readthedocs:...

One additional note, that didn't make it into those linked issues: Because of an inability to use `+` versions in `@bids/schema`, we moved from `schema-0.minor.patch+postN` to `schema-major.minor.patch`, where `minor` is...