I am quite surprised to discover several WFS services (v1.0.0) running on the web which are not compliant with the OGC WFS-1.0.0 standard. In the framework of my project, I use a JAXB binding built with the XSD schemas from the OGC, and notably the schemas for WFS v1.0.0. As you imagine, not OGC-compliant services are a problem in such a project.

The problem of compliance is for example the XML element:


which is replaced by:


For example in the capabilities: http://www.disasterschartercatalog.org/ogc/cecec4wfs?REQUEST=GetCapabilities&VERSION=1.0.0&SERVICE=WFS

Is anyone know the reasons of this? is it something common?

| improve this question | | | | |

This following one is correct:


as defined by the following portion of the schema definition for version 1.0.0

<xsd:element name="Service" type="wfs:ServiceType"/>

Take a look at 12.3.3 Service section in the Web Feature Service Implementation Specification (OGC 02-058)

| improve this answer | | | | |
  • My mistake, sorry, I thought that WFS-1.0.0 and 1.1.0 use OWS-1.0 but actually it is not the case... my mistake, I will delete my question soon. – njames Jul 28 '12 at 12:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.