Codelist value is not resolved correctly

[JohannaOtt]

• a description of the steps to reproduce your issue Validate the dataset attached against LandUse - PlannedLandUse inspire(11).zip It fails with several errors with this pattern "XML document 'inspire(11).gml', SpatialPlan 'BP_Plan_20331831-8903-486D-B6DD-DA584F415398': The property 'PlanTypeNameValue' has a value 'https://registry.gdi-de.org/codelist/de.xleitstelle.inspire_plu/PlanTypeNameValue/7_3_ErgaenzungsSatzung' that cannot be retrieved using HTTP. Every code list value must be made available in an online registry." The code https://registry.gdi-de.org/codelist/de.xleitstelle.inspire_plu/PlanTypeNameValue/7_3_ErgaenzungsSatzung can be accessed using HTTP though. Potentially a re-occurrence of https://github.com/INSPIRE-MIF/helpdesk-validator/issues/559 ?

• the browser and version used Firefox 110.0.1

• a screenshot illustrating the problem

• the Test Report (ideally as an attachment to the issue) Test run on 14 45 - 09.03.2023 with test suite Annex III - Land Use (LU).html.zip

• the name of the Test that failed or better: change the Level of Detail in the Report by clicking on All Details, then scroll down to the failed test and copy the Link on the right-hand side of the Assertion URI Test ID EIDaab1fa13-b19a-44c3-8ca4-1e97b8cf05f5

• the URL of your service / the file you have uploaded or referenced (as an attachment). Is attached to the ticket.

[fabiovinci]

Dear @JohannaOtt,

thank you for the issue, it should not be a problem related to redirecting. We will further investigate.

[fabiovinci]

Dear @JohannaOtt,

I tested your dataset and the issue is no longer present (see report). The error was probably due to the temporary unavailability of the DE registry.

[JohannaOtt]

@fabiovinci I am running in such errors again with the dataset attached (LandCover vector) testExportHessenALKIS712.zip When receving the validation error, I checked and the GDI-DE registry was available. I also repeated the test in order to make sure that there was no temporal issue during the first test run but there are still such messages (different codes this time though). Reports attached reports.zip I am afraid, we need to re-open this ticket and some investigation needs to be done on why the registry cannot be accessed as expected during the test runs.