Incorrect href for dcat:endpointDescription and other statements

[dennisvang]

FDP metadata contains the following:

  dcat:endpointDescription <http://localhost:8080/v3/api-docs>, <http://localhost:8080/swagger-ui.html> .

However, the resulting HTML anchors' href values are relative to the client origin, and the path for the /swagger-ui.html is replaced by /:

<div class="metadata-value">
  <ul>
    <li><a href="/v3/api-docs" class="text-link">api-docs</a></li>
    <li><a aria-current="page" href="/" class="router-link-active router-link-exact-active text-link">swagger-ui.html</a></li>
  </ul>
</div>

[dennisvang]

This is actually a more general problem, not restricted to dcat:endpointDescription.
For example, for "Endpoint URL" we have:

<a aria-current="page" href="/" class="router-link-active router-link-exact-active text-link">http://localhost:8080</a>

Here the href is also relative to the client origin, which is http://localhost:5173 in this case.

On the other hand, for access rights, it is handled correctly, with an absolute uri:

<a href="http://localhost:8080#accessRights" target="_blank" rel="noopener noreferrer" class="text-link">localhost:8080#accessRights</a>

There is also a bit of inconsistency between the text content localhost:8080#accessRights (without the http scheme part) and e.g. http://localhost:8080 (with the http) for the endpoint url.