When users click on any of the "edit" links on a translation summary page returned by the Web2Cit server, they are sent to a Web2Cit-JSON-Editor URL including the templates, patterns or tests JSON schema as parameter.

Because these files could not be served directly from the Web2Cit-Core's gitlab repository (T305700), they are served from the GitHub mirror instead.

Recently, an alpha version of Web2Cit-Server was deployed to the test instance at w2c-beta.toolforge.org for public testing, which uses an alpha version of Web2Cit-Core, which supports JSON-LD selection. JSON schema files were updated on the corresponding development branch.

However, because the "edit" links returned by the alpha version of the server still use the JSON schemas from the Web2Cit-Core's branch, the Web2Cit-JSON-Editor form does not include JSON-LD selection.

A solution may involve changing the Web2Cit-Core's branch from which JSON schemas must be pulled in the alpha version of the server. But I don't like this as one may forget changing it back later on.

Alternatively, consider serving these JSON schema files from the server itself. I think this would make sense, considering that it is the server (and only the server so far) which refer to these JSON schemas when creating the corresponding Web2Cit-JSON-Editor URLs.

In addition, it would make better sense to provide translations for these JSON schema files here on the server source code, instead of on the core source code (see T317044).

This doesn't mean we will remove these schemas from the Web2Cit-Core repository. We will continue maintaining them there. We will just serve them from the server.

Also, by doing this, we will no longer have to rely on GitHub to serve these files.

The only disadvantage I can think of right now is that we will need to release new core and server versions each time a schema has to be updated.