The INSPIRE Profile of ISO 19128 conformance class is defined in the Technical Guidance for the implementation of INSPIRE View Services and it is part of the Abstract Test Suite for the INSPIRE View Services Technical Guidance.
OGC web service (WMS 1.3.0)
A direct dependency is another conformance class whose requirements must be met by the view service, too.
Specification | Conformance class | Parameters |
---|---|---|
ISO 19128 / OGC WMS 1.3.0 | Basic WMS | n/a |
Based on requirement numbering in TG VS.
The TG VS gives three options (scenarios) for providing the service metadata in the Capabilities document of the WMS services:
-
Scenario 1: The View Service metadata elements are managed in an INSPIRE Discovery catalogue. The INSPIRE network service metadata record in a Discovery Service is referenced in the extended INSPIRE capabilities.
-
Scenario 2: The View Service metadata elements are fully mapped to [ISO 19128] – WMS 1.3.0 elements and elements in the INSPIRE extended capabilities.
-
Scenario 3: The View Service metadata elements are fully mapped to [ISO 19128] – WMS 1.3.0 elements without the use of any extended capabilities.
Since there is no dedicated method in TG VS for the data provider to indicate which scenario has been chosen, the validator software must use the following logic to decide the appropriate set of tests to apply:
- If the <inspire_common:MetadataURL> element is present as first element in the ExtendedCapabilities section, we assume to be in Scenario 1.
- If the <inspire_common:ResourceLocator> element is present as first element in the ExtendedCapabilities section, we assume to be in Scenario 2.
- If the ExtendedCapabilities section is not present, we assume to be in Scenario 3.
Figure 1. Extended Capabilities for INSPIRE View Services. Source: TG VS.
The case of scenario 1, the metadata record referred to by the inspire_common:MetadataUrl
element must also pass the service scenario of the test suite ATS Metadata.
This Conformance Class contains the following tests. The "scenario" column of the test table below indicates if the tests are applied in scenarios 1, 2, 3 or all (see above).
The "type" column indicates whether a test is automated, manual, automated/manual or none. Tests that are manual or automated/manual require extra checks from the tester to decide if the view service satisfy the specific requirement.
The following prefixes are used to refer to the corresponding XML namespaces in all test descriptions:
Prefix | Namespace |
---|---|
wms | http://www.opengis.net/wms |
xlink | http://www.w3.org/1999/xlink |
gmd | http://www.isotc211.org/2005/gmd |
inspire_vs | http://inspire.ec.europa.eu/schemas/inspire_vs/1.0 |
inspire_common | http://inspire.ec.europa.eu/schemas/common/1.0 |