[ENH][BEP028] Specification update for BEP028 BIDS-Prov

[bclenet]

This is a work in progress PR proposing a specification update for BEP028 BIDS-Prov.

Todo lists

• Road to community review - Top priorities BEP028_BIDSprov#167
• Road to community review - Secondary priorities BEP028_BIDSprov#168

Blocking points

• [schema] allow for an optional subdirectory prov/[prov-<label>] BEP028_BIDSprov#169
• [schema/validator] different usages of GeneratedBy BEP028_BIDSprov#170
• [ci] pdf rendering error due to "multiline links" BEP028_BIDSprov#171
• [validator] provenance files are considered as sidecars BEP028_BIDSprov#172

Associated BIDS examples

• [BEP028] provenance - study dataset + manual annotation #519
• [BEP028] provenance - fMRIPrep preprocessing #502
• [BEP028] provenance - SPM preprocessing #497
• [BEP028] provenance - heudiconv conversion #496
• [BEP028] provenance - dcm2niix conversion #494

[cmaumet]

@bclenet While thinking about the first two points on how to validate certain parts of the files I started to realize the nature of the changes that will be required of the schema to validate them.

@rwblair thanks a lot for this detailed overview. I second @bclenet's comment in that we were thinking of a much lighter validation using the BIDS schema (mainly making sure that the newly created files had a proper naming and that the keys inside the metadata files corresponded to what is in the spec). I was hoping we could focus on this first before we open the BEP for community review.

@rwblair @effigies: Could we plan a quick meeting to identify the remaining steps we need to follow in order to update the schema for BIDS-Prov (BEP028)? So we can have a clearer plan of when we'll be able to open for community review. Thank you!

[effigies]

@cmaumet @bclenet Let's schedule a call: https://www.when2meet.com/?33661829-Yw724

Please forward to anybody you want on there.