Why default Dataset resources to `dcat:landingPage` instead of `foaf:page`? about geodcat-ap

[jakubklimek]

@streino We were hoping to get some more community feedback on this. Since the release of GeoDCAT-AP is imminent, we have pushed this into the next cycle. PR here is not necessary, as the change is relatively trivial.

[streino]

Adding some more concrete context.

Some of our INSPIRE catalogs have gmd:distributionInfo linking to studies or other types of publications that used the Dataset as a source of data. For instance a Dataset record with "Related works" (ISO XML).

Having no relevant CI_OnlineFunctionCode, those resources can't declare a gmd:function and therefore end up as dcat:landingPage -- despite the fact those resources are not "about" the Dataset. While not ideal (dct:isReferencedBy would be more appropriate), the more generic definition of foaf:page seems better than dcat:landingPage in those cases.

[fxprunayre]

The approach planned in GeoNetwork (geonetwork/core-geonetwork#7600) for this is:

• in ISO19115-3, metadatalinkage is used as the dcat:landingPage (https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-distribution.xsl#L81-L97). Also for records with a DOI (eg. https://sextant.ifremer.fr/Donnees/Catalogue#/metadata/cf5048f6-5bbf-4e44-ba74-e6f429af51ea) maybe the DOI is a good candidate for the landing page.
• graphic overview is a foaf:page https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-distribution.xsl#L101-L109
• online resources are mapped to foaf:page or dcat:distribution based on function or protocol values. https://github.com/SPW-DIG/metawal-core-geonetwork/blob/dcat/schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/dcat/dcat-core-distribution.xsl#L142

[jakubklimek]

@streino Is your proposal to switch the mapping from

1. "undefined" => dcat:landingPage
2. Information => foaf:page

to the other way around, i.e.

1. "undefined" => foaf:page
2. Information => dcat:landingPage

?

[streino]

Thanks for looking into this!

Yes that's basically our suggestion, with "undefined" => foaf:page being the most important.

Information => dcat:landingPage is more of a stretch, as the definition of Information is broader than dcat:landingPage. Ideally we'd want another CI_OnlineFunctionCode dedicated to landingPage, but I'm not sure how feasible that is. Short of that, Information might be a good approximation?

[streino]

@jakubklimek what's the process to accept/reject this change? We'll be happy to help with a PR, but we don't want to get ahead of the process.