Reconsider MUST for implemenations to use their own copy of JSON-LD context

[elf-pavlik]

From today's call. Related to:

• Version JSON-LD context #103

There were also suggestions to relax it to SHOULD or even MAY. @pietercolpaert provided various resons why implementations MUST use their own copy.

[xdxxxdx]

I believe this should be marked as a SHOULD rather than a MUST.

The prerequisite for a user to copy the versioned fixed context (assume #103 is there) to their own environment arises in two scenarios:

• The user requires a low-latency, high-dependency connection to the context, in case the context host server is unreachable.
• The user needs to modify the context for their specific use case.

For users who do not fall into either of these categories, labeling it as a MUST is too strong. Therefore, copying the context to a local environment should be based on the user’s specific needs and carried out at their own risk.

[pietercolpaert]

I’m still in favour of MUST. We do not have an environment, at this time at least, that can keep the context highly available.

@sandervd In case SEMIC would say it does have a CDN environment for these kind of use cases, we could reconsider. Do you know about something like that?