Purpose: Test that the capabilities section of the View Service contains the Service metadata elements in accordance with Table 3a.
Prerequisites
This test only applies to Scenario 2. Otherwise, the test case is skipped.
Test method
-
Send a getCapabilities request to the service endpoint. Into the response:
-
Check that exactly one Title element is provided and it is not empty.
-
Check that exactly one Abstract element is provided and it is not empty.
-
Check that there is exactly one Resource Type element and its value is 'service'.
-
Check that a Resource Locator element is provided and the URL is working.
-
Check that, if there is a MetadataURL element for a layer:
-
the OnlineResource element has an 'xlink:href' attribute, its content is not empty and one of the following checks is passed:
-
a valid response is returned sending an HTTP/GET request to the GetRecorById of the Discovery Service,
-
a direct link is provided to the ISO19139 metadata document.
-
-
otherwise, check manually that "if linkage to data sets on which the service operates are available" the MetadataURL element is mandatory.
-
-
Check that there is a SpatialDataServiceType element and that has a fixed value equal to 'view'.
-
Check that at least one Keyword element with a value from the "Classification of Spatial data Services" codelist is provided.
-
Check if there is a EX_GeographicBoundingBox element in each named Layer element or if it is inherited from a parent Layer, otherwise:
- check manually that "if the service has an explicit geographic extent." the EX_GeographicBoundingBox element is mandatory.
-
Check that at least one DateOfPublication, DateOfLastRevision or DateOfCreation element is provided and that the date provided is formatted in YYYY-MM-DD format.
-
Check that at least one Conformity element is provided with the declaration of conformity against the Commission Regulation (EC) No 976/2009 of 19 October 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards the Network Services - URI: http://data.europa.eu/eli/reg/2009/976. (Regulation name or URI shall be provided in the Specification Title.)
-
Check that at least one Fees element is provided defining the conditions for access and use. If no conditions apply to the access and use of the resource, "no conditions apply" shall be used. If conditions are unknown "conditions unknown" shall be used.
-
Check that at least one AccessConstraints element is provided.
-
Check that the Responsible Organisation is provided through the ContactOrganization element and that the Responsible Party role is provided through the ContactPosition element with one of the values of code list Responsible party role.
-
Check that the Metadata Point of Contact is provided through the OrganisationName and the EmailAddress elements of the MetadataPointOfContact element.
-
Check that exactly one MetadataDate element is provided and the date is expressed in conformity with ISO 8601.
-
Check that there is a SupportedLanguages element.
-
Table 3a : Mapping between INSPIRE metadata elements and [ISO 19128] WMS elements with the use of extended capabilities.
| INSPIRE Metadata element (Mandatory - Conditional) |
ISO 19128 or INSPIRE ExtendedCapabilities element |
Multiplicity | Condition | Specific TG requirement (if present)/Notes | Check type |
|---|---|---|---|---|---|
| Resource Title (M) | wms:Title | 1 | Automatic | ||
| Resource Abstract (M) | wms:Abstract | 1 | Automatic | ||
| Resource Type (M) | inspire_common:ResourceType (ExtendedCapabilities) |
1 | Requirement 11: the value shall be 'service'. | Automatic | |
| Resource Locator (C) | inspire_common:ResourceLocator (ExtendedCapabilities) |
0..* | Mandatory if linkage to the service is available. | The element is mandatory in the inspire_vs.xsd | Automatic |
| Coupled Resource (C) | wms:MetadataURL (Layer property) |
0..* | Mandatory if linkage to data sets on which the service operates are available. | Requirement 14: the value shall be a URL that allows access to a metadata record. | Automatic + Manual |
| Spatial Data Service Type (M) | inspire_common:SpatialDataServiceType (ExtendedCapabilities) |
1 | Requirement 15: the value shall be 'view'. | Automatic | |
| Keyword (M) | wms:Keyword and wms:Keyword/@vocabulary; inspire_common:Keyword |
1..* | Requirement 16: at least one keyword from the Classification of spatial data services shall be provided. | Automatic | |
| Geographic Bounding Box (C) | wms:EX_GeographicBoundingBox (Layer property) |
0..* | Mandatory for services with an explicit geographic extent. | Automatic + Manual | |
| Temporal Reference (M) | inspire_common:TemporalReference (ExtendedCapabilities) |
1..* | Requirement 20: one of the following dates shall be provided: date of publication, date of last revision, or the date of creation. Date of last revision is preferred. The date shall be expressed in conformity with ISO 8601. | Automatic | |
| Spatial Resolution (C) | wms:Abstract | 0..* | Mandatory when there is a restriction on the spatial resolution for this service. | Manual | |
| Conformity (M) | inspire_common:Conformity (ExtendedCapabilities) |
1..* | Automatic | ||
| Conditions for Access and Use (M) | wms:Fees | 1..* | Requirement 24: If no conditions apply to the access and use of the resource, the value "no conditions apply" shall be used. If conditions are unknown "conditions unknown" shall be used. | Automatic | |
| Limitations on Public Access (M) | wms:AccessConstraints | 1..* | Automatic | ||
| Responsible Organisation (M) | wms:ContactInformation/ wms:ContactPersonPrimary/ wms:ContactOrganization and wms:ContactInformation/ wms:ContactPosition |
1..* | Requirement 26: The value domain of the Responsible Party role shall be one of the values of code list Responsible party role. | Automatic | |
| Metadata Point of Contact (M) | inspire_common:MetadataPointOfContact (ExtendedCapabilities) |
1..* | Requirement 27: The role of the metadata point of contact shall be "pointOfContact". | Automatic | |
| Metadata Date (M) | inspire_common:MetadataDate (ExtendedCapabilities) |
1 | Requirement 29: The date shall be expressed in conformity with the [INS MD], meaning it shall be expressed in conformity with ISO 8601. | Automatic | |
| Metadata Language (M) | inspire_common:SupportedLanguages (ExtendedCapabilities) |
1 | Automatic |
Reference(s):
- TG VS, Chapter 4.2.3.3.1, Requirement 6 - Section 2, Requirement 11
- INS MD, Part C - Table 2; Classification of Spatial data Services, Part D.4
Test type: Automated + Manual
Notes
As stated by the INSPIRE Metadata Technical Guidance [INS MDTG], it is not possible to express the restriction of a service concerning the spatial resolution in the current version of [ISO 19119]. While this issue is being addressed by the standardisation community, spatial resolution restrictions for services shall be written in the Abstract as mandated by the Metadata Technical Guidance [INS MDTG]. Spatial Resolution restrictions at service metadata level shall be declaratively described in the wms:Abstract element.
For the AccessConstraints element, is recommended to use "None" value when any constraints is applied and when constraints are imposed may be used the codelists defined in [ISO 19115, Annex B – Data Dictionary, Section 5.24].
Contextual XPath references
The namespace prefixes used as described in README.md. Related XPaths are provided in the table above.