Page tree

Monday, 15 December 2014, 14:30 - 16:30 CET

Connection details


Agenda

14:30 - 14:45 Welcome and Tour de table

14:45 - 15:00 MIWP-6 Overview (Michael Lutz) [Slides: 20141215_MIWP-6_kick-off.pptx]

  • Objectives
  • Tasks
  • Outcomes

15:00 - 15:15 Overview on registry federation study (Andreas von Doemming, Florian Esser)

15:15 - 15:30 New release of INSPIRE registry and Re3gistry software (Daniele Francioli, Emanuela Epure) [Slides: 20141215_Re3gistry_rc1.0_INSPIRE_registry_rc5.ppt]

  • New features and content
  • Testing period

15:30 - 16:00 Work plan (Michael Lutz)

  • Task participants / leads
  • Timing and dependencies

16:00 - 16:15 Working methods

  • Meeting frequency
  • Tools

16:15 - 16:30 AOB


Draft Minutes


Attendees

  • MIWP-6 sub-group members: Alejandra Sánchez, Anders Foureaux, Andreas von Dömming, Chris Schubert, Christian Ansorge, Christine Laaboudie, Clément JAQUEMET, Esa Tiainen, Jeremy Tandy, Magnus Karge, Martin Tuchyna, Michael Lutz, Norbert Pfaffinger, Tõnis Kärdi, Willem van Gemert, Wolfgang Tinkl
  • Other attendees: Daniele Francioli, Emanuela Epure, Vanda Nunes de Lima, Heidi Vanparys, Hannes Reuter, Marcus walther


Welcome and Tour de table

All participants shortly introduced themselves and stated their experience and interest for participating in the sub-group.

See the table Sub-group_MIWP-6_members.xlsx for an overview of all members of the sub-group.


MIWP-6 Overview

Michael gave an overview of the proposed tasks and outcomes of the sub-group [Slides: 20141215_MIWP-6_kick-off.pptx].

Wolfgang asked whether there will there be QoS requirements for the registry services in the member states. Michael said that there are no obligations (since registry services do not fall under the NS IRs), but that this could be recommended in the Guidelines to be drafted by the group (if deemed necessary/useful).

Wolfgang asked whether there is a legal background for Technical Guidelines for registers and registries. Michael said that the only obligation for registers is the obligation in the IRs for interoperability of spatial data sets and services to publish extended code list values in some kind of register (Art. 6(3)).

Martin asked whether there is no any link to invoke/spatial data services. Michael will investigate and clarify this in the next meeting.


Overview on registry federation study

Andreas presented the scope and preliminary results of the registry federation study [Slides: ...]. More details are available on the wiki page of the webinar given on 26/11/2014. The study results will be made available to the sub-group (and possibly the public) in January.

In the scope of study on an INSPIRE registry federation, a webinar was organised to present intermediate results. [Slides presented at INSPIRE registry federation webinar]

The study aims at 

  • Collecting and organising reference material on existing national registry implementations and requirements for an INSPIRE registry federation from selected Member States and EU institutions and bodies;
  • Preparing a report proposing:
    • An architecture for an INSPIRE registry federation including the central INSPIRE registry/registers, registries/registers in the Member States (at national and sub-national level) and the proposed registry of registries. The architecture shall allow registries/registers to be connected to each other and to access and make available each other’s content.
    • Metadata elements for describing registries/registers, taking into account relevant international standards, where appropriate.
    • A core API and exchange format(s) for querying and exchanging register content between registries inside the federation, taking into account existing standards and initiatives and widely used encodings (e.g. RDF, XML or CSV).
    • A concept (methods, procedures etc.) and conceptual data model for modelling national, local or community extensions of INSPIRE registers.
    • A set-up for a testbed for implementing the proposed registry federation with several Member States.
    • Recommendations for missing features or functionalities of the central INSPIRE registry.


New release of INSPIRE registry and Re3gistry software

Daniele and Chris presented the new candidate release of the Re3gistry software (v1.0rc) and of the INSPIRE registry service (rc5) [Slides: 20141215_Re3gistry_rc1.0_INSPIRE_registry_rc5.ppt]. The main new features are a simplified registry data management interface (Re3gistry) and the addition of the recommended code list values from the TGs.

A testing period will run until 23 January - details are available on the registry development and testing wiki.

Alejandra asked whose responsability it is to create the data input (each point of contact of each country?) and where the structure for uploading data is available. Michael clarified that there are no plans to include MS registers or register extensions in the central INSPIRE registry, but that the Re3gistry software can be used to set up national registers. Empty CSV templates providing the required structure are available in the software. This can be tried out in the testing sandbox.

Christian asked whether the new release will support RDF/XML. Michael clarified that this is already available in the current stable release.

Wolfgang asked whether there will there be QoS requirements for the registry services in the member states. Michael said that there are no obligations (since registry services do not fall under the NS IRs), but that this could be recommended in the Guidelines to be drafted by the group (if deemed necessary/useful).


Work plan

The following overall approach for the workplan was agreed.

The rough timing should be as follows:

  • TG v1: Feb-May 2015
  • TG v2: Oct-Dec 2015
  • Testbed set-up: Jan-Apr 2015
  • Use cases: Jan-Feb 2015
  • Testbed v1:May-Sep 2015
  • Testbed v2: Nov 2015 ??

It was agreed to propose a workshop for the INSPIRE/GWF conference (in addition to a short presentation in the MIG-T session presenting the status of the active MIWP actions). This workshop would ensure feedback from the INSPIRE community, but also other participants outside of the INSPIRE community. The workshop could present the testbed set up, but could also be used to give participants some hands-on experience with existing tools like the UK LD registry and the Re3gistry implementations.

All participants were asked to indicate how they would like to contribute to the work of the sub-group. See ta

RoleLeadParticipation
Overall sub-group lead

Testbed coordination/set-up
Jeremy Tandy
Testbed participation
EEA, Norbert Pfaffinger, Martin Tuchyna, Magnus Karge, Andreas von Dömming, Tõnis Kärdi, Jeremy Tandy, Clément Jaquemet, Marcus Walther, Esa Tiainen (?)
TG editor

TG contributor
EEA, Wolfgang Tinkl, Norbert Pfaffinger, Martin Tuchyna, Andreas von Dömming, Esa Tiainen, Jeremy Tandy
Reviewer
Wolfgang Tinkl, Norbert Pfaffinger (if needed), Magnus Karge, Clément Jaquemet
INSPIRE registry & Re3gistry development & testingJRC registry teamMartin Tuchyna, Jeremy Tandy (?)
Use cases
Wolfgang Tinkl, Magnus Karge, Anders Foureaux, EEA, Martin Tuchyna, Norbert Pfaffinger, Tõnis Kärdi, Marcus Walther


Working methods

It was agreed to have a web meeting once per month intially. A doodle will be set up for the meetings. If a preferred date emerges, we may move to a regular slot.

A physical meeting is not planned at the moment, but those members of the sub-group attending the INSPIRE conference could meet up for an informal meeting there.

The work (including the Technical Guidelines) will be documented using the wiki and issue tracker of the MIG collaboration platform. Michael reminded everyone to register on  at https://ies-svn.jrc.ec.europa.eu/account/register to get write access.


AOB

Magnus suggested to send presentations and links around before meetings.

  • No labels