I'm currently merging changes to the bids specification into our repository to keep us in sync with those changes.
The point of this issue is to note where there are conceptual merge conflicts (rather than just git not knowing which line information should be on!) so we can review and discuss them.
The paragraph below comes kinda out of nowhere in the main specification at the moment - it seems to be nested under the rec entitity but I don't think it is really related to that point. I think it probably needs its own heading. "Additional metadata"?? What's a good heading?
Some meta information about the acquisition MAY be provided in an additional
JSON file. See Common metadata fields for a
list of terms and their definitions. There are also some OPTIONAL JSON
fields specific to anatomical scans:
(Table not shown, but we have added two rows to it in BEP001)
I'm currently merging changes to the bids specification into our repository to keep us in sync with those changes.
The point of this issue is to note where there are conceptual merge conflicts (rather than just git not knowing which line information should be on!) so we can review and discuss them.
The paragraph below comes kinda out of nowhere in the main specification at the moment - it seems to be nested under the
recentitity but I don't think it is really related to that point. I think it probably needs its own heading. "Additional metadata"?? What's a good heading?(Table not shown, but we have added two rows to it in BEP001)