Static local contexts need to be kept in sync.

[davidlehn]

The static contexts in this library need to be kept in sync with upstream contexts. How should this be accomplished?

Contexts:

• https://www.w3.org/2018/credentials/v1 => https://github.com/digitalbazaar/credentials-context
• https://www.w3.org/2018/credentials/examples/v1 => https://github.com/digitalbazaar/vc-js/blob/main/lib/contexts/vc-examples-v1.js
• https://www.w3.org/ns/odrl.jsonld => https://github.com/digitalbazaar/vc-js/blob/main/lib/contexts/odrl.js

One approach would be to run a github action check, probably on PRs and periodically (weekly?). In a recent PR I used diff, curl, and jq to compare what this module serves and the live dereferenced resources:
#111

I don't know what would happen if this reported diffs that were not desired in this package. It would be good to at least know.

[davidlehn]

Two other options to at least help with comparisons. Instead of inline data in JS, inline the JSON direct:

module.exports =
/* BEGIN CONTEXT */
{
  "@context": ...
  "foo": ...
}
/* END CONTEXT */
;

Or put the contexts in webpack/node loader friendly .json files and require() them. I think that would work with the current structure?