Abstract Test Suite for View Services Table of Contents · PDF fileAbstract Test Suite for View Services Abstract Test Suite for INSPIRE View Services Technical Guidance ISO 19128

1

Abstract Test Suite for View Services

Abstract Test Suite for INSPIRE View Services Technical Guidance ISO 19128 Profile (OGC

Web Map Service 1.3.0)

Note: This ATS is in Ready for review stage, none of the tests have an official INSPIRE MIG

approval.

Table of Contents A.02.IR04.extended.capabilities.node .................................................................................................. 12

A.03.IR05.schema.validation ................................................................................................................ 13

A.04.IR06.metadataURL.node............................................................................................................... 14

A.05.IR07.extended.capabilities.elements.node .................................................................................. 15

A.06.IR08.language.node ...................................................................................................................... 16

A.07.IR10.title.abstract ......................................................................................................................... 17

A.08.IR11.resource.type.node .............................................................................................................. 18

A.09.IR12.resource.locator.node .......................................................................................................... 19

A.10.IR13.coupled.resource.node ........................................................................................................ 20

A.11.IR14.metadata.record.node ......................................................................................................... 21

A.12.IR15.spatialdataservicetype.node ................................................................................................ 22

A.13.IR18.keywords.node ..................................................................................................................... 23

A.14.IR19.geographicboundingbox.node ............................................................................................. 24

A.15.IR20.dates.node ............................................................................................................................ 25

A.16.IR21.temporal.reference.node ..................................................................................................... 26

A.17.IR22.conformity.deegree.node .................................................................................................... 27

A.18.IR23.conformity.node ................................................................................................................... 28

A.19.IR24.fees.node .............................................................................................................................. 29

A.20.IR25.contactpersonprimary.node................................................................................................. 30

A.21.IR26.contactposition.node ........................................................................................................... 31

A.22.IR27.metadata.pointofcontact.details.node ................................................................................ 32

A.24.IR29.metadata.data.node ............................................................................................................. 33

A.26.IR31.getmap.format.node ............................................................................................................ 34

A.28.IR33.layer.title.node ..................................................................................................................... 35

A.29.IR34.layer.abstract.node .............................................................................................................. 36

A.30.IR35.layer.keywordlist.node ......................................................................................................... 37

A.31.IR36.layer.bbox.node .................................................................................................................... 38

A.32.IR38.layer.identifier.node ............................................................................................................. 39

2

A.33.IR38.authority.url.node ................................................................................................................ 40

A.34.IR46.style.node ............................................................................................................................. 41

A.35.IR39.harmonized.layer.name ....................................................................................................... 42

A.36.IR40.etrs89.itrs.crs ........................................................................................................................ 44

A.37.IR42.inspire.default.style .............................................................................................................. 45

A.38.IR45.IR47.style.legend.url ............................................................................................................. 47

A.39.IR16.spatial.data.service.keyword.embedded.metadata ............................................................ 49

A.40.IR67.IR68.language.affects.capabilities ........................................................................................ 50

A.41.IR69.default.language ................................................................................................................... 52

3

External document references

Abbreviation Document name

INSPIRE

Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007

establishing an Infrastructure for Spatial Information in the European Community

(INSPIRE)

TG VS Technical Guidance for the implementation of INSPIRE View Services 3.11

IR NS

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

IR MD

COMMISSION REGULATION (EC) No 1205/2008 of 3 December 2008 implementing

Directive 2007/2/EC of the European Parliament and of the Council as regards

metadata

TG MD INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115

and EN ISO 19119

IR IOP

COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing

Directive 2007/2/EC of the European Parliament and of the Council as regards

interoperability of spatial data sets and services

WMS OpenGIS Web Map Service (WMS) Implementation Specification, version 1.3.0

TG Requirement coverage

Based on requirement numbering in TG VS.

Req

# Description Covered by test(s)

IR

reference(s)

1 Scoping: ISO 19128 +

INSPIRE ext. n/a n/a

2 WMS basic

conformance class

OGC WMS 1.3.0. A.1.2 Basic WMS Server,

A.03.IR05.schema.validation n/a

3 GetCapabilities,

GetMap OGC WMS 1.3.0. "WMS basic" CC ATS n/a

4 INSPIRE

ExtendedCapabilities A.02.IR04.extended.capabilities.node n/a

http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32007L0002&from=EN



http://inspire.jrc.ec.europa.eu/documents/Network_Services/TechnicalGuidance_ViewServices_v3.11.pdf

http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32009R0976&from=EN



http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2008:326:0012:0030:EN:PDF



http://inspire.ec.europa.eu/documents/Metadata/MD_IR_and_ISO_20131029.pdf

http://inspire.ec.europa.eu/documents/Metadata/MD_IR_and_ISO_20131029.pdf

http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L:2010:323:FULL&from=EN



http://portal.opengeospatial.org/files/?artifact_id=14416

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/README.md#ref_TG_VS

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.03.IR05.schema.validation.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.02.IR04.extended.capabilities.node.md

4

Req


IR

reference(s)

5 GetCapabilities request

parameters OGC WMS 1.3.0. "WMS basic" CC ATS,

IR NS, Annex

III, Chapter

2.1.1

6 INSPIRE MetadataURL

element A.04.IR06.metadataURL.node

7 Use WMS + INSPIRE

extended capabilities Test bound to specific requirements n/a

8 Language section in

Extended capabilities A.06.IR08.language.node

IR NS, Annex

III, Chapter

2.2.3

9 View Service Metadata

in Discovery Service Not testable

IR NS, Annex

III, Chapter 4.

10 Mapping of service

metadata elements

A.05, A.07, A.08, A.09, A.10, A.11, A.12, A.13, A.14,

A.15, A.16, A.17, A.18, A.19, A.20, A.21, A.22, A.24 IR MD, Part B

11 ResourceType element A.08.IR11.resource.type.node

12 ResourceLocator

element A.09.IR12.resource.locator.node

13 MetadataURL for each

layer A.10.IR13.coupled.resource.node

14 MetadataURL

resolvable to MD

record

A.11.IR14.metadata.record.node

15 SpatialDataServiceType

element A.12.IR15.spatialdataservicetype.node

16 Classification of Spatial

