Open cmaumet opened 5 days ago
@yarikoptic Thanks for the suggestion. I do understand the value of simplifying the information that is required in BIDS-Prov and I am happy to discuss how we can achieve that (simplification is indeed a driving idea in the specification of BIDS-Prov).
it would be for the bids-prov tooling to extract those, equip with ids and add to the graph
Relying on BIDS-Prov tooling to recreate a valid JSON-LD from BIDS-Prov documents is to me a point of weakness. This would require sustained effort on the BIDS-Prov tooling and, unfortunately, I think that long-term support is not guaranteed (although I hope this will happen clearly).
I am keen for the BIDS-Prov document themselves to be valid JSON-LD as this will make it possible to benefit from the JSON-LD ecosystem of tools.
I think that particular quote relates to
I agree that for a full formed .jsonld there should be @context
defined within -- we should not lobotomize .jsonld
if it is a .jsonld
(not just .json
).
I only wonder if there is a way to centralize @context
reference somehow, e.g. at the top of the bids dataset and then have relative URLs pointing to it. If not -- I am ok. But might be worth bids-validator check to ensure that @context
is consistent across all present .jsonld
files and warn otherwise. Overall I think also relates to
Update proposal for BIDS Prov (BEP028)
by @yarikoptic in https://github.com/bids-standard/BEP028_BIDSprov/issues/125#issuecomment-2492133921