Fix the generated PURL configuration

[gouttegd]

Following this issue by @cmungall, I wonder if the ODK could somehow propose a feature to facilitate the maintenance of the config file needed by purl.obolibrary.org.

The problem in the aforementioned issue is not in CL itself, it’s in its PURL configuration, which redirects the http://purl.obolibrary.org/obo/cl/imports/... and http://purl.obolibrary.org/obo/cl/components/... IRIs to URLs that do not point to where the actual import modules and components can be found.

There is no way the ODK can solve that entirely automatically of course. The purl config is not even in the same repository as the ontology that is managed by the ODK, so it is entirely out of reach for the ODK.

But the ODK does have complete knowledge of what the import modules and components are (it uses that knowledge for example to generate the XML catalog), so maybe it could at least generate a skeleton of a purl config – it would then be up to the user to adjust it as needed and to submit to the purl.obolibrary.org repository.

[gouttegd]

Ah, just realised that the ODK is actually already generating a PURL config file.

Several problems with it though:

• It blatantly assumes the use of GitHub.
• It is never re-generated upon update.
• It does not redirect the IRIs for imports and components to the master branch.