1. Understanding resource coupling CSW 2.0.2 Kristian Senkler 29.05.2015

2. Three questions: Which datasets are provided by a service? Which service provides access to a dataset? By the means of which operation does a service operate on a dataset?

3. Which datasets are provided by a service? CSW INSPIRE Service Dataset (foo:1)Dataset (foo:2)Dataset (foo:3)

4. Which service provides access to a dataset? 2 foo CSW.Discovery -> operatesOnIdentifier (2) Dataset (foo:2) Service_1Service_2

5. Which service provides access to a dataset? foo:2 CSW.Discovery  operatesOnIdentifier (foo:2) Dataset (foo:2) Service_1Service_2

6. By the means of which operation does a service operate on a dataset? Transaction 1 streets coupledResource maps identifier  layer name ISO 19115  OGC Capabilities OGC WFS GetFeature (foo:1) Transaction (foo:2)

7. Solution (technical) Assumptions 1.INSPIRE targets only the first two questions (service -> dataset) (dataset -> service) 2.INSPIRE uses URIs for resource identification 3.INSPIRE declares HTTP Get for CSW.Discovery GetRecords operation obligatory (whereas 3. is optional)

8. Solution (technical) Use existing xlink to realize the relationship Important aspects: The first requires subsequent queries to resolve the relationship; The second yields a GetRecordsResponse document; The second helps to link resources provided by different hosts. Does not fit to CSW ISO AP, Annex F (informative anyway);

9. Solution (technical) Compliance with CSW 2.0.2 still possible: Important aspects: Still not compatible with ISO 19118; Relation only resolvable by using subsequent queries;

10. Requirements of the directive 1.6. Coupled resource If the resource is a spatial data service, this metadata element identifies, where relevant, the target spatial data set(s) of the service through their unique resource identifiers (URI). […] Strictly speaking, only the direction service  dataset is relevant. Pure CSW AP ISO using uuidref is sufficient.