search

opengeospatial / ets-wms13

Repository for the Exectutable Test Suite for WMS 1.3.0
Apache License 2.0
2 stars 4 forks source link

OGC WMS 1.3.0 test gives "validate-using-schemaLocation" failure in the test result for an INSPIRE View Service WMS #110

Open robblis opened 3 months ago

robblis commented 3 months ago

Describe the bug While testing a valid INSPIRE View Service WMS failures are encountered.

To Reproduce Steps to reproduce the behavior:

  1. Goto https://cite.opengeospatial.org/teamengine/viewSessions.jsp
  2. Create a new OGC_Web Map Service (WMS)_1.3.0 test session.
  3. Use the following service endpoint. https://agsinspire2.esri.com/server/services/A4I/EnergyResources/MapServer/WMSServer?request=GetCapabilities&service=WMS
  4. See errors: validate-using-schemaLocation FAILED.

Expected behavior See validate-using-schemaLocation pass

Screenshots image

Additional context This seems to occur when adding the following namespace and schema location for INSPIRE view service to the getCapabilitiies. xmlns:inspire_vs="http://inspire.ec.europa.eu/schemas/inspire_vs/1.0" http://inspire.ec.europa.eu/schemas/inspire_vs/1.0 http://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd

dstenger commented 3 months ago

Thank you for reporting. We can reproduce your problem and will do further investigation.

I propose to discuss the second screenshot (second-style-invalid) in #112 as the error message is the same as reported in #112. Can you please move the screenshot from this issue into the other one (e.g. by editing the description)?

robblis commented 3 months ago

Hi @dstenger, I moved the second issue into #112 . Thanks for looking at this.

bpross-52n commented 1 month ago

@robblis, your observation is correct, the issue is the schema location URL http://inspire.ec.europa.eu/schemas/inspire_vs/1.0 (http://inspire.ec.europa.eu/schemas/inspire_vs/1.0 http://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd) The INSPIRE schemas have been moved to https, accessing the schemas using http leads to a redirect. The Java Validator does not follow these by default. Would it be possible for you to change the schema location to https?

robblis commented 1 month ago

Hi @bpross-52n, yes, I believe we should be able to use the https schema location. We will make the changes and run through the validator again.

Update...

After updating the schema to "https" for the URLs in question in the GetCapabilities XML, the WMS service passed the "validate-using-schemaLocation" test.