WMS Validation : at04 (xml schema not valid) and at47 (check-legend-by-layer)

[Dnoack49]

Dear INSPIRE-Team,

I validated the following WMS:
https://inspire.brandenburg.de/services/br_natraum_wms?request=GetCapabilities&service=WMS

and received the Error:
at04-getcapabilities-xml-schema-validation / check-xml-schema-valid

Schema not valid: [org.xml.sax.SAXException: Fatal error: org.xml.sax.SAXParseException; lineNumber: 141; columnNumber: 302; cvc-complex-type.2.4.a: Invalid content was found starting with element '{"https://schemas.deegree.org/extensions/services/wms/1.3.0":ExtendedCapabilities}'. One of '{"http://www.opengis.net/wms":_ExtendedCapabilities, "http://www.opengis.net/wms":Layer}' is expected. Response did not validate against schema 'http://www.opengis.net/wms https://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd http://www.opengis.net/sld https://schemas.opengis.net/sld/1.1.0/sld_capabilities.xsd'.]

Test run on 15_29 - 11.07.2025 with test suite Conformance Class View Service WMS.zip

Another Error appears for at47-getcapabilities-layer-style-legend-url / check-legend-by-layer-and-language however there is no description about the error itself. In the WMS a legend is provided in each LegendURL-Element.

In the past these tests did not appear and everything passed. Why do they fail now? Maybe with the first error the reason is a schema update perhaps?

[damienmulder]

We are running into similar issues when validating the following WMS against 'Conformance Class View Service WMS':
https://service.pdok.nl/provincies/aardkundige-waarden/wms/v1_0?request=GetCapabilities&service=WMS&VERSION=1.3.0

Errors are appearing without description for:

• at47-getcapabilities-layer-style-legend-url / check-legend-by-layer-and-language and
• at68-language-parameter / check-default-language

In both cases the validation seems to end with the following exception (as seen in the corresponding Attachment Messages) :

groovy.lang.MissingMethodException: No signature of method: com.eviware.soapui.support.types.StringToStringsMap.getCaseInsensitive() is applicable for argument types: (java.lang.String) values: [Content-Type]
Possible solutions: getCaseInsensitive(java.lang.String, java.lang.String)

[fabiovinci]

Dear @Dnoack49,

I confirm the error identified by the validator for schema validation. Upon opening the capability document with an XML editor, the same error appears, as the schema declared at "https://schemas.deegree.org/core/3.5/extensions/services/wms/soapwms.xsd" is not accessible.

Please verify the accessibility of the URL with the relevant provider.

[fabiovinci]

Dear all,

For the other errors for at47 and at68, we will conduct further investigation.

[Dnoack49]

Dear @fabiovinci, Thank you for clarification.

[hallinpihlatie]

I have compared validating a view service with the INSPIRE validator in use before and after the July version update.
The test results confirm that at47 is a new error, which seems to have been introduced by the version update. . See attached zip file.

Test results before and after July update_View Service - WMS.zip

The URL of the view service tested: https://inspire-wms.maanmittauslaitos.fi/inspire-wms/GN/ows?service=WMS&request=GetCapabilities

[Dnoack49]

Dear @fabiovinci are there any Updates on the 2 erros regarding at47-getcapabilities-layer-style-legend-url and at68-language-parameter ? I think it might be an error in the validator.

[fabiovinci]

Dear @Dnoack49,

we reviewed the issue and verified that errors in the at-47 and at-68 tests were introduced with the changes made for issue 558 (see #558 (comment)).

Incorporating the getCaseInsensitive function for 'Content-Type' values should not have introduced any errors.

We will review the issue and resolve it.