More an observation / recommendation for portal owners, rather than an issue (though the XSLT could maybe test / provide a work-around by adding e.g '#id" , or use 'http' for one and 'https' for the other)
If the site/portal owner does not clearly distinct Dataset URI and URLs for e.g. landing pages, the (incorrect) result could be multiple titles on the Dataset.
E.g in this example
<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation>
<gmd:CI_Citation>
<gmd:title>
<gco:CharacterString>Higher trophic levels in the Southern North Sea (TROPHOS)</gco:CharacterString>
</gmd:title>
...
<gmd:identifier>
<gmd:MD_Identifier>
...
<gmd:code>
<gmx:Anchor xlink:href="https://doi.org/10.24417/bmdc.be:dataset:940">https://doi.org/10.24417/bmdc.be:dataset:940</gmx:Anchor>
</gmd:code>
...
<gmd:MD_DigitalTransferOptions>
<gmd:onLine>
<gmd:CI_OnlineResource>
<gmd:linkage>
<gmd:URL>https://doi.org/10.24417/bmdc.be:dataset:940</gmd:URL>
</gmd:linkage>
<gmd:name>
<gco:CharacterString>Digital Object Identifier (DOI)</gco:CharacterString>
</gmd:name>
...
The result will eventually be
<dcat:Dataset rdf:about="https://doi.org/10.24417/bmdc.be:dataset:940">
<dct:title>Higher trophic levels in the Southern North Sea (TROPHOS)</dct:title>
<dct:title>Digital Object Identifier (DOI)</dct:title>
Since https://doi.org/10.24417/bmdc.be:dataset:940 will be used both as ID for the dataset and as URL for a page
More an observation / recommendation for portal owners, rather than an issue (though the XSLT could maybe test / provide a work-around by adding e.g '#id" , or use 'http' for one and 'https' for the other)
If the site/portal owner does not clearly distinct Dataset URI and URLs for e.g. landing pages, the (incorrect) result could be multiple titles on the Dataset.
E.g in this example
The result will eventually be
Since
https://doi.org/10.24417/bmdc.be:dataset:940will be used both as ID for the dataset and as URL for a page