IACS metadata

[toenshoff-c]

We are currently experiencing problems with the validity of our IACS metadata and the test classes of the ETF Validator (and in some cases with our national validator tool).

The tests for INSPIRE data sets and data set series metadata for IACS are carried out by the GDI-DE test suite in the INSPIRE reference validator (https://inspire.ec.europa.eu/validator/home/index.html) used by it.

An initial assumption that this could be due to the schema location or the resolution of gmx:Anchor was not confirmed.
A comparison of the results obtained from our national GDI-DE test suite with those from a direct execution of the tests in the INSPIRE reference validator gave a more differentiated picture.

1,For the resource ‘Landscape elements’ https://registry.gdi-de.org/id/de.sl/fab55608-b1af-4672-bbd6-4ddd44853ed2, both the test for the keyword INSPIRE data theme and the test for the keyword IACS CodeList value lead to errors in the INSPIRE validator
1_Land with test suite Conformance Clas... and data set series metadata for IACS.pdf

2, For the resource ‘LPIS’ https://registry.gdi-de.org/id/de.sl/bf241f8c-f4e0-41e3-a6de-bc469994f78a, the test executed directly in the INSPIRE validator for the keyword IACS CodeList leads to errors.
2_LPIS with test suite Conformance Clas... and data set series metadata for IACS.pdf

Do you have any ideas as to what could be causing the errors?

Thank you very much

[hogredan]

Dear @toenshoff-c , dear @fabiovinci ,

fyi: the descrepancies found in the test results between the national validator (GDI-DE Testsuite) and the INSPIRE Reference Validator are due to a bug in the national validator. This will be fixed with the next release of the national validator.

[m2fuhrmann]

Dear Helpdesk Team,

we can confirm the error “Keyword IACS CodeList value” that Saarland reported yesterday for Brandenburg.

We followed the IACS-Keyword example in GitHub:
(https://github.com/inspire-eu-validation/metadata/blob/2.0/iacs/IACS-datasets.md#iacstemporalreference):

• Keywords: LPIS and IACS
• thesaurusName: IACS Data
• Publication date: 2021-06-08
  With the appropriate anchor links.

<gmd:descriptiveKeywords>
	<gmd:MD_Keywords>
		<gmd:keyword>
			<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/IACSData/iacs">IACS</gmx:Anchor>
		</gmd:keyword>
		<gmd:keyword>
			<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/IACSData/lpis">LPIS</gmx:Anchor>
		</gmd:keyword>
		<gmd:thesaurusName>
			<gmd:CI_Citation>
				<gmd:title>
					<gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/IACSData">IACS Data</gmx:Anchor>
				</gmd:title>
				<gmd:date>
					<gmd:CI_Date>
						<gmd:date>
							<gco:Date>2021-06-08</gco:Date>
						</gmd:date>
						<gmd:dateType>
							<gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>
						</gmd:dateType>
					</gmd:CI_Date>
				</gmd:date>
			</gmd:CI_Citation>
		</gmd:thesaurusName>
	</gmd:MD_Keywords>
</gmd:descriptiveKeywords>

But the INSPIRE Reference Validator still gives an error.
When specifying the IACS keywords in our metadata, we cannot see any difference from the IACS keyword example in GitHub.

• the XML-File
  2024-12-10_7faa23ac-a153-46e9-b4d1-893284d0a82b.zip

• the Test Report (ideally as an attachment to the issue)
  Test run on 14_00 - 10.12.2024 with test suite Conformance Class 8_ INSPIRE data sets and data set series linked service metadata.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 :
  https://yzyiqfakm4.execute-api.eu-west-1.amazonaws.com/validator/v2/TestRuns/EID5cc12aae-00f0-4fa1-adbd-4b0a208fbc18.html?lang=de#EIDc933f4da-cab0-405a-a788-e5f2bd38d582

If you could find out where the error is located with Saarland and us, that would help us a lot.

Thanks & regards.

[fabiovinci]

Dear all,

the IACS keywords appear to be encoded correctly; we will check why the related test fails.