improve URL rendering on MESH pages

[VladimirAlexiev]

A MESH page eg https://id.nlm.nih.gov/mesh/D008071.html uses ugly URLs, eg

• https://id.nlm.nih.gov/mesh/describe?uri=http%3A%2F%2Fid.nlm.nih.gov%2Fmesh%2FQ000138
• https://id.nlm.nih.gov/mesh/describe?uri=http%3A%2F%2Fid.nlm.nih.gov%2Fmesh%2FT042501

Given that all these URLs resolve, please present them in their canonic form:

• https://id.nlm.nih.gov/mesh/Q000138
• https://id.nlm.nih.gov/mesh/T042501

Otherwise it becomes unnecessarily complex to share MESH semantic URLs.

There are also links over ontology terms, eg

• https://id.nlm.nih.gov/mesh/describe?uri=http%3A%2F%2Fid.nlm.nih.gov%2Fmesh%2Fvocab%23TopicalDescriptor

Because these use hash, presenting them in their canonic form

• https://id.nlm.nih.gov/mesh/vocab#TopicalDescriptor

will be a problem because the browser will send only https://id.nlm.nih.gov/mesh/vocab, resulting in the whole ontology being returned.

Perhaps you can use the canonic form in the link name, but the describe form in the link, eg

<a href="https://id.nlm.nih.gov/mesh/describe?uri=http%3A%2F%2Fid.nlm.nih.gov%2Fmesh%2Fvocab%23TopicalDescriptor">
https://id.nlm.nih.gov/mesh/vocab#TopicalDescriptor
</a>

[danizen]

@VladimirAlexiev, in principal, a "lodestar" should be able to host IRIs that may not be permanently resolvable or which may not be hosted on that particular server. Using canonical forms can lead to odd results occasionally, for instance, try this query:

SELECT DISTINCT ?g
WHERE {
  GRAPH ?g { ?s ?p ?o }
} 

On the other hand, I caused this issue so that development on http://localhost:8080/ would refer to the development system rather than to the production installation. That is a basic requirement for my automated testing of the system, but I think it could be done in a different way where a REST URI beginning with https://id.nlm.nih.gov/ is rewritten to a baseURI.

[VladimirAlexiev]

Perhaps you can patch lodestar to do this better thing for MESH URLs?