agenda session (75 minutes duration, friday sessions are 90 minutes) co-lead introduces the session...

14
Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) repeat of one chart from opening plenary list of responses relevant to session Self introductions of persons in the session (10 minutes) Presentations by several primary participants (30 minutes) identify what problem are you solving emphasis on the end-to-end use case: publish, find, bind, workflow, decision listing of services and data contributions Open Discussion (20 minutes) For technology sessions: Interactive discussion of design and interoperability arrangements Develop a work plan for the topic: dates and actions (10 minutes) Review and comment on AIP-2 Master Schedule identify session specific milestones What is missing and still needed: service and data gaps What would result in a paradigm shift to meeting our objectives rather than a simple evolutionary path.

Upload: owen-purcell

Post on 27-Mar-2015

215 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

Agenda

• Session (75 minutes duration, Friday sessions are 90 minutes) • Co-lead introduces the session (5 minutes)

– repeat of one chart from opening plenary – list of responses relevant to session

• Self introductions of persons in the session (10 minutes) • Presentations by several primary participants (30 minutes)

– identify what problem are you solving – emphasis on the end-to-end use case: publish, find, bind, workflow, decision – listing of services and data contributions

• Open Discussion (20 minutes) – For technology sessions: Interactive discussion of design and interoperability

arrangements • Develop a work plan for the topic: dates and actions (10 minutes)

– Review and comment on AIP-2 Master Schedule – identify session specific milestones – What is missing and still needed: service and data gaps – What would result in a paradigm shift to meeting our objectives rather than a simple

evolutionary path.

Page 2: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

Test Facility for Service Registration

• Primary Participants: BKG, ESA, USGS • Contributing Participants: CIESIN, ICT4EO • Topics

– ESA SSE - Workflow, Conformance Testing and Test Environment: WMS, WFS, WCS, GML/SLD, CSW

– ESA SSE - Dedicated test clients (catalogue, ordering and programming interfaces).

– USGS Geospatial web service status facility for testing standards-based services at the time of registration and elsewhere in the operational lifecycle.

– USGS At present, testing of the OGC WMS and ArcIMS image services; WFS and WCS in the coming months

– BKG Catalog-test based on OGC's TEAM engine for interoperability testing – CIESIN offers support for testing of service chaining and interoperability

arrangements for WPS – Usability testing / recommendations for IOC

Page 3: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

Test Facility for Service Registration

• Co-leads: Jolyon Martin, Doug Nebert

• Primary Participants: BKG, ESA, USGS

• 11 participants in the session• Topics

– Conformance test– Persistent testbed– Operations testing

• Results: Testing resources identified• Action: Register the URLs of the test

interfaces• Action: Create a proxy view for

service testing endpoint

Page 4: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

GEO AIP-2 Kickoff

Persistent Testbed

Page 5: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

Service Support Environment (SSE)

• Service-oriented architecture;

• Business process management platform;

• Use of Open standards (W3C, OASIS, WSI OGC);

• Orchestration of synchronous and asynchronous Web Services;

• Integration of the EO data access within the prototyping and delivering of the services;

• Integration of multiple domains data within the processing and exploitation chains;

• Support of service evolution and maintenance.

http://services.eoportal.org/

Page 6: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

SSE

• Forums

• Wikis

• Blogs

The SSE Portal provides an area to share ideas and competencies:

Page 7: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

Tools

• Scenario and service prototyping support tools

– SSE Toolbox:conversion of any legacy service in a SOA based one (in progress the update with the Buddata ebXML Registry, OMAR EbRR)

– Workflow Editor :creation of complex workflows and chaining services through an orchestration engine (BPEL based)

Page 8: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

Tools

• Test and conformance testing Tools

– SSE Client (supporting, WMS, WFS, WCS, SOS)

– Generic SOAP Test Client

– Test Skeleton (Client + Server)

– Accessibility Test (WMS,WFS,WCS)

– GML/SLD Tester

– OGC Compliance Tests

Page 9: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

SSE Client (supporting, CSW, WMS, WFS, WCS, SOS)

Page 10: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

Generic SOAP Test Client

Low level testing of the SOAP requests and responses for the specific service

Page 11: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

Test Skeleton

Test Client

Test Server

Page 12: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

Test Server

– Catalogue - OGC 06-131

– Ordering - OGC 06-141

– Programming - OGC 07-018

HMA ICDs simulations:

Page 13: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

OGC Compliance Tests

• Referenced to CITE environment by Open Geospatial Consortium (OGC)

• Compliance Test Language (CTL) as script language OGC 06-126

• Test, Evaluation, And Measurement (TEAM) Engine updated with SOAP support as test script interpreter

Page 14: Agenda Session (75 minutes duration, Friday sessions are 90 minutes) Co-lead introduces the session (5 minutes) –repeat of one chart from opening plenary

OGC Compliance Tests – (in progress)

• Reference Implementations:– HMA-T project schedules to provide reference

implementations for the following HMA interfaces:

– HMA Catalogue Protocol (EO ext package) OGC 06-131

– HMA Catalogue protocol (CIM ext package) OGC 07-038

– HMA User Management protocols OGC 07-118

– HMA Ordering protocols OGC 06-141

– HMA Programming protocols OGC 07-018

– OGC 07-063 WMS Profile for Earth Observation

• CITE conformance test scripts :– HMA Catalogue Protocol (EO ext package) OGC 06-131

– HMA Catalogue protocol (CIM ext package) OGC 07-038

– HMA User Management protocols OGC 07-118