Problem with Content-Location header for delegated Namespace Forward (proxy mode) about ukl-registry-poc HOT 3 CLOSED

This isn't a problem it's a deliberate feature of the LDA config at environment.data.gov.uk :)

As you say the URLs in the data are fine and any time a URL is rendered in text (e.g. the URL for spittal) it is shown correctly).

What happens is that the link href's are rewritten by some javascript (see http://environment.data.gov.uk/lda-assets/scripts/staging.js) to that they point back to the site from which the page has been viewed. This is done to allow staging deployments of LDA installations. When staging an HTML view of linked data you have this problem that you want to be able to click around the HTML view within the staging site but you want the data to be correct and ready for the target deployment site. The staging.js rewrite is the trick that solves that problem.

In general, independent of this trick, you can't rely on what the browser shows you as the href target in an HTML view of linked data corresponding to the actual data URI. The HTML rendering often has to point back to some intermediate rendering URL.

It would be better if there was also a tooltip popup showing the correct URI to make the correct URI clear.

This, plus your issue 22, reinforce that the function of a DelegatedRegister is enable a part of the registry space to be delegated to some operator who is knowingly serving data within the registry namespace (just from different machines). It is a way of delivering a distributed implementation of a registry namespace, not a way to subvert existing publications at one URI and make them appear as part of the registry. The right way to point to an external resource is by use the ForwardNamespace with a 3XX code.

[The example of forwarding at http://ukgovld-registry.dnsalias.net/def/eabw is a 200 forwarding (to demo that the proxy mode works) but being proxy mode has similar behaviour to delegation.]

from ukl-registry-poc.

Noted and thanks for explaining the issue. With hindsight, the "staging URL-rewrite" behaviour makes sense.

from ukl-registry-poc.

Have noted this behaviour in the FAQ with link to this thread, closing the issue qua issue.

from ukl-registry-poc.