WMS tests: GetMetadataURL test failing on PropertyTransferMD_Identifer

[trophies]

I'm short on details for this as the test results don't give a lot of details. I'm seeing this error when running the INSPIRE validator against our service implementations:

"Error performing transfer [addMD_IdentiferToList] - Missing source value for ResponseAsXml"

This is failing under the PropertyTransferMD_Identifer test step. The RunGetMetadataForLayer test step is also shown as failing but it gives no error message.

I've noticed a couple of things though: addMD_IdentiferToList has a typo (should be addMD_IdentifierToList), but I'm not sure that would make any difference to how the test runs.

Looking through the code for this test () I noticed this:

<result>AssertionFailures:
{
let $id:=//gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString
return
if (contains('${#Project#datasetIdentifiersList}', $id))
then ""
else concat("the MD_Identifier ",$id," does not exist in the service metadata. The MD_identifier is found in the metadata document at URL: '${#urlToTestEncoded}'. The service metadata refers to these identifiers: '${#Project#datasetIdentifiersList}'")
}

Which shows that it's grabbing the MD_Identifier elements from the metadata. However, all of the references in the View Service Technical Guidance to writing out the identifiers say to use the RS_Identifier element (See section 4.2.3.3.4.5 UNIQUE RESOURCE IDENTIFIER of the View Service TG), so I think it should be checking for that instead. It's still not entirely clear from the error message I'm getting that this is what's causing the issue, but the test should still be checking for the RS_Identifier as specified in the Technical Guidance.

[thijsbrentjens]

Thanks for reporting. Indeed, it seems that (also)RS_Identifier should be supported. However, this test will probably be removed in a new version.

This test checks if references in metadata to other metadata documents are correct. (Background: in the Netherlands many dataproviders found it difficult to provide (correct) identifiers pointing to the datasets from service metadata and WMS Capabilities. Therefore we created some tests to do checks on the contents of the metadata documents referenced from the Capabilities.)
In the INSPIRE validation workgroup for Abstract Test Suites on metadata and services, this kind of tests will be moved from the View Services tests to a conformance class "Metadata Interoperability", on metadata.

For reference, I think following topics are related:

• https://github.com/inspire-eu-validation/metadata/blob/1.3/iso-19115-19119/ds-identification.md
• https://github.com/inspire-eu-validation/view-service/blob/master/iso-19128/metadataurl-reference-inspire-service-metadata.md
• https://github.com/inspire-eu-validation/view-service/blob/3.11/iso-19128/map-coupled-resource-metadata.md