Satrajit Ghosh

@bclenet - we should make sure the prov-jsonld documents go through a json-ld parser/validator.

could we simply say that an `@context` is optionally allowed, but if provided should follow `json-ld` specifications? we could formalize this in bids itself saying that a bids-specific context has...

@jAchtzehn - are you using this within a Nipype workflow? with nodes? if so, the SPM.mat file is passed along and copied by the underlying nipype mechanisms.

@jAchtzehn - i'm not sure i can follow what's going wrong here. here is an example of how a mask file is passed on to level1design: https://github.com/niflows/nipype1-examples/blob/master/package/niflow/nipype1/examples/fmri_spm.py#L277 could you please...

@jAchtzehn - there seems to be two issues here: 1. the redundancy of setting the mask image in certain recent versions if this is indeed fixed in SPM12, we can...

@anbai106 - unless you use the `--minmeta` flag, the json files should store all the dcmstack metadata in addition to the bids metadata. @mgxd - could you please verify?

@anbai106 - we still use dicomstack internally for the metadata. i am a little surprised that you do not get the full metadata. is there anyway you can share some...

one option is to add the provenance keys to any sidecar json as an option.

we wanted to separate it into a different file simply for simplification that a tool could write out provenance without worrying about the bids json spec for an entity. this...

in prov we separate the agent/software and the activity/process as separate constructs as each has its utility. here is an example of such a generatedby (more fields exist for processes...