Standard / ISO / Schematron for DCAT HVD requirements

[fxprunayre]

ISO metadata can be retrieved in DCAT and specific rules apply to High Value Dataset context. See https://semiceu.github.io/DCAT-AP/releases/2.2.0-hvd/

This schematron test ISO19139 or ISO19115-3 records and check mandatory elements for datasets and services to facilitate encoding of HVD requirements in ISO records.

The mapping rule defined in the ISO to DCAT mapping are used. Some rules may require adjustments eg.

• no common practice to encode service documentation which is a mandatory element for HVD
• conformsTo reference INSPIRE data specification but how none INSPIRE dataset reference specification?

Relates to #8547

Dataset validation

Service validation

DCAT-AP-HVD output is available at http://localhost:8080/geonetwork/srv/api/records/2414e736-72e2-4b5a-967d-da410ef4526c/formatters/eu-dcat-ap-hvd

A complementary work could be to have a DCAT-AP requirements validation.

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[josegar74]

Why are not defined the translations in schematron-rules-dcat-ap-hvd.xml files that can be added to the loc folder?

[fxprunayre]

Why are not defined the translations in schematron-rules-dcat-ap-hvd.xml files that can be added to the loc folder?

sch:diagnostic (eg. https://github.com/ISO-TC211/XML/blob/master/schemas.isotc211.org/19115/-3/gex/1.0/gex.sch https://github.com/geonetwork/core-geonetwork/blob/main/schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/schematron/schematron-rules-iso.sch#L26) was used in the work done by TC211 for ISO19115-3 which makes the schematron independent to the way GeoNetwork is managing translations (not sure anyone else is using it though). So I can move all translations to dedicated loc files but not sure which approach is better. No strong opinion on this, let me know.

[josegar74]

@fxprunayre if using sch:diagnostic makes the schematron better for use in other systems or for adding to GeoNetwork schematrons created in other systems, it seems a good point to use it.