Update context.js and constants.js

[JSAssassin]

No description provided.

[dmitrizagidulin]

👍
Thanks @JSAssassin!

[davidlehn]

Re syncing js and json issues: I think the theory of this newer template style is that developers should just edit the js and use the serialize script to generate and commit the JSON. @dmitrizagidulin should confirm. I assume the generated JSON is supposed to be in git? The build script is going to run serialize anyway so I think the main purpose for the JSON in the repo is for local testing?

[dmitrizagidulin]

@davidlehn - good question. Yes, the generated JSON is supposed to be committed to Git. The reason for that is -- for many of the contexts this template serves, the w3id URL resolves to that very same generated JSON file, hosted via Github Pages.
Meaning, the main purpose for the JSON is not for local testing, but for serving the context on the web.

[davidlehn]

@dmitrizagidulin Ah yes, I forgot that use case. Would be good to figure out how to write a github action that checks to make sure js and json are in sync. As was seen here, that can be an issue and is difficult to spot.

[davidlehn]

Added tracking issue: digitalbazaar/context-template#6