Problem with community defined code list (gmd:hierarchyLevelName)

[enricoboldrini]

Error returned: 'Validation failed: 15:188: cvc-complex-type.2.4.a: Invalid content was found starting with element '{"http://www.seadatanet.org":SDN_HierarchyLevelNameCode}'. One of '{"http://www.isotc211.org/2005/gco":CharacterString}' is expected.'.

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 gco:CharacterString instead of the codelist sdn:SDN_HierarchyLevelNameCode that is a community defined code list.

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#EIDff9a517c-f8ab-4d18-bae7-be8b749649de
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]

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 close all these issues and to analyse all the issues that were already closed in order to see if the TGs Requirements are implemented in the validator:

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