GEOSS Interoperability Workshop Lessons learned: GIGAS Stefano Nativi (CNR & GIGAS) IEEE-USA...

GEOSS Interoperability Workshop

Lessons learned: GIGAS

Stefano Nativi (CNR & GIGAS)

IEEE-USA Headquarters, Suite 7002001 L Street, NWWashington, D.C. 20036

12 & 13 November 2009

[email protected]

Outline

• GIGAS Project

• SIF European Team

• GIGAS interoperability achievements:

– Recognized obstacles

– Recommendations

© 2008 GIGAS Consortium http://www.thegigasforum.eu

Promotes the coherent and interoperable development of the GMES, INSPIRE and GEOSS initiatives through their concerted adoption of standards, protocols, and open architectures

Start date: June 2008 End date: May 2010

GIGAS - GEOSS, INSPIRE, and GMES an Action in Support

Website: http://www.thegigasforum.eu

SIF European Regional Team Implementation

GIGAS helped to constitute the Team

This objective is in the scope of the project

The SIF European Team is implemented in two phases:

1. A starting and preparatory phase;

2. A regime phase.

Structure and Roles

Sector Experts

discuss the Regional

Team positions

carry out

the tasks assigned by SIF

Lead

The lead serves as the regional representative on the SIF

Executive Committee

The Executive Committee supports the lead

The committee may be structured in secretaries

SIF European Team

Web Site

http://www.thegigasforum.eu/sif/

Executive Committee

ESA, JRC, Fraunhofer

Pro-tempore Lead

Stefano Nativi

GIGAS committment

GIGAS has devoted a specific task to

explicitly set-up the European SIF team

foster the sustainability of the European SIF team beyond the GIGAS project duration

promote the participation of European actors outside GIGAS to the European SIF

promote the registration of, European or not, standards used by INSPIRE and GMES

promote the registration of, European or not, standards used by FP7 projects

GIGAS INTEROPERABILITY ACHIEVEMENTS

The Approach

Four subsequent steps:

monitoring, comparison, discussion & consensus, and influence &

shape.

This process will be iterated twice in the course of the

project (loop1 and loop2).

Recommendations are made towards the converging

requirements for recognized interoperability obstacles

The Approach

The following set of thematic areas or themes has been

addressed:

Architecture

Cross-initiatives scenario deployment plan

Catalogue, meta-data and discovery

Data access and processing

Data harmonisation and semantic interoperability

User management

The Approach


1. Analysis

2.2. Comparison and Comparison and

RecommeandationsRecommeandations

3. Discussion & consensus

4. Influence

ArchitectureGIGAS Methodology for Technology Watch and Comparative Analysis

The architecture technology watch yielded identified issues rather than recommendations

To Whom (actor) Identified issue

GIGASGIGAS +Possible future involvement of working groups of INSPIRE, GEOSS and GMESINSPIRE, GEOSS and GMES

Requirements forRequirements for architectural architectural coherence andcoherence and cross-initiative cross-initiative interoperability unclearinteroperability unclear

GIGASGIGAS + Possible future involvement of working groups of GMES and FP6/7GMES and FP6/7 projects

GMES and FP7 projects seem to have less emphasis on standards-less emphasis on standards-based architecturebased architecture as compared to GEOSS and INSPIRE

GIGASGIGAS + Possible future involvement of working groups of INSPIRE, GEOSS and GMESINSPIRE, GEOSS and GMES

Need to address the topic of Need to address the topic of semantic interoperabilitysemantic interoperability across across initiatives with initiatives with prioritypriority

Catalogue, metadata and discovery

To Whom (actor) Recommendation (action)

GIGASGIGAS in collaboration with the responsible working groups of INSPIREINSPIRE, GEOSSGEOSS and GMESGMES

Design joint cross-initiative joint cross-initiative scenarios for resource discovery scenarios for resource discovery

INSPIREINSPIRE, GEOSSGEOSS and GMESGMES technical teams

Elaborate a set of core queryable core queryable metadata elementsmetadata elements


Analyze service descriptionsservice descriptions




• Reach interoperability between catalogue interoperability between catalogue service solutions

• Better fulfill discovery requirementsfulfill discovery requirements• Short-term step: extend the CIM package extend the CIM package to

make it interoperable with the INSPIRE ISO Application Profile of CS-W

• Longer-term step: set up ebRIM extension set up ebRIM extension packagespackages for metadata discovery reflecting its own user view on metadata

Catalogue, metadata and discoveryTo Whom (actor) Recommendation (action)


Provide standardized access to other types standardized access to other types of geographic resourcesof geographic resources, through standardized ebRIM extension packages:

• Feature catalogues;• Application schemas;• Geodetic codes and parameters• Portrayal information• Feature concept dictionaries, thesauri,

glossaries and other registers of terms• Data quality measures• Ontologies• Code lists• Object identifier namespaces• Units• Data specifications• Encoding schemas




Consider the use of the OASIS RegRep OASIS RegRep standard standard and/or the OGC RegRep profileOGC RegRep profile

Data Access and Processing


OGCOGC, ISO/TC211ISO/TC211and CEN TC287 CEN TC287

Support SOAP/HTTP-POST binding SOAP/HTTP-POST binding according to INSPIRE IR, in addition to KVP/HTTP-GET bindingKVP/HTTP-GET binding

OGC OGC OWS Common 1.2 SWG

Evaluate the opportunity to support asupport a language parameter to set the natural language parameter to set the natural languagelanguage used for request and response

INSPIRE INSPIRE Network Services Drafting Team

Support metadataURL metadataURL that would point on to "ISO 19115:2003ISO 19115:2003" or "FGDC:1998FGDC:1998" metadata typemetadata type



INSPIREINSPIRE Consolidation Team

Include actual O&M standard O&M standard in the INSPIRE Generic Conceptual Model

GMESGMES Fast-Track Service Projects

Adopt O&M-based information models and O&M-based information models and servicesservices

GEOSSGEOSS SIF Endorse the O&M standardO&M standard

GEOSSGEOSS ADC Adopt a framework based on O&Mframework based on O&M

Second LoopGIGAS has been working on the second loop of analysis.

New recommendations will be released before the end of 2009

The analyzed topics are the same of the first loop:

Architecture

Cross-initiatives scenario deployment plan

Catalogue, meta-data and discovery

Data access and processing


User management

OutlookGIGAS runs until mid 2010 as a project

GIGAS Business model and exploitation plan identifies measures needed to make GIGAS sustainable

Continue to improve the bi-directional communication with stakeholders

Embed GIGAS elements in existing forums

Identify “champions” that take willing to continue activities and maintain GIGAS-initiated activities

Identify elements that would require further funding

THANK YOU !


Please, register to the SIF European Team Wiki site !Please, register to the SIF European Team Wiki site !


Please, register to the SIF European Team Wiki site !Please, register to the SIF European Team Wiki site !


GEOSS Interoperability Workshop Lessons learned: GIGAS Stefano Nativi (CNR & GIGAS) IEEE-USA...

Documents

Transcript of GEOSS Interoperability Workshop Lessons learned: GIGAS Stefano Nativi (CNR & GIGAS) IEEE-USA...