Problem with community extended element (gmd:MD_DataIdentification_Type)

[enricoboldrini]

Error returned: Every metadata record must have a title, but this record does not have a 'title' property.

I'm validating a SeaDataNet XML document, that is a community profile of ISO 19115 metadata (https://www.seadatanet.org/Standards/Metadata-formats/CDI), drafted according to official ISO 19115 rules.
Most likely, the test expects gmd:MD_DataIdentification instead of the element sdn:SDN_DataIdentification (gco:isoType="MD_DataIdentification_Type") that is a community defined element extending the ISO one.

Test Report: http://inspire.ec.europa.eu/validator/v2/TestRuns/EID78510388-5466-4487-adce-6e460b23fe57.html
Assertion URI: http://inspire.ec.europa.eu/validator/v2/TestRuns/EID78510388-5466-4487-adce-6e460b23fe57.html?lang=en#EID7a6ce9c1-e1f7-4945-a26a-c8f070dd9d83
Referenced file: https://www.seadatanet.org/content/download/4534/file/CDI_ISO19139_full_example_12.2.0.xml

[danielnavarrogeo]

The same comment applies here https://github.com/inspire-eu-validation/community/issues/297#issuecomment-621897483

[iuriemaxim]

INSPIRE TGs are imposing different requirements than ISO.

But here, in both, ISO and INSPIRE the Title is mandatory. And there was a reason to have this element mandatory.

The INSPIRE validator should not be transformed into a tool that validates the Metadata against ISO. Tests should not be relaxed to such a degree that INSPIRE Requirements not to be fulfilled.

Sometimes INSPIRE is more demanding, somtimes ISO is more demanding. The image below is from Metadata TG 1.3:

I noticed a lot of such requirements posted by @enricoboldrini and I am afraid that already the INSPIRE validator is not taking into account the TGs.

If there are aspects that should be modified, then the first step is to be modified in the TGs. Validator should follow the TGs and not the ISO, I am suggesting to mark all these as discussion and to analyse all the issues that were already closed in order to see if the TGs Requirements are implemented in the validator or the tests were relaxed with no reasoin:

Can be marked as discussion:
#296
#297
#298

To be verified if they are against the TGs:
#134
#45
https://github.com/inspire-eu-validation/ets-repository/issues/183
inspire-eu-validation/ets-repository#184
inspire-eu-validation/ets-repository#185