About context

[cmaumet]

Update proposal for BIDS Prov (BEP028)

by @yarikoptic in #125 (comment)

• would not need explicit @context (potentially related: #[ENH] Add ContextURI to allow to define the context for the entity values bids-specification#1939)
• it would be for the bids-prov tooling to extract those, equip with ids and add to the graph

[cmaumet]

@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.

• This probably means we have to keep the context in (unless we can have the context in a separate json and concatenate both files?).
• About the identifiers, this is indeed something we could look into (using blank node) but this will be limited to the cases where we do not need to cross-reference a particular object (in practice I am not sure this will happen often).

[yarikoptic]

I think that particular quote relates to

• JSON and BIDS-Prov #146

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

• [ENH] Add ContextURI to allow to define the context for the entity values bids-specification#1939

[yarikoptic]

if we are to avoid possible divergence from different .jsonld files pointing to different @context -- could be a job for BIDS validator (jsonld component) to warn if that happens. This way we would stick with duplicated explicit @context across all jsonld files.

[cmaumet]

This issue was taken into account in the current version of the BIDS-Prov specification. The context is added when aggregating the various provenance traces across files in the BIDS hierarchy.