Stefan Appelhoff

this was mentioned in bids-standard/legacy-validator#571 already, which I'll close as a duplicate And it should be an error IMHO (warning is not enough)

~Perhaps the `uniqueItems` key can be added for the schemas? https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.6.4.3~ edit: nope, just saw that `uniqueItems` only works for "arrays" ... we would need a similar functionality for objects...

Hi @JonteP, this may be of interest to you: - https://github.com/bids-standard/bids-specification/issues/914

> Found an old install of 1.3.4 on the HPC and interestingly it did not fail in this case. See also bids-standard/legacy-validator#648

@rwblair if somebody wanted to make a PR for this issue, are there some caveats with regards to how they can open and read a file? E.g., in Python I...

this enhancement would be a neat and powerful way to improve validation and BIDS usage ... and just to draw attention back to another important (IMHO) and generalizable feature, please...

I think a **part** of this issue could be solved with [JSON schema conditionals](https://json-schema.org/understanding-json-schema/reference/conditionals.html), but that wouldn't allow us to send out targeted warnings more specifically, see: https://stackoverflow.com/a/38781027/5201771 > Either...

also related to https://github.com/bids-standard/bids-validator/issues/945 ... but the feature request here goes beyond that issue.

@rwblair will your new package https://github.com/poldracklab/cmixf-js be easily integrated into bids-validator?

bids-standard/bids-specification#411 is now merged, we should "deactivate" current unit validation ASAP @rwblair