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

Inheritance: Further Relaxation allowing multiple files per directory #1195

Open
yarikoptic opened this issue Aug 10, 2022 · 5 comments
Open

Comments

@yarikoptic
Copy link
Collaborator

Follow up/continuation to #1003 as suggested/discussed in #1003 (comment) . Extracting here:

For that latter case (e.g. task-rest_bold.json and acq-tricky_bold.json) we could have removed this requirement ("subsequent ... is a strict superset ...") and require that for such cases of unclear ordering, order is arbitrary but metadata files MUST NOT have identical metadata fields overloaded (thus order would not matter).

        if multiple applicable files have the same number of entities,
        they could be ordered arbitrarily among themselves and they MUST NOT
        contain overlapping metadata.

It would be up for validator to ensure adherence to such a principle. This would "relax" inheritance principle further and allow for arbitrary combinatorics if so desired for some studies, e.g. mix in of _task-rest_bold.json and ses-pilot_bold.json, _space-X and _desc-Y in bids-standard/bids-bep016#32 etc.

@Lestropie
Copy link
Collaborator

@yarikoptic Finally got around to this; see Lestropie#5.

@effigies

This comment was marked as off-topic.

@effigies

This comment was marked as off-topic.

@Remi-Gau
Copy link
Collaborator

  • agree to start a separate thread because this sounds actionable
  • maybe just me but I think that the rephrasing is just making more explicit what was in the original point 4.

@effigies
Copy link
Collaborator

Okay. New issue created. Will hide these posts.

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

No branches or pull requests

5 participants