Hi all, I am using the INSPIRE extension with Geoserver 2.20.0, to provide INSPIRE services. I am testing the implementation with the INSPIRE validator (the one provided by JRC along with a local installation).
I would like to know if anyone has noticed problematic behavior, as regards the encoding of other supported languages. Bellow I am describing the problem I noticed: *Correct INSPIRE extended caps schema (TechnicalGuidance_ViewServices_v3.0 <https://inspire.ec.europa.eu/documents/Network_Services/TechnicalGuidance_ViewServices_v3.0.pdf>)* <inspire_vs:ExtendedCapabilities> <inspire_common:MetadataUrl xsi:type="inspire_common:resourceLocatorType"> <inspire_common:URL>http://discoveryService <http://discoveryservice/> ....</inspire_common:URL> < inspire_common:MediaType>application/vnd.ogc.csw….</inspire_common:MediaType> </inspire_common:MetadataUrl> <inspire_common:SupportedLanguages xsi:type="inspire_common:supportedLanguagesType"> <inspire_common:DefaultLanguage> <inspire_common:Language>dut</inspire_common:Language> </inspire_common:DefaultLanguage> <inspire_common:SupportedLanguage> <inspire_common:Language>eng</inspire_common:Language> </inspire_common:SupportedLanguage> </inspire_common:SupportedLanguages> <inspire_common:ResponseLanguage> <inspire_common:Language>dut</inspire_common:Language> </inspire_common:ResponseLanguage> </inspire_vs:ExtendedCapabilities> 1. *same default and supported language in wms INSPIRE extension configuration * When the default and other supported language is the same, the capabilities document omits the element /../inspire_vs:ExtendedCapabilities/inspire_common:SupportedLanguages/inspire_common:SupportedLanguage. Since the element is not mandatory, the INSPIRE validation is successful (at least as regards the schema validation). [image: image] <https://user-images.githubusercontent.com/55238073/139808925-127efcac-199d-4879-ba60-88031f4a91b7.png> [image: image] <https://user-images.githubusercontent.com/55238073/139808938-d1875384-7651-4a68-8d1d-2613141c2aa5.png> 1. *no other supported language* When no other supported language is selected, the element /../inspire_vs:ExtendedCapabilities/inspire_common:SupportedLanguages/inspire_common:SupportedLanguage is present in the capabilities document but it is not correctly encoded. [image: image] <https://user-images.githubusercontent.com/55238073/139810364-eb42d028-b6c0-4234-9f5c-98b73b41c713.png> [image: image] <https://user-images.githubusercontent.com/55238073/139809772-485a3996-cdd0-49b9-bd9b-bbefbe353d45.png> The child element /../inspire_vs:ExtendedCapabilities/inspire_common:SupportedLanguages/inspire_common:SupportedLanguage/inspire_common:Language is missing so the schema validation fails. The INSPIRE validator returns the following message: *Schema not valid: [org.xml.sax.SAXException: Fatal error: org.xml.sax.SAXParseException; lineNumber: 110; columnNumber: 48; cvc-complex-type.2.4.b: The content of element 'inspire_common:SupportedLanguage' is not complete. One of '{"http://inspire.ec.europa.eu/schemas/common/1.0 <http://inspire.ec.europa.eu/schemas/common/1.0>":Language}' is expected. Response did not validate against schema 'http://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd' <http://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd'>.]* 1. *different default and other supported languages* The desired configuration in our case is to provide different default and supported languages, using the i18n configuration for the internationalization of the capabilities response. [image: image] <https://user-images.githubusercontent.com/55238073/139810330-0eab0fc1-11fc-44c4-a815-91786bb55fa6.png> When this configuration is present, the capabilities response is again not correctly according to the INSPIRE validator. [image: image] <https://user-images.githubusercontent.com/55238073/139809516-80da5327-c2d7-4236-af6f-4b729b2be3f5.png> The relevant test fails for the schema validation. The error is *Schema not valid: [org.xml.sax.SAXException: Fatal error: org.xml.sax.SAXParseException; lineNumber: 110; columnNumber: 85; cvc-complex-type.2.3: Element 'inspire_common:SupportedLanguage' cannot have character [children], because the type's content type is element-only. Response did not validate against schema 'http://inspire.ec.europa.eu/ <http://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd'>* Note #1 <https://github.com/EOFarm/geoportal.ypen.gr/issues/1>: The i18n configuration does not affect geoserver’s behavior regarding the inspire extended caps. Note #2 <https://github.com/EOFarm/geoportal.ypen.gr/issues/2>: The above testing was made for the following virtual wms http://beta.geoportal.ypen.gr/geoserver/aqd-wms/ows?service=wms&version=1.3.0&request=GetCapabilities Thanx, Elena
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
