search

inspire-eu-validation / discovery-service

Abstract Test Suite for the Technical Guidance for INSPIRE Discovery Services
Creative Commons Zero v1.0 Universal
0 stars 0 forks source link

A.02.07.federated.discovery.service #40

Closed jensscheerlinck closed 8 years ago

jensscheerlinck commented 8 years ago

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685

Comment

XPATH expression is missing

Proposed Change

Add XPATH reference

PeterParslow commented 8 years ago

This has two pre-requisites that cannot be tested automatically:

  1. the operator of the system under test (probably a Member State) has chosen to implement the federated search option for the Link Discovery Service operation
  2. there are in fact other Discovery Services registered in the service under test (with the intention of federating the search to them) Only then does Requirement 16 apply The XPath at which one would then find the linked service advertised is as described in the TG text above the requirement (by reference to OGC CSW ISO AP 10.8..4.13): /ows:OperationsMetadata/ows:Constraint[@name="FederatedCatalogues"/ows:Value - and the service at that URL should pass all the tests!
cportele commented 8 years ago

Then the test type should be changed to "Manual".

Or a new conformance class needs to be introducted in the TG for the federated search option, but that requires an update to the TG first, so not an option for now.

PeterParslow commented 8 years ago

Reading further in TG section 4.3.4.2, the service operator can publish the details in this way (in this section of the GetCapabilities response) even if he has adopted the 'discovery client approach' as an option, instead of 'federated search'. Arguably, this makes no difference to conformance testing. Agree: set to 'manual'