hvdsomp
commented
1 year ago Very much agreed that a single, consistent model for links is preferable. And dcterms:relation can be used for that purpose in a manner that aligns with Signposting. For example, here's a statement in an XML metadata record that describes an object that has a PDF file as content resource:
<dcterms:relation rel="item" type="application/pdf">https://strathprints.strath.ac.uk/84907/7/Jiang_etal_IEEETGRS_2023_Microseismic_event_classification.pdf</dcterms:relation>
in the dcterms:relation element, we want to implement content like RFC8288 web links. This approach is like signposting, xlink, html , OGCAPI link model. DCAT takes another approach, recommending using the dcterms subclasses of relation where appropriate and dcat:QualifiedRelation. Having multiple implementation approaches to the same challenge seems like a way to generate confusion. Using the RFC8288 link properties is consisten for all relation types, and aligned with signposting approach, just putting the signpost links in the metadata....