Frequently Asked Questions

Categories:

The Testing Process
Web Map Server
GML 2.1.2 Validation



The Testing Process


1. How do I get "certified" or to become "compliant"?

In general, your product will need to pass all of the mandatory tests for a particular service implementation specification (and version) for that product to become compliant. To make claims of compliance in the marketplace, you must complete the compliance certification process outlined in the OGC Compliance Testing Program Document. Furthermore, you should be aware that OGC has a well-documented Trademark & Servicemark License & Usage policy describing the proper use of OGC trademarks and servicemarks and on using OGC logos, icons, and certification mark.

For detailed information concerning compliance testing process, please visit the OGC® Compliance Testing page.

top


2. Why are there two different Test Engines?

The CITE Test Engine was initially developed to test WFS 1.0 and WMS 1.1.1. Later on, it was extended to incorporate WCS 1.0 testing and GML 2.1.2 validation. Greater extensibility was required to extend the test suites to include CSW and WFS 1.1 and WMS 1.3 testing so a new, open source engine, the TEAM Engine was created. Although the WFS 1.0 and WMS 1.1.1 were migrated to the new TEAM Engine during the OWS-4 CITE effort, WCS 1.0 hasn't yet been migrated to the new engine. The original CITE Test Engine is maintained for legacy certification of WCS 1.0. All other compliance testing should take place on the newer TEAM Engine.


3. Where are the Compliance Testing Engines?

As described above, there are currently two test engines. The legacy CITE Test Engine tests WCS 1.0.0 compliance while the TEAM Engine tests everything else.

top


4. Where are the instructions on using the test engines?

For TEAM Engine instructions, refer the the specification links here.
Legacy CITE Test Engine instructions are here.

top


5. Is my use of the testing resources monitored?

No. OGC does not track or monitor testing or attempt to discover the company an account is associated with. Furthermore, it is not assumed that testing is officially associated with a particular company's software until the certification process is initiated.

top




Web Map Server


1. What is a Web Map Service?

A Web Map Service is an application that implements the OpenGIS Web Map Service Implementation Specification. The latest testable revision of this specification may be found here. Please visit this page to find the latest version of OGC implementation specifications.

top


2. How many WMS tests are there?

For WMS 1.1.1 there are a total of 108 WMS tests. However, when you create a test session it will always contain fewer tests, no matter what options are selected. This is because some of the options are mutually exclusive. For example, you can't select both the STRICT and LOOSE Bounding Box Constraint tests. Also, some tests may not be included because they are designed to test capabilities that the WMS doesn't claim to support. For example, if the WMS doesn't advertise support the image/gif format in its capabilities document, test wms/wmsops/getmap/params/format/2 will not be included. See the Scope section in the Assertions document to see under what conditions each test applies.

top


3. How can I tell if the test dataset is loaded on a WMS server?

Create a test session, selecting either the Basic or Queryable profile. Execute the profiles/basic/1 or profiles/queryable/1 test. If the test passes, the WMS is at least advertising the standard dataset layers correctly.

top


4. What WMS capabilities DTD does the test suite use?

For WMS 1.1.1 test wms/wmsops/getcapabilities/response/2 in the test suite uses a copy of the DTD which is listed in Annex A.1 of the WMS 1.1.1 spec to verify that the capabilities document references a valid DTD. A copy of this DTD can be found online at http://schemas.opengis.net/wms/1.1.1/WMS_MS_Capabilities.dtd. Note that currently, this differs slightly from the online version mentioned in Annex A (http://www.digitalearth.gov/wmt/xml/capabilities_1_1_1.dtd), so capabilites documents which reference that DTD will fail.

WMS 1.3.0 uses an XSD located here: http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd.

top


5. Why is the profies/basic/1 or profiles/queryable/1 test failing?

These tests will fail if the cite dataset is not set up correctly. Make sure that all of the cite dataset layers are included in the capabilities document and that the <Title> element in each layer contains correct identifier (i.e. cite:BasicPolygons). Note that this identifier appears in the <Title> element instead of the <Name> element. This allows testing with WMS software which may be not be capable of including a namespace prefix in the Name.

top




GML 2.1.2 Validation


What does the GML schema validator check?
  • Validity against XML Schema 1.0
  • A GML feature definition must be derived fromgml:AbstractFeatureType or from a complex type that derivesfrom gml:AbstractFeatureType.
  • A GML feature definition must not have a direct childelement that derives from gml:AbstractGeometryType.
  • A GML feature definition must not have a direct childelement that derives from gml:AbstractFeatureType.

top


What does the schema validator use for validation?
  • The Xerces schema parser and schema object model is usedfor the base validation.
  • Custom code developed for the CITE project and the Galdos Schema Parser is used to validate the GML rules.

top


Why do I get a lot of 'Non-whitespace characters are notallowed in schema elements other than xs:appinfo andxs:documentation.' error messages?

If the error report contains a lot of these messages it isnormally caused by using the draft version of the XML Schemaspecification as opposed to version 1.0. Prior to GML 2.1 the GMLspecifications used this draft version. The validator is only ableto test schemas that conform to GML 2.1.2 and XML Schema 1.0.

top


Why do I get the error 'There was an unexpected errorprocessing the schema, please check the schema using a tool suchas XML spy to check that it is schema valid.'

The underlying XML Schema validator (Xerces) does notgenerate detailed error messages if the document contain the XMLschema element as the root element of in the case of validationerrors against the XML Schema. In this case use a tool such as XMLSpy to validate that you schema conforms the the XML Schemaspecification before revalidating. Common causes include.

  • The XML document for the schema does not start with theschema element in the'http://www.w3.org/2001/XMLSchema' namespace.
  • The schemaLocations for the import and includestatements are not defined or the URL cannot be resolved.Ensure all schemaLocations are set with absolute URLs.

top


What does the GML instance validator check?
  • Conformance to the XML Schema 1.0
  • Validity against the GML 2.1.2 schemas.
  • Validity against the application schemas defined in thedocument.

top


What software does the schema validator use for validation.?
  • The Xerces document parser is used for the base validation.
  • Custom code for the CITE project wraps the Xerces parserto control the validation and error reporting.

top


Why do I get the error "Cannot find the declaration of element 'XXXXXX'"?

The validator performs XML structure and schema validation,you must provide an xsi:schemaLocation for each independent schemaused by the document.

top