GML 3.2 (ISO 19136:2007) Conformance Test Suite

Scope

This executable test suite (ETS) verifies the conformance of GML data and application schemas with respect to ISO 19136:2007 (GML 3.2.1). As shown in Figure 1, a conforming GML data instance must refer to the relevant GML application schema, which in turn imports the complete GML schema.

A Schematron schema (ISO 19757-3) may be used to define supplementary data constraints that lay beyond the reach of an XML Schema grammar. A GML instance document may include a schema reference using the xml-model processing instruction (PI) as described in the W3C group note Associating Schemas with XML documents 1.0 (Third Edition). The PI must appear before the document element as shown in the following listing.

<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://example.org/data-constraints.sch" 
            schematypens="http://purl.oclc.org/dsdl/schematron" 
            phase="#ALL"?>
<CityModel xmlns="http://www.opengis.net/citygml/2.0">
  <!-- content omitted --> 
</CityModel>

Several conformance classes are defined in the principal specification:

All GML application schemas: Clause A.1.1
GML application schemas defining Features and Feature Collections: Clause A.1.4
GML application schemas defining Spatial Geometries: Clause A.1.5
GML application schemas defining Spatial Topologies: Clause A.1.6
GML application schemas defining Time: Clause A.1.7
GML application schemas defining Coordinate Reference Systems: Clause A.1.8
GML application schemas defining Coverages: Clause A.1.9
GML application schemas defining Observations: Clause A.1.10
GML application schemas defining Dictionaries and Definitions: Clause A.1.11
GML application schemas defining Values: Clause A.1.12

Test requirements

The documents listed below stipulate requirements that must be satisfied by a conforming application schema.

[ISO-19136] Geographic information -- Geography Markup Language (GML)
[XMLSchema] XML Schema Part 1: Structures, Second Edition

See the Javadoc documentation for more detailed information about the test classes and test methods that comprise the suite.

How to run the tests

The test suite may be run in any of the following environments:

Integrated development environment (IDE): The main Java class is TestNGController.
REST API: Submit a request that includes the necessary arguments to the test run controller
TEAM-Engine: Run the CTL script located in the /src/main/ctl/ directory.

The test run arguments are summarized in Table 1. The Obligation descriptor can have the following values: M (mandatory), O (optional), or C (conditional). A GML application schema may be validated without supplying any data. If both arguments are present, the 'xsd' value is ignored and the (required) schema reference in the GML instance is used instead.

Table 1 - Test run arguments
Name	Value domain	Obligation	Description
xsd	URI	C (must be present if the 'gml' argument is not supplied)	A URI referring to a GML application schema ¹.
gml	URI	C (must be present if the 'xsd' argument is not supplied)	A URI referring to a representation of a GML data instance ¹.
sch	URI	O	A URI referring to a Schematron schema that defines supplementary data constraints ².
Notes Ampersand ('&') characters appearing within query parameter values must be percent-encoded as %26. ISO 19757-3:2006

Release notes

3.2.1-r7 (2013-07-24)

This is a maintenance release; it includes the following fixes:

CITE-840 (findGeometryComponents misses geometry properties).

3.2.1-r6 (2013-07-19)

This is a maintenance release; it includes the following fixes:

CITE-845 (Anonymous feature type definition not detected).

3.2.1-r5 (2013-07-15)

This is a maintenance release; it includes the following changes:

CITE-826: Disable tests for lexical conventions
CITE-825: Some schemas referenced in @xsi:schemaLocation are ignored
Use XLink 1.1 schema (internal catalog resolver)
Updated dependencies: schema-utils-1.2

3.2.1-r4 (2013-07-04)

This maintenance release includes the following changes:

Updated dependencies: teamengine-spi-4.0, jersey-client-1.17.1
Don't clear reporter output in SuiteFixtureListener#onFinish()