This issue is open to keep track of discussions / things to do following BIDS-derivatives meeting :
We need an example in BIDS-Prov spec on how to include custom code for some of the steps
The file-level provenance that we had in older version can be more intuitive when writing the provenance of a single file and should probably included back in the spec
This issue is open to keep track of discussions / things to do following BIDS-derivatives meeting :
.prov.json
and not.prov.jsonld
to be simpler for the devs who know json (suggestion by Arnault)