Ambiguities in the Implementation of the INSPIRE directive for Metadata. J.Walther, F.Schenk

Transcription

1 Ambiguities in the Implementation of the INSPIRE directive for Metadata J.Walther, F.Schenk

2 Errors and Ambiguities e.g. UseLimitation INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO and EN ISO 19119: restrictions on the access and use of a resource or metadata ISO 19115: limitation affecting the fitness for use of the resource or metadata. Example, not to be used for navigation more suitable: useconstraints constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations or warnings on using the resource or metadata

3 INSPIRE and Metadata Foundations Implementing Directive 2007/2/EC INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO and EN ISO 19119

4 INSPIRE and Metadata Principles 1. finding data / services: discovery services 2. using data requires finding services (download or view services)

5 Typical SDI Topology decentralised discovery infrastructure limited (thematic) coverage of individual discovery services (e.g. federal states, nation, themes) duplication (harvesting) of metadata

6 INSPIRE Portal Geodatenkatalog.de catalogues of fed. government department-specific catalogues catalogues of federal states further catalogues department-specific catalogues communal catalogues further catalogues

7 Use case 1: use discovery service to find relevant data select data find appropriate (coupled) view service visualize data

8 Dataset: ATKIS-Basis-DLM NRW

9 Service:

10 <gmd:md_identifier> <gmd:code> <gco:characterstring> </gco:characterstring> </gmd:code> </gmd:md_identifier> Dataset Metadata Resource Identifier Service Metadata <srv:operateson uuidref=" xlink:href=

11 Legal Background Metadata implementing directive

12 Background - TG

13 <gmd:md_identifier> <gmd:code> <gco:characterstring> </gco:characterstring> </gmd:code> </gmd:md_identifier> CSW-Queryable operateson Service Metadata operateson DENWAT01 <gmd:rs_identifier> <gmd:code> <gco:characterstring> DENWAT01 </gco:characterstring> </gmd:code> <gmd:codespace> <gco:characterstring> </gco:characterstring> </gmd:codespace> </gmd:rs_identifier>

14 Use case 2: use discovery service to find relevant view services the service operates on one or more datasets: find the descriptions of those datasets

15 URL vs URI: Two Different Interpretations <srv:operateson uuidref=" xlink:href= Service Metadata URL? URI?

16 iso / gmd schema (xlink:href -> xsd:anyuri) The type xsd:anyuri represents a Uniform Resource Identifier (URI) reference. [...] URIs are not required to be dereferencable; that is, it is not necessary for there to be a web page at in order for this to be a valid URI. xlink-specification The value of the href attribute must be a URI reference as defined in [IETF RFC 2396], or must result in a URI reference after the escaping procedure described below is applied. The procedure is applied when passing the URI reference to a URI resolver.

17 dereferenceable URIs are cool...but not always present... only useful in stable environments (e.g. if registries are already available)

18 URL vs URI: Two Different Interpretations <srv:operateson uuidref=" xlink:href= URL Service Metadata URI Discovery Service Dataset Metadata Dataset Metadata

19 Interoperability needs the cosideration of different variants in Workflows / SDIs Validation services Use registries, as soon as they are available!