Data Services keyword

A.39.IR16.spatial.data.service.keyword.embedded.met

adata

17 Additional keywords Not testable

18 MD keywords A.13.IR18.keywords.node

19 Geographic Bounding

Box A.14.IR19.geographicboundingbox.node

20 Temporal reference

dates A.15.IR20.dates.node

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/README.md#ref_IR_NS

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.04.IR06.metadataURL.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.06.IR08.language.node.md



https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.05.extended.capabilities.elements.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.07.IR10.title.abstract.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.08.IR11.resource.type.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.09.IR12.resource.locator.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.10.IR12.coupled.resource.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.11.IR14.metadata.record.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.12.IR15.spatialdataservicetype.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.13.IR18.keywords.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.14.IR19.geographicboundingbox.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.15.IR20.dates.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.16.IR21.temporal.reference.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.17.IR22.conformity.degree.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.18.IR23.conformity.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.19.IR24.fees.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.20.IR25.contactpersonprimary.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.21.IR26.contactposition.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.22.IR27.IR28.metadata.pointofcontact.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.24.IR29.metadata.date.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/README.md#ref_IR_MD






https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.39.IR16.spatial.data.service.keyword.embedded.metadata.md





5

Req


IR

reference(s)

21 TemporalReference

element A.16.IR21.temporal.reference.node

22 Degree of conformity A.17.IR22.conformity.degree.node

23 Conformity A.18.IR23.conformity.node

24 Conditions of access

and use A.19.IR24.fees.node

25 Responsible party A.20.IR25.contactpersonprimary.node

26 Responsible party role A.21.IR26.contactposition.node

27 Point of contact with

name and email A.22.IR27.IR28.metadata.pointofcontact.node

28 Point of contact in ext.

capabilities A.22.IR27.IR28.metadata.pointofcontact.node

29 Metadata date A.24.IR29.metadata.date.node

30 GetCapabilities

operation A.03.IR05.schema.validation

31 GetMap with PNG of

GIF A.26.IR31.getmap.format.node

32 Layer metadata A.28, A.29, A.30, A.31, A.32, A.33, A.34, A.35, A.36,

A.37, A.38

33 Harmonized layer title A.28.IR33.layer.title.node

34 Layer abstract A.29.IR34.layer.abstract.node

35 Additional layer

keywords A.30.IR35.layer.keywordlist.node

36 Layer Bounding Box A.31.IR36.layer.bbox.node

37 Unique Resource

Indentifier (layer

origin)

Not testable

38 AuthorityURL &

Indentifier

A.32.IR38.layer.identifier.node,

A.33.IR38.layer.authority.url.node











https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.26.IR31.getmap.format.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.28.IR33.layer.title.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.29.IR34.layer.abstract.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.30.IR35.layer.keywordlist.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.31.IR36.layer.bbox.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.32.IR38.layer.identifier.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.33.IR38.layer.authority.url.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.34.IR46.style.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.36.IR40.etrs89.itrs.crs.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.37.IR42.inspire.default.style.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.38.IR45.IR47.style.legend.url.md







6

Req


IR

reference(s)

39 Harmonized layer

name A.35.IR39.harmonized.layer.name

IR IOP, Article

14

40 Coordinate Reference

Systems A.36.IR40.etrs89.itrs.crs

41 Style composed of title

and identifier A.34.IR46.style.node

42 inspire_common:defau

lt style A.37.IR42.inspire.default.style

43 GCM fallback style Not testable

44 inspire_common:defau

lt is the default layer

Style

Not testable

45 Layer legend for each

style+language

combination

A.38.IR45.IR47.style.legend.url

46 Style by wms:Style

element A.34.IR46.style.node

47 Layer legend by

LegendURL element A.38.IR45.IR47.style.legend.url

48 Layer Dimension

elements Not testable

49 Category layers Not testable

50 GetMap: VERSION

parameter OGC WMS 1.3.0. ATS: A.1.2.4 GetMap response

51 GetMap: REQUEST


52 GetMap: LAYERS


53 GetMap: STYLES


54 GetMap: CRS



https://github.com/inspire-eu-validation/ats-view-wms/blob/master/README.md#ref_IR_IOP







7

Req


IR

reference(s)

55 GetMap: BBOX


56 GetMap: WIDTH &

HEIGHT parameters OGC WMS 1.3.0. ATS: A.1.2.4 GetMap response

57 GetMap: FORMAT


58 GetMap:

TRANSPARENT

parameter

OGC WMS ATS: 1.3.0. A.1.2.4 GetMap response

59 GetMap: EXCEPTIONS


60 Link View Service:

scoping Not testable

61 Service metadata in

Discovery Service Not testable

62 Cascading layers in

collated capabilities Not testable

63 Cascaded layers to

include "cascaded"

attribute

Not testable

64

The value of the

"cascaded" attribute

indicates cascading

level

Not testable

65 Transparency &

background for

collated layers

Not testable

66 List of supported

languages A.06.IR08.language.node

IR NS, Annex

III, Chapter

2.2.3

67 Client may select the

language A.40.IR67.IR68.language.affects.capabilities

68 GetCapabilities:

LANGUAGE parameter A.40.IR67.IR68.language.affects.capabilities



https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.40.IR67.IR68.language.affects.capabilities.md


8

Req


IR

reference(s)

69 GetCapabilities: default

language A.41.IR69.default.language

70 ResponseLanguage

element A.40.IR67.IR68.language.affects.capabilities

IR NS, Annex

III, Chapter

2.2.3

71

SupportedLanguages

and DefaultLanguage

elements

A.06.IR08.language.node

IR NS, Annex

III, Chapter

2.2.3

72 ExtendedCapabilities

XML Schema A.02.IR04.extended.capabilities.node

73 GetMap: Portrayal

requiring localized

rendering

Not testable

Two scenarios for providing the service metadata

The TG VS gives two options (scenarios) for providing the service metadata in the Capabilities

document of the WMS services:

1. INSPIRE network service metadata in a Discovery Service is referenced through an extended capability.

2. Use (extended) capabilities to map all INSPIRE metadata elements to the WMS 1.3.0 elements.

The requirements considering including the mandatory INSPIRE metadata elements on the

