Role of service metadata in the EDP, in HVD-reporting and in this pilot?

[hallinpihlatie]

The provision of service metadata is compulsory according to the metadata profile which is being recommended to use for HVD reporting DCAT-AP High Value Datasets (overview.jpg (1852×804)). However, you are only be able to search for HVD and other datasets in the European Data Portal, not services.

Is there development going on to support search for service metadata in EDP? Does service metadata have a clear role i HVD reporting and in the future or is more a matter of preserving what they contain in case they exist? If the latter, perhaps we can focus on the dataset metadata in the first place priority and time table wise.

[H-a-g-L]

There is a filter (TRUE/FALSE) for limiting search results to datasets that have data services:
https://data.europa.eu/data/datasets?is_hvd=true&locale=en&page=1&dataServices=true

Note that data services can be linked to datasets either from the :DataService via the dcat:servesDataset property or from the :Dataset via the dcat:accessService of the dataset's :Distribution . The data.europa.eu documentation provides a query that returns both use cases.

[hallinpihlatie]

Thanks. I realised that there is that kind of filter at some point.
Thanks for the notes and the link to the documentation.

[akuegeler]

Some additional notes from me (con terra is the contractor in charge of the "geoharvester" for data.europe.eu):

If you have ISO service metadata (hierarchyLevel service) and you tag it as HVD according to the anchor solution [1], it will be considered an HVD in the European Data Portal.
Example: Original [2], European Data Portal [3]

On the role of service (geo)metadata in HVD reporting:
In my opinion the focus should be on the dataset metadata (because of the INSPIRE good practice Data-Service Linking Simplification [4] and because geoservices often seem to include a variety of layers that don’t match well to GeoDCAT-AP’s dataset distribution). I also agree with your notion of preserving what service metadata contain in case they exist.
Please note that this is not the EC’s official view – this would need to be clarified with DG Connect.

[1] https://dataeuropa.gitlab.io/data-provider-manual/hvd/annotation_in_geometadata/
[2] https://www.paikkatietohakemisto.fi/geonetwork/srv/api/records/174c57fd-deaa-4af4-aa9d-eafdd469382e/formatters/xml
[3] https://data.europa.eu/data/datasets/174c57fd-deaa-4af4-aa9d-eafdd469382e?locale=en
[4] https://github.com/INSPIRE-MIF/gp-data-service-linking-simplification/blob/main/good-practice/good-practice-fiche.md

[jescriu]

This issue was discussed in the Fourth Pilot meeting on 28 April, explaining further the views expressed above.

As a result, the INSPIRE community needs to clarify and discuss the role of service metadata.

A remark for further reflection - In the DCAT-AP High Value Datasets metadata profile there is a clear encouragement to mark the service metadata.
The INSPIRE community should discuss how to do this, as illustration either following the approach of the mentioned profile, or through another approach to be appended in the future to the current Data-Service Linking Simplification Approach (as part of this good practice) - e.g. only preserving the service metadata if they provide additional useful information on HVDs.

In summary

• Further guidance and discussion is needed on how to represent HVD services in INSPIRE metadata.
• Importance of encoding them as sevices.