Currently the INSPIRE plugin puts a schemaLocation which includes "http://inspire.ec.europa.eu/schemas/inspire_vs/1.0 http://localhost:8080/geoserver/www/inspire/inspire_vs.xsd" for the INSPIRE view service namespace. However, this local schema is a very minimal wrapper which imports two other schemas from the Internet:
<import namespace="http://www.opengis.net/wms" schemaLocation="http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd"/><import namespace="http://inspire.ec.europa.eu/schemas/common/1.0" schemaLocation="http://inspire.ec.europa.eu/schemas/common/1.0/common.xsd"/>
<import namespace="
" schemaLocation="
"/><import namespace="
"/>
So there doesn't seem to be any benefit from hosting this small wrapper locally rather than using the canonical location at http://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd .
There is a comment above the getSchemaLocations method in org.geoserver.inspire.wms.WMSExtendedCapabilitiesProvider asking whether the XSD still needs hosting.
See also email thread at http://sourceforge.net/p/geoserver/mailman/message/34125799/
I will submit a pull request.
(I couldn't work out which component this should be filed under as INSPIRE extension wasn't an option.)
Mass closing all resolved issues not modified in the last 4 weeks
Marking as resolved since it's merged already.
Thanks, Marcus. PR 1083 merged. See PR for discussion.
Pull request https://github.com/geoserver/geoserver/pull/1083
Currently the INSPIRE plugin puts a schemaLocation which includes "http://inspire.ec.europa.eu/schemas/inspire_vs/1.0 http://localhost:8080/geoserver/www/inspire/inspire_vs.xsd" for the INSPIRE view service namespace. However, this local schema is a very minimal wrapper which imports two other schemas from the Internet:
<import namespace="
http://www.opengis.net/wms" schemaLocation="
http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd"/><import namespace="
http://inspire.ec.europa.eu/schemas/common/1.0" schemaLocation="
http://inspire.ec.europa.eu/schemas/common/1.0/common.xsd"/>
So there doesn't seem to be any benefit from hosting this small wrapper locally rather than using the canonical location at http://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd .
There is a comment above the getSchemaLocations method in org.geoserver.inspire.wms.WMSExtendedCapabilitiesProvider asking whether the XSD still needs hosting.
See also email thread at http://sourceforge.net/p/geoserver/mailman/message/34125799/
I will submit a pull request.
(I couldn't work out which component this should be filed under as INSPIRE extension wasn't an option.)