Capabilities document depend on which scenario the data provider has chosen to follow. Since

there is no dedicated method in TG VS for the data prodiver to indicate which scenario he/she

has chosen, the validator software must use the following logic to decide the appropriate set of

tests to apply:

The scenario 2 is selected only if at least one of the following elements exists in the WMS

Capabilities document's inspire_vs:ExtendedCapabilities element:

inspire_common:ResourceLocator, inspire_common:ResourceType, inspire_common:TemporalReference, inspire_common:Conformity, inspire_common:MetadataPointOfContact, inspire_common:MetadataDate, inspire_common:SpatialDataServiceType, inspire_common:MandatoryKeyword, inspire_common:Keyword

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.41.IR69.default.language.md








9

If none of them is found, the scenario 1 must be selected for the validation.

The the case of scenario 1, the the metadata record referred to by the

inspire_common:MetadataUrl element must also pass the service scenario of the test suite

ats-metadata.

Tests

This Conformance Class contains the following tests. The "scenario" column of the test table

below indicates if the tests are to be applied in service metadata validation scenarios 1, 2 or all

(see above).

The tests with a prefix "WMS" refer to the ATS included in the OGC WMS 1.3.0 specification

(Annex A).

Identifier Scenario(s) Status

WMS.A.1.2.1 Version negotiation All Final

WMS.A.1.2.2 Request parameter rules All Final

WMS.A.1.2.3 GetCapabilities response All Final

WMS.A.1.2.4 GetMap response All Final

A.02.IR04.extended.capabilities.node All Ready for review

A.03.IR05.schema.validation All Ready for review

A.04.IR06.metadataURL.node 1 only Ready for review

A.05.IR07.extended.capabilities.elements.node 2 only Ready for review

A.06.IR08.language.node All Ready for review

A.07.IR10.title.abstract All Ready for review

A.08.IR11.resource.type.node 2 only Ready for review

A.09.IR12.resource.locator.node 2 only Ready for review

A.10.IR13.coupled.resource.node All Ready for review

A.11.IR14.metadata.record.node All Ready for review

A.12.IR15.spatialdataservicetype.node 2 only Ready for review

A.13.IR18.keywords.node 2 only Ready for review

A.14.IR19.geographicboundingbox.node All Ready for review

https://github.com/inspire-eu-validation/ats-metadata

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/README.md#ref_WMS



https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.04.IR06.metadataURL.node.md

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.05.extended.capabilities.elements.node.md


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.07.IR10.title.abstract.md








10

Identifier Scenario(s) Status

A.15.IR20.dates.node 2 only Ready for review

A.16.IR21.temporal.reference.node 2 only Ready for review

A.17.IR22.conformity.degree.node 2 only Ready for review

A.18.IR23.conformity.node 2 only Ready for review

A.19.IR24.fees.node All Ready for review

A.20.IR25.contactpersonprimary.node All Ready for review

A.21.IR26.contactposition.node All Ready for review

A.22.IR27.IR28.metadata.pointofcontact.node 2 only Ready for review

A.24.IR29.metadata.date.node 2 only Ready for review

A.26.IR31.getmap.format.node All Ready for review

A.28.IR33.layer.title.node All Ready for review

A.29.IR34.layer.abstract.node All Ready for review

A.30.IR35.layer.keywordlist.node All Ready for review

A.31.IR36.layer.bbox.node All Ready for review

A.32.IR38.layer.identifier.node All Ready for review

A.33.IR38.layer.authority.url.node All Ready for review

A.34.IR46.style.node All Ready for review

A.35.IR39.harmonized.layer.name All Ready for review

A.36.IR40.etrs89.itrs.crs All Ready for review

A.37.IR42.inspire.default.style All Ready for review

A.38.IR45.IR47.style.legend.url All Ready for review

A.39.IR16.spatial.data.service.keyword.embedded.metadata 2 only Ready for Review

A.40.IR67.IR68.language.affects.capabilities All Ready for review

A.41.IR69.default.language All Ready for review

Open issues










https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.26.IR31.getmap.format.node.md














https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.41.IR69.default.language.md

11

The requirement 6 for providing a link to the INSPIRE MetadataURL is limited to service metadata scenario 1. However, the requirement 9 states that the View Service metadata must be included in an INSPIRE Discovery regardless of the chosen scenario. Also the Requirements 60 & 61 state that the Link View Service operation is realized by using a Discovery Service. Thus it would make sense that the MetadataURL element if the Service in the ExtendedCapabilities would be mandatory in both scenarios.

Should the mandatory keyword from the "Classification of Spatial data Services" be also given as wms:Keyword in the Capabilities document under wms:WMS_Capabilities/wms:Service/wms:KeywordList in addition to the ExtendedCapabilities (scenario 2) or in the referenced service metadata record (scenario 1)?

XML namespace prefixes

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

http://www.opengis.net/wms

http://www.w3.org/1999/xlink

http://www.isotc211.org/2005/gmd

http://inspire.ec.europa.eu/schemas/inspire_vs/1.0

http://inspire.ec.europa.eu/schemas/common/1.0

12

A.02.IR04.extended.capabilities.node

Purpose: The metadata response parameters shall be provided through the service Capabilities,

as defined in the WMS Standard ISO 19128, Section 7.2.4. These capabilities are mandatory

and defined when a WMS is set up. They consist of service information, supported operations

and parameters values. The extended capabilities section shall be used to fully comply with the

INSPIRE View Service metadata requirements (see section 4.2.3.3.1).

Prerequisites

Test for the existence of default element namespace. Test for the existence of the namespaces for INSPIRE View Services inspire_vs and

inspire_common.

Test method

First check if the service document contains the ExtendedCapabilities node. Then check that the extended capabilities element validates against the INSPIRE schemas.

Reference (s): TG VS, Chapter 4.2.3.1

Notes

Contextual XPath references

The namespace prefixes used as described in README.md.

Abbreviation XPath expression

ExtendedCapabilities /wms:WMS_Capabilities/wms:Capability/inspire_vs:ExtendedCapabilities


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/README.md#namespaces

13

A.03.IR05.schema.validation

Purpose: The operation for implementing INSPIRE Get View Service Metadata operation is

the GetCapabilities operation. The parameters defined within the ISO 19128 standard shall be

used to convey relevant information in order to get the expected responses as described in INS

NS, Annex III, Section 2.2 of the Regulation on INSPIRE Network Services.

Prerequisites

Test for the existence of default element namespace.

Test method

First check if the ISO 19128 schema is given in the service capabilities Then check that the GetCapabilities request result validates against this schema.

Reference (s): TG VS, Chapter 4.2.3.2

Notes




service

Capabilities /WMS_Capabilities/@xsi:schemaLocation

GetCapabilities

request

/WMS_Capabilities/Capability/Request/GetCapabilities/DCPType/HTTP/Get/

OnlineResource/@xlink:href

http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd



14

A.04.IR06.metadataURL.node

Purpose: The element within the extended INSPIRE capabilities of an ISO 19128 – WMS

1.3.0 wms:Capability element shall be used to reference the INSPIRE service metadata

available through an INSPIRE Discovery Service. Mandatory ISO 19128 – WMS 1.3.0

metadata elements shall be mapped to INSPIRE metadata elements to implement a consistent

interface.

Prerequisites


inspire_common.

Test method

First check if the metadata URL node exists in the ExtendedCapabilities section and validates against the ISO metadata schema.

If no metadata URL is given then all mandatory ISO 19128 metadata elements must exist in the ExtendedCapabilities section.

Reference(s):

TG VS, Chapter 4.2.3.3.1 IR Annex III, Part A, Chapter 2.2.1

Notes




metadataURL /WMS_Capability/Capability/inspire_vs:ExtendedCapabilities/inspire_comm

on:MetadataUrl

ExtendedCapabilities /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities

http://www.isotc211.org/2005/gmd/gmd.xsd

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/see%20%5BTG%20VS%5D%28README.md#ref_TG_VS%29,%20Table%203



15

A.05.IR07.extended.capabilities.elements.no

de

Purpose: INSPIRE metadata are mapped to WMS capabilities elements to its full extent. It is

mandatory to use the mapping provided in this Technical Guideline (described in Section

4.2.3.3.1.1 to 4.2.3.3.1.16. INSPIRE metadata elements that cannot be mapped to available ISO

19128 – WMS1.3.0 elements are implemented as Extended Capabilities. Metadata are

published through a service's capabilities document and can be harvested by an INSPIRE

Discovery service.

Prerequisites


inspire_common.

Test method

Check if all mandatory ISO 19128 metadata elements exist in the ExtendedCapabilities section.

Reference(s):


Notes





https://github.com/inspire-eu-validation/ats-view-wms/blob/master/see%20%5BTG%20VS%5D%28README.md#ref_TG_VS%29,%20Table%203



16

A.06.IR08.language.node

Purpose: INSPIRE metadata are mapped to WMS capabilities elements to its full extent. It is

mandatory to use the mapping provided in this Technical Guideline (described in Section

4.2.3.3.1.1 to 4.2.3.3.1.16. INSPIRE metadata elements that cannot be mapped to available ISO

19128 – WMS1.3.0 elements are implemented as Extended Capabilities. Metadata are

published through a service's capabilities document and can be harvested by an INSPIRE

Discovery service.

Prerequisites


inspire_common.

Test method

Check if there is a supportedLanguages node and a ResponseLanguage node in the ExtendedCapabilities section.

Reference(s):


Notes




SupportedLanguage /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_com

mon:SupportedLanguages

ResponseLanguage /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_com

mon:ResponseLanguage




17

A.07.IR10.title.abstract

Purpose: A View Service must contain a non-empty Title and Abstract to fulfill the INSPIRE

Metadata requirements for Resource Title, Resource Abstract and Spatial Resolution.

Prerequisites


Test method

Check that both Title and Abstract exist and are non-empty. If so, pass the test. Otherwise fail the test.

Reference(s):

TG VS, Requirement 10, Chapter 4.2.3.3.1

Notes




Title /wms:WMS_Capabilities/wms:Service/wms:Title

Abstract /wms:WMS_Capabilities/wms:Service/wms:Abstract

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.07.IR10.title.abstract.md#title

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.07.IR10.title.abstract.md#abstract



18

A.08.IR11.resource.type.node

Purpose: Within the scope defined by the INSPIRE directive the value of the Resource Type

shall be fixed to service for spatial data services. As the Resource Type is not supported by

ISO 19128 – WMS 1.3.0, an extension shall be used to map this to an element within an

element.

Prerequisites


inspire_common.

Test method

First check if there is a ResourceType node in the ExtendedCapabilities section If yes, check that it is set to 'service'.

Reference(s):

TG VS, Chapter 4.2.3.3.1.3

Notes




ResourceType /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_com

mon:ResourceType




19

A.09.IR12.resource.locator.node

Purpose: An extension shall be used to map Resource Locator to an element within an element.

Prerequisites


inspire_common.

Test method

Check if there is a ResourceLocator node in the ExtendedCapabilities section.

Reference(s):


Notes




ResourceLocator

/WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_co

mmon:Conformity/inspire_common:Specification/inspire_common:Resou

rceLocator/inspire_common:URL




20

A.10.IR13.coupled.resource.node

Purpose: Coupled Resource shall be mapped to the elements of the Layer elements of the

service capabilities. If linkage to the data sets or series on which the service operates are

available, then the linkage to these resources shall be provided as stated by the INSPIRE

Metadata Technical Guidance INS MDTG.

Prerequisites


Test method

Check if there is a MetadataURL node for each layer. If yes, check if the href in the OnlineResource node of the MetadataURL section is a valid link.

Reference(s):


Notes




MetadataURL /WMS_Capabilities/Capability/Layer/MetadataURL

OnlineResource/@xlink:href /WMS_Capabilities/Capability/Layer/MetadataURL/Format/Online

Resource/@xlink:href





21

A.11.IR14.metadata.record.node

Purpose: Each of the elements shall be populated with a URL that allows access to an

unambiguous metadata record. The URL shall be either an HTTP/GET call on the

GetRecordById operation of the Discovery Service or a direct link to the ISO 19139 metadata

document.

Prerequisites


Test method

Then check if there is a MetadataURL node for each layer. If yes, check if the href in the OnlineResource node of the MetadataURL section is a valid link.

Reference(s):


Notes




MetadataURL /WMS_Capabilities/Capability/Layer/MetadataURL

OnlineResource/@xlink:href /WMS_Capabilities/Capability/Layer/MetadataURL/Format/Online

Resource/@xlink:href





22

A.12.IR15.spatialdataservicetype.node

Purpose: For the Spatial Data Service Type as defined by the INSPIRE Metadata Regulation

INS MD (‘view’) an extension shall be used to map this to an element within an element. For

an INSPIRE View Service the Spatial Data Service Type shall have a fixed value “view”

according to INSPIRE Metadata Regulation INS MD Part 3.

Prerequisites


inspire_common.

Test method

Check if there is a SpatialDataServiceType node in the ExtendedCapabilities section If yes, check that it is set to 'view'.

Reference(s):


Notes




SpatialDataServiceType /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_co

mmon:SpatialDataServiceType




23

A.13.IR18.keywords.node

Purpose: The keywords shall be mapped to the capabilities extension and within an element.

Prerequisites


inspire_common.

Test method

Check if there are a Keyword node and a MandatoryKeyword node in the ExtendedCapabilities section.

Reference(s):


Notes




Keyword /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_co

mmon:Keyword

MandatoryKeyword /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_co

mmon:MandatoryKeyword




24

A.14.IR19.geographicboundingbox.node

Purpose: Geographic Bounding Box shall be mapped to the EX_GeographicBoundingBox

element of Layer elements.

Prerequisites


inspire_common.

Test method

Check if there is a EX_GeographicBoundingBox node in each Layer section of the Capabilities section.

Reference(s):


Notes




EX_GeographicBoundingBox /WMS_Capabilities/Capability/Layer/EX_GeographicBounding

Box

Layer /WMS_Capabilities/Capability/Layer

Capabilities /WMS_Capabilities/Capability



25

A.15.IR20.dates.node

Purpose: To be compliant with the INSPIRE Metadata Regulation INS MD and with ISO

19115 one of following dates shall be used: 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

the INS MD.

Prerequisites


inspire_common.

Test method

Check if there is either a DateOfCreation node, a DateOfPublication node or a DateOfLastRevision node in the TemporalReference section.

Reference(s):


Notes




DateOfCreation /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_co

mmon:TemporalReference/inspire_common:DateOfCreation

DateOfPublication /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_co

mmon:TemporalReference/inspire_common:DateOfPublication

DateOfLastRevision /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_co

mmon:TemporalReference/inspire_common:DateOfLastRevision

TemporalReference /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_co

mmon:TemporalReference



26

A.16.IR21.temporal.reference.node

Purpose: As the Temporal Reference is not directly supported by ISO 19128 – WMS 1.3.0 an

extension shall be used to map this to an element within an element.

Prerequisites


inspire_common.

Test method

Check if there is a TemporalReference node in the ExtendedCapabilities section.

Reference(s):


Notes




TemporalReference /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_co

mmon:TemporalReference




27

A.17.IR22.conformity.deegree.node

Purpose: The INSPIRE Metadata Regulation INS MD requires that metadata shall include

information on the degree of conformity with the implementing rules provided in Art. 7.1

(Interoperability of spatial data sets and services) of the INSPIRE Directive Directive

2007/2/EC.

Prerequisites


inspire_common.

Test method

Check if there is a Conformity node in the ExtendedCapabilities section. If yes, check that it has a Deegree node with one of these values: notEvaluated, conformant,

notConformant.

Reference(s):


Notes




Conformity /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_com

mon:Conformity


Degree /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_com

mon:Conformity/inspire_common:Degree



28

A.18.IR23.conformity.node

Purpose: An extension shall be used to map this to an element within an element.

Prerequisites


inspire_common.

Test method

Check if there is a Conformity node in the ExtendedCapabilities section.

Reference(s):


Notes




Conformity /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_com

mon:Conformity




29

A.19.IR24.fees.node

Purpose: Metadata concerning to conditions for access and use shall be mapped to the

wms:Fees element of the capabilities. 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.

Prerequisites


inspire_common.

Test method

Check if there is a Fees node in the Service Capabilities If yes, check that it has one of the values: no conditions apply, conditions unknown or free

text.

Reference(s):


Notes




Fees /WMS_Capabilities/Service/Fees

Service /WMS_Capabilities/Service



30

A.20.IR25.contactpersonprimary.node

Purpose: Responsible Party as described in the INSPIRE Metadata Regulation INS MD shall

be mapped to the wms:ContactOrganization element of the wms:ContactPersonPrimary within

the wms:ContactInformation element.

Prerequisites


inspire_common.

Test method

Check if there is a ContactPersonPrimary node in the ContactInformation section.

Reference(s):


Notes




ContactPersonPrimary /WMS_Capabilities/Service/ContactInformation/ContactPersonPrimary

ContactInformation /WMS_Capabilities/Service/ContactInformation



31

A.21.IR26.contactposition.node

Purpose: The value domain of the Responsible Party role shall comply with the INSPIRE

Metadata Regulation INS MD, Part D6. The Responsible Party Role shall be mapped to the

wms:ContactPosition of the wms:ContactInformation element

Prerequisites


Test method

Check if there is a ContactPosition node in the ContactInformation section If yes, check if that it has one of the values: resourceProvider, custodian, owner, user,

distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author.

Reference(s):


Notes




ContactPosition /WMS_Capabilities/Service/ContactInformation/ContactPosition

ContactInformation /WMS_Capabilities/Service/ContactInformation



32

A.22.IR27.metadata.pointofcontact.details.

node

Purpose: INSPIRE is more demanding than ISO 19115 by mandating both the name of the

organisation, and a contact e-mail address. The role of the responsible party serving as a

metadata point of contact is out of scope of the Metadata Regulation INS MD, but this property

is mandated by ISO 19115. Its value shall be defaulted to “pointOfContact”.

Prerequisites


inspire_common.

Test method

Check if there is a MetadataPointOfContact node in the ExtendedCapabilities section. If yes, check if there is a OrganisationName node and a EmailAddress node in the

MetadataPointOfContact section.

Reference(s):


Notes




MetadataPointOfContact /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspir

e_common:MetadataPointOfContact


OrganisationName

/WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspir

e_common:MetadataPointOfContact/inspire_common:Organisation

Name

EmailAddress /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspir

e_common:MetadataPointOfContact/inspire_common:EmailAddress



33

A.24.IR29.metadata.data.node

Purpose: As the Metadata Date is not supported by ISO 19128 – WMS 1.3.0, an extension

shall be used to map this to an element within an element. The date shall be expressed in

conformity with the INS MD.

Prerequisites


inspire_common.

Test method

Check if there is a MetadataDate node in the ExtendedCapabilities section.

Reference(s):


Notes




MetadataDate /WMS_Capabilities/Capability/inspire_vs:ExtendedCapabilities/inspire_com

mon:MetadataDate




34

A.26.IR31.getmap.format.node

Purpose: GetMap operation metadata shall be mapped to the wms:GetMap element. Either

PNG or GIF format (without LZW compression) with transparency shall be supported by the

View service INS NS, Annex III, Part B.

Prerequisites


Test method

Check if there is a GetMap node in the Request section If yes, check if there is one Format node in the GetMap section with the value 'image/png' or

one with the value 'image/gif'.

Reference(s):


Notes




GetMap /WMS_Capabilities/Capability/Request/GetMap

Request /WMS_Capabilities/Capability/Request

Format /WMS_Capabilities/Capability/Request/GetMap/Format



35

A.28.IR33.layer.title.node

Purpose: Layer title is mapped with wms:Title. The harmonised title of a layer for an INSPIRE

spatial data theme is defined by INS DS and shall be subject to multilingualism (translations

shall appear in each mono-lingual capabilities localised documents).

Prerequisites


Test method

Check if there is a Title node in each Layer section.

Reference(s):


Notes




Title /WMS_Capabilities/Capability/Layer/Title




36

A.29.IR34.layer.abstract.node

Purpose: Text describing the layer. Subject to multilingualism. It shall be mapped with the

wms:Abstract element.

Prerequisites


Test method

Check if there is an Abstract node in each Layer section.

Reference(s):


Notes




Abstract /WMS_Capabilities/Capability/Layer/Abstract




37

A.30.IR35.layer.keywordlist.node

Purpose: Keywords shall be mapped to the wms:KeywordList element.

Prerequisites


Test method

Check if there is a KeywordList node in each Layer section.

Reference(s):


Notes




KeywordList /WMS_Capabilities/Capability/Layer/KeywordList




38

A.31.IR36.layer.bbox.node

Purpose: This Layer metadata element shall be mapped to the wms:BoundingBox element.

The minimum bounding rectangle of the area covered by the Layer in all supported CRS shall

be given.

Prerequisites


Test method

Check if there is a BoundingBox node in each Layer section for each CRS declared.

Reference(s):

IR Annex III, Part A, Chapter 2.2.4 TG VS, Chapter 4.2.3.3.4.4

Notes




BoundingBox /WMS_Capabilities/Capability/Layer/BoundingBox


CRS /WMS_Capabilities/Capability/Layer/BoundingBox/@CRS



39

A.32.IR38.layer.identifier.node

Purpose: To be able to map the concept of a responsible body/codeSpace and local

identifier/code to ISO 19128), AuthorityURL and Identifier elements shall be used. The

authority name and explanatory URL shall be defined in a separate AuthorityURL element,

which may be defined once and inherited by subsidiary layers. Identifiers themselves are not

inherited.

Prerequisites


Test method

Check if there is a Identifier node in each Layer section other than layer without Name element formed from daughters and each Identifier node has been declared in an AuthorityURL node of the layer itself or its parent layer by heritage.

Reference(s):

TG VS, Chapter 4.2.3.3.4.5 IR Annex III, Part A, Chapter 2.2.4

Notes




Identifier /WMS_Capabilities/Capability/Layer/Identifier


@authority /WMS_Capabilities/Capability/Layer/Identifier/@authority



40

A.33.IR38.authority.url.node

Purpose: The INS MD Regulation defines a Unique Resource Identifier as a value uniquely

identifying an object within a namespace. The code property shall be specified at a minimum,

and a codeSpace (namespace) property may be provided.

Prerequisites


Test method

Check if there is a AuthorityURL node in each Layer section.

Reference(s):


Notes




AuthorityUrl /WMS_Capabilities/Capability/Layer/AuthorityUrl




41

A.34.IR46.style.node

Purpose: Style shall be mapped to the wms:Style element. The human readable name shall be

mapped to the wms:Title element and the Unique Identifier shall be mapped to the wms:Name

element.

Prerequisites


Test method

Check if there is a Title node and a Name node with a Unique Identifier in each Style section.

Reference(s):


Notes




Title /WMS_Capabilities/Capability/Layer/Style/Title

Name /WMS_Capabilities/Capability/Layer/Style/Name

Style /WMS_Capabilities/Capability/Layer/Style



42

A.35.IR39.harmonized.layer.name

Purpose: It must be unambiguous to find out which of the layers provided by the service

visualize the INSPIRE spatial data sets given in the Data Specifications for each INSPIRE

theme. These layers must be named according to the INSPIRE Harmonised layer names

defined in IR IOP

Prerequisites


Test method

The identifiers of the WMTS layers portraying INSPIRE datasets must be INSPIRE

harmonised names. To determine if a layer is portraying an INSPIRE dataset, the metadata

record describing the portrayed dataset must be available for validator.

For each Layer element provided by the service according to it's Service Metadata:

For each MetadataURL element of the layer as metadata: o Check that metadata contains an OnlineResource element. If yes,

Check that OnlineResource element contains a non-empty href attribute. If it does,

Check that the href attribute value is a valid URL and fetch the document it refers to. If not valid URL or the document cannot be fetched mark this layer as failed. If a document fetch is successful:

Check that the fetched document contains is a valid INSPIRE metadata record for a dataset at it's document root. If yes, then

Check if the Specification contains one of the official translations of the names of IR IOP and that the value of Pass equals "true".

If no valid INSPIRE dataset metadata record is found or Specification condition above is not met, mark this layer skipped as a non-harmonised or non-INSPIRE layer. Otherwise:

Check that the trimmed string content of the Name element matches one the harmonised layer names given in IR IOP or it's amendments. If matched, mark layer as passed.

If in the end each of the layers is either skipped or passed, the test passes. If there are more than one layer with the MetadataURL element pointing to the same INSPIRE

metadata record, the Name element of only one of them needs to match one of the harmonised layer names in order for the test to pass for all of those layers.

Reference(s)

IR IOP Article 14 TG VS, chapters 5.2.3.3.4.5 and 5.2.3.3.4.6



https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md#layer

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md#metadata

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md#onlineresource

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md#onlineresource

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md#href_attr

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md#specification


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md#pass

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md#specification

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.35.IR39.harmonized.layer.name.md#name







43

Test type: Automated

Notes

Note 1: The harmonised names only apply to the harmonised INSPIRE datasets provided

according to the INSPIRE Data Specifications.

Note 2: The use and usefulness of the harmonised layer names and titles is under discussion,

see https://ies-svn.jrc.ec.europa.eu/issues/2172 and https://ies-svn.jrc.ec.europa.eu/

projects/miwp-20

Note 3: It's assumed that there may be layers providing portrayals for both the INSPIRE

datasets and non-INSPIRE data sets in the same service. Also it's assumed, that there may be

more than one layer portraying the same dataset and thus pointing to the same metadata record

using the MetadataURL element.

Note 4: This test should be kept harmonized with the corresponding WMTS profile test

A.04.layer.name.id




Layer /wms:WMS_Capabilities/wms:Capability//wms:Layer

MetadataURL

OnlineResource

element

./wms:MetadataURL

OnlineResource

element ./wms:OnlineResource

href attribute ./@xlink:href

Name element ./wms:Name

Specification

/csw:GetRecordByIdResponse/gmd:MD_Metadata/gmd:dataQualityInfo/gmd

:DQ_DataQuality/gmd:report/gmd:DQ_DomainConsistency/gmd:result/gmd:

DQ_ConformanceResult/gmd:specification/gmd:CI_Citation/gmd:title/gco:Ch

aracterString

Pass

/csw:GetRecordByIdResponse/gmd:MD_Metadata/gmd:dataQualityInfo/gmd

:DQ_DataQuality/gmd:report/gmd:DQ_DomainConsistency/gmd:result/gmd:

DQ_ConformanceResult/gmd:pass/gco:Boolean

https://ies-svn.jrc.ec.europa.eu/issues/2172

https://ies-svn.jrc.ec.europa.eu/%20projects/miwp-20

https://ies-svn.jrc.ec.europa.eu/%20projects/miwp-20


https://github.com/inspire-eu-validation/ats-view-wmts/blob/master/A.04.layer.name.id.md


44

A.36.IR40.etrs89.itrs.crs

Purpose: All INSPIRE spatial datasets must be provided at using at least one geographical

coordinate system based on either ETRS89 (for datasets within continental Europe) or ITRS

(outside continental Europe).

Prerequisites


Test method

For each Layer:

Check if the text content of at least one of the CRS elements matches the CRS identifier of one of the ETRS89 based or ITRS based coordinate systems.

If no match is found, repeat the same test recursively with the Parent layer, if one exists, until a match is found or no parent layer is found.

If CRS match is found, pass the test, otherwise fail the test.

Reference(s):

TG VS, chapter 4.2.3.3.4.7 Coordinate reference systems


Notes

This test is a tricky one and will not be complete without a machine-readable "whitelist"

register of the acceptable CRSes with their CRS identifiers and commonly used aliases ("label"

and "URL" versions). To implement the test this kind on publicly available, official list must

be established.





CRS elements ./wms:CRS

Parent Layer ../../wms:Layer


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.36.IR40.etrs89.itrs.crs.md#layer

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.36.IR40.etrs89.itrs.crs.md#crs

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.36.IR40.etrs89.itrs.crs.md#parent_layer



45

A.37.IR42.inspire.default.style

Purpose: To make combining of layers from different INSPIRE data providers possible, the

layers portraying harmonized particular INSPIRE datasets must be made available with the

same harmonized INSPIRE rendering styles as specified in the Data Specification documents

for each theme.

Prerequisites

A.03.IR05.schema.validation A.35.IR39.harmonized.layer.name

Test method

For each Layer qualified as presenting an INSPIRE harmonized dataset during the previously

run test A.35.IR39.harmonized.layer.name:

For each Style element within the Layer: o If no required default style for this layer is given in the INSPIRE Data Specification in

which this harmonized layer name is introduced, pass the test for this layer. Otherwise:

Check if the Style Name equals the name of the default style name for this layer as defined by the Portrayal section of the INSPIRE Data Specification of the INSPIRE theme.

If none of the Style Name elements match, repeat the test recursively for any Parent Layers until a match is found or there is no parent layer (1). If no match was found in the end, fail the test for the original layer.

All layers not qualified as presenting INSPIRE harmonized datasets must be ignored in running this test.

Reference(s):

TG VS, chapter 4.2.3.3.4.8 Styles


Notes

1. Note that the parent layers do not have to be qualified as INSPIRE harmonized layers to be included in the recursive style name matching.







https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.37.IR42.inspire.default.style.md#Layer


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.37.IR42.inspire.default.style.md#style

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.37.IR42.inspire.default.style.md#style-name

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.37.IR42.inspire.default.style.md#style-name

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.37.IR42.inspire.default.style.md#parent_layer



46


Style element ./wms:Style

Style Name ./wms:Style/wms:Name

Parent Layer ../../wms:Layer

47

A.38.IR45.IR47.style.legend.url

Purpose: Legend is required for explaining the data visualization used for each layer. If the

legend contains language-specific elements, localized legends shall be made available in each

localized capabilities document.

Prerequisites

A.03.IR05.schema.validation A.34.IR46.style.node A.35.IR39.harmonized.layer.name

Test method

For each Layer qualified as presenting an INSPIRE harmonized dataset during the previously

run test A.35.IR39.harmonized.layer.name:

Check that for each Style element: o There exists a non-empty href attribute in the OnlineResource element. Let the value

of the attibute be href. o Resolve and download the Internet resource referred to by href. If the download is

successful and a non-empty image file returned: If the Format element equals 'image/gif' or 'image/png':

the downloaded resource must be a valid image of these image formats correspondingly. If it is, pass the test. If not, fail the test for this Style.

Otherwise, pass the test for this Style. o Otherwise, fail the test for this Style

Reference(s)

TG VS, chapter 4.2.3.3.4.8 Styles IR NS, Annex III, Part A, 2.2.4. Layers Metadata parameters


Notes

Interpreted as to be applicable only to layers with an INSPIRE harmonized name. Note that it's generally not required for the validator to recognize the image formats of the

downloaded legend files in order to pass the test.






https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.38.IR45.IR47.style.legend.url.md#Layer


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.38.IR45.IR47.style.legend.url.md#style

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.38.IR45.IR47.style.legend.url.md#href

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.38.IR45.IR47.style.legend.url.md#format




48



Style element ./wms:Style

href attribute ./wms:Style/wms:LegendURL/wms:OnlineResource/@xlink:href

Format element ./wms:Style/wms:LegendURL/wms:Format

49

A.39.IR16.spatial.data.service.keyword.emb

edded.metadata

Purpose: The INSPIRE Metadata Regulation [INS MD] mandates that in the case of spatial

data services at least one keyword from the "Classification of Spatial data Services" (Part D.4

from INS MD] shall be provided.

Prerequisites

A.03.IR05.schema.validation A.05.IR07.extended.capabilities.elements.node A.13.IR18.keywords.node

Test method

Check that there exists at least one MandatoryKeyword element containing one of the

keywords listed in IR MD, Part D, 4.Classification of Spatial data Services (the

lowerCamelCase terms in parenthesis).

Reference(s)

TG VS, chapter 4.2.3.3.1.7 Keyword IR MD, Annex, Part B.3 Keyword


Notes




MandatoryKeyword /wms:WMS_Capabilities/wms:Capability/inspire_vs:ExtendedCapabilities[1]

/inspire_common:MandatoryKeyword


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.05.IR07.extended.capabilities.elements.node.md


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.39.IR16.spatial.data.service.keyword.embedded.metadata.md#ext-mandatory-keyword





50

A.40.IR67.IR68.language.affects.capabilitie

s

Purpose: The user must be able to select one of the supported languages. This language

selection must be reflected in the provided capabilities document.

Prerequisites

A.03.IR05.schema.validation A.06.IR08.language.node

Test method

Let the value of GetCapabilities OnlineResource be getcapabilities-url. For each SupportedLanguage codes as lang-code:

o Create a GetCapabilities HTTP request by adding the parameters SERVICE=WMS, REQUEST=GetCapabilities, VERSION=1.3.0 and LANGUAGE= + lang-code to the getcapabilities-url

o Execute the request. If the returned resource can be parsed as a valid XML document and if the document passes tests A.03.IR05.schema.validation and A.06.IR08.language.node:

Check that the ResponseLanguage code equals the lang-code. If it does not, fail the test for this language.

o Otherwise fail the test. If the test for any of the languages failed, fail the test. Otherwise pass the test.

Reference(s):

TG VS, chapter 4.3.1 TG MD, chapter 2.2.7


Notes




SupportedLanguage

codes

/wms:WMS_Capabilities/wms:Capability/inspire_vs:ExtendedCapabilities[1]/

inspire_common:SupportedLanguages/inspire_common:SupportedLanguage

/inspire_common:Language

ResponseLanguage

code

/wms:WMS_Capabilities/wms:Capability/inspire_vs:ExtendedCapabilities[1]/

inspire_common:ResponseLanguage/inspire_common:Language



https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.40.IR67.IR68.language.affects.capabilities.md#getcap-href

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.40.IR67.IR68.language.affects.capabilities.md#supported-languages



https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.40.IR67.IR68.language.affects.capabilities.md#response-language


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/README.md#ref_TG_MD


51


GetCapabilities

OnlineResource

/wms:WMS_Capabilities/wms:Capability/wms:Request/wms:GetCapabilities

/wms:DCPType/wms:HTTP/(wms:Get|wms:Post)[1]/wms:OnlineResource/@

xlink:href

52

A.41.IR69.default.language

Purpose: The default language for the service must be provided in order the user to be able to

know which language can be expected to be used if the capabilities document when no

language is explicitly requested.

Prerequisites

A.03.IR05.schema.validation A.06.IR08.language.node

Test method

Let the value of GetCapabilities OnlineResource be getcapabilities-url. Let the DefaultLanguage code be lang-code. Create a GetCapabilities HTTP request by adding the parameters SERVICE=WMS,

REQUEST=GetCapabilities, VERSION=1.3.0 to the getcapabilities-url. Execute the request. If the returned resource can be parsed as a valid XML document and if

the document passes tests A.03.IR05.schema.validation and A.06.IR08.language.node: o Check that the ResponseLanguage code equals the lang-code. If it does pass the

test. Otherwise fail the test.

Reference(s):

TG VS, chapter 4.3.1 TG MD, chapter 2.2.7


Notes




DefaultLanguage

code

/wms:WMS_Capabilities/wms:Capability/inspire_vs:ExtendedCapabilities[1]/i

nspire_common:SupportedLanguages/inspire_common:DefaultLanguage/ins

pire_common:Language

ResponseLanguage

code

/wms:WMS_Capabilities/wms:Capability/inspire_vs:ExtendedCapabilities[1]/i

nspire_common:ResponseLanguage/inspire_common:Language

GetCapabilities

OnlineResource

/wms:WMS_Capabilities/wms:Capability/wms:Request/wms:GetCapabilities/

wms:DCPType/wms:HTTP/(wms:Get|wms:Post)[1]/wms:OnlineResource/@x

link:href



https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.41.IR69.default.language.md#getcap-href

https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.41.IR69.default.language.md#default-language



https://github.com/inspire-eu-validation/ats-view-wms/blob/master/A.41.IR69.default.language.md#response-language


https://github.com/inspire-eu-validation/ats-view-wms/blob/master/README.md#ref_TG_MD


53

Documents

Abstract Test Suite for View Services Table of Contents · PDF fileAbstract Test Suite for View Services Abstract Test Suite for INSPIRE View Services Technical Guidance ISO 19128