Purpose:
The OpenSearch description must contain a "Url" element that describes a template URL for the Get Spatial Data Set operation. This template must accept the INSPIRE parameters "crs", "spatial_dataset_identifier_code", "spatial_dataset_identifier_namespace" and the OpenSearch "language" parameter. The "Url" element must have an attribute "type" with a value corresponding to the media type of the result and an attribute "rel" with the value "results".
Test method
- test if the OpenSearch Description provides at least one Get Spatial Dataset url
- for each Get Spatial Dataset url, fill in the parameters for "crs", "spatial_dataset_identifier_code", "spatial_dataset_identifier_namespace" and "language" and resolve the Get Spatial Dataset url
- test if the HTTP response of the previous step has the same content-type as the media-type of the Get Spatial Dataset url
Reference(s):
- IR NS, M1, section 3 (3.1-3.2.1)
- TG DL, Req 43
- OpenSearch
Test type:
Automated
Notes
[1] The values for the parameters "crs", "spatial_dataset_identifier_code", "spatial_dataset_identifier_namespace" and "language" can be obtained from the OpenSearch description
Comment to the TG: The Get Spatial Data Set operation implementation as OpenSearch query feels strange and unnecessary: The Dataset Feed + HTTP requests for the dataset content (requirements 26 - 34) already implement the Get Spatial Data Set operation. Also the semantics of Open Search queries is that they should return a list of search hits (entries), not the actual data contents.
The namespace prefixes used as described in README.md.