Ambiguities in the Implementation of the INSPIRE directive for Metadata J.Walther, F.Schenk
Errors and Ambiguities e.g. UseLimitation INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 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
INSPIRE and Metadata Foundations Implementing Directive 2007/2/EC INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119
INSPIRE and Metadata Principles 1. finding data / services: discovery services 2. using data requires finding services (download or view services)
Typical SDI Topology decentralised discovery infrastructure limited (thematic) coverage of individual discovery services (e.g. federal states, nation, themes) duplication (harvesting) of metadata
INSPIRE Portal Geodatenkatalog.de catalogues of fed. government department-specific catalogues catalogues of federal states further catalogues department-specific catalogues communal catalogues further catalogues
Use case 1: use discovery service to find relevant data select data find appropriate (coupled) view service visualize data
Dataset: ATKIS-Basis-DLM NRW
Service: http://www.wms.nrw.de/geobasis/wms_nw_dtk100?
<gmd:md_identifier> <gmd:code> <gco:characterstring>http://geoportal.nrw.de#denwat01 </gco:characterstring> </gmd:code> </gmd:md_identifier> Dataset Metadata Resource Identifier Service Metadata <srv:operateson uuidref="www.geoportal.nrw.de#denwat01" xlink:href= http://geoportal.nrw.de#denwat01"/>
Legal Background Metadata implementing directive
Background - TG
<gmd:md_identifier> <gmd:code> <gco:characterstring> http://geoportal.nrw.de#denwat01 </gco:characterstring> </gmd:code> </gmd:md_identifier> CSW-Queryable operateson Service Metadata operateson http://geoportal.nrw.de# DENWAT01 <gmd:rs_identifier> <gmd:code> <gco:characterstring> DENWAT01 </gco:characterstring> </gmd:code> <gmd:codespace> <gco:characterstring> http://geoportal.nrw.de# </gco:characterstring> </gmd:codespace> </gmd:rs_identifier>
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
URL vs URI: Two Different Interpretations <srv:operateson uuidref="www.geoportal.nrw.de#denwat01" xlink:href= http://geoportal.nrw.de#denwat01"/> Service Metadata URL? URI?
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 http://datypic.com/prod.html 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.
dereferenceable URIs are cool...but not always present... only useful in stable environments (e.g. if registries are already available)
URL vs URI: Two Different Interpretations <srv:operateson uuidref="www.geoportal.nrw.de#denwat01" xlink:href= http://geoportal.nrw.de#denwat01"/> URL Service Metadata URI Discovery Service Dataset Metadata Dataset Metadata
Interoperability needs the cosideration of different variants in Workflows / SDIs Validation services Use registries, as soon as they are available!