Use Case: elaborate extensions to the @context want to refer to that remotely (by URI) rather than inline #150
Labels
use-case
A (potential) use-case for ROLite creation, consumption or integration
This came up in the ro-profile discussion
see minutes of 2021-05-13 -- ro-profile-discussion
As a scientist in some data-management procedure adapting an elaborate (extending) profile, I want to be able to have slim and readable ro-create-metadata.json files that do not have to repeat all
@context
extensions inline.We already have and suggest ways to extend the
@context
by having it be an array ofThe suggestion here is that we could as easily have that extended to
Note: this adds additional preservation challenges - e.g. ensuring the JSON-LD context does not change beneat our feet, use semantic versioning etc. Since we do use
@context
URIs ourselves this boils down to ensuring profile editors are as diligent about sustained semantics as we promise to be.The text was updated successfully, but these errors were encountered: