jsonld at any level

[cmaumet]

Update proposal for BIDS Prov (BEP028)

Proposal by @yarikoptic

• allowance of presence of .jsonld at any level (not even subject to inheritance principle limitations since nothing would really to be inherited -- they are to be composed into the graph):
• if not specific to any particular file, could in effect get _prov suffix, thus mimicing dataset level prov.jsonld. so there could be

      * `prov.jsonld`
      * `sub-1/sub-1_prov.jsonld` -- wide subject relevant provenance
      * `sub-1/ses-2/sub-1_ses-2_prov.jsonld` -- specific for the session
      * `sub-1/ses-2/func/sub-1_ses-2_prov.jsonld` -- for all the functionals
      * `sub-1/ses-2/func/sub-1_ses-2_task-rest_bold.jsonld` -- specific to those `sub-1/ses-2/func/sub-1_ses-2_task-rest_bold.*`
        This way tools would have flexibility to express themselves at the level they are operating at (file level, or group of files etc).

[cmaumet]

@yarikoptic -- the rationale behind having all the _prov.jsonld files in a single folder was to make it easy to delete all of them at once if needed.

But I see your point and I can't see why we should not make this possible. @satra: just let us know if you think otherwise.

@bclenet can you help us and update the gdoc accordingly and let us know of any issues you identify? Thanks!

[kabilar]

Thanks all. I agree with the above proposal.

Clarifying question. Since the inheritance principle would not be in effect here, ideally would every data file need a sidecar *.jsonld file?

[yarikoptic]

That is what BEP028 indeed suggests that as one of the ways. I have concern though with potentially nearly doubling number of files in the dataset that way, which I think should be avoided unless there is good rationale and indeed the PROV record could not be just "inherited". That is why IMHO there should be the another way at .json file level:

• I just reopened https://github.com/bids-standard/BEP028_BIDSprov/issues/146