AIP-2 Development

Development of AIP-2 began with the completion of the Kickoff Workshop.    AIP-2 Participants are now developing best practices, deploying services and components, testing interoperability, and developing integrated results.  The key outcome of the pilot initiative will be persistent, operational exemplars and demonstrations of the exemplars.  The AIP Development process is defined in the AIP-2 Call for Participation .

• AIP-2 Working Groups
• Cross-WG topics
• AIP-2 Milestones and Schedule
• Transition to Operations
• Persistent Exemplars
• Engineering Reports
• Communications : e-mail, web pages, telecons

AIP-2 Development will be conducted in the AIP-2 Working Groups:

Results for each Working Group are linked to the corresponding workspace below. Day-to-day development collaboration will be carried out in draft fashion on google sites.   Cross-WG topics are also being addressed.

Leaders of the Working Groups.

• Disaster Response: Stuart Frye, NASA; Didier Giacobbo, Spot Image;
• Air Quality:  David McCabe,Frank Lindsay, Stefan Falke, Rudy Husar ESIP AQ Team
• Biodiversity and Climate: Stefano Nativi, CNR; Gary Geller, NASA-JPL
• Energy SBA:  Thierry Ranchin and Lionel Menard, Mines Paris Tech; Ellsworth LeDrew, Univ Waterloo

• Catalogues, Clearinghouse, Metadata, Registry: Doug Nebert, USGS; Josh Lieberman OGC/Traverse; Kengo Aizawa, JAXA; Ted haberman, NOAA
• Access Services-Products, Sensors, Models :  Hervé Caumont, ERDAS/OGC; Glenn Rutledge, NOAA; Hans Peter Plag, UNR; Anwar Vahed, CSIR, Luis Bermudez, SURA
• Workflow and alerts: Satoshi Sekiguchi, AIST; Greg Yetman, CIESIN; Eugene Yu, GMU
• Clients: portals and application clients: Nadine Alameh, OGC/MobileAps;
• Test Facility for service registration: Mauro Semarano, ESA

Responsibilities of the Working Group leaders are:

• lead the Working Group toward achieving the objectives of GEOSS
• collaborate with the other AIP-2 Participants in the WG to accomplish the following:
• define a plan for the working group including deliverables and schedule
• utilize the AIP collaboration resources for WG activities
• accomplish the WG deliverables in support of the overall AIP-2 plan
• track the progress of the WG toward the agreed plan
• report the status of the WG to the AIP Plenary telecon and to other GEOSS venues

 AIP-2 Development milestones and schedule

Initial list of items to transition to operations

A goal of AIP-2 is to augment the Initial Operating Capability (IOC) of GEOSS.  The main elements of the GEOSS IOC are contained in the GEOSS Common Infrastructure, e.g., GEO Web Portals, Registries and Clearinghouse.   AIP-2 aims to augment the IOC with peristent exemplars.  A defintion of "operational persistentence" is provided in the AIP-2 CFP, Annex B, Clause 6.2 and listed below.

An inital list of potential AIP-2 components to augment the IOC are:

• Community portals
• Community catalogues
• Operational access services 

Note that not all development of AIP-2 is focused on augmenting the IOC.  Some AIP-2 development aims to demonstrate the of approaches suitable for GEOSS, such that they can be recommended for GEOSS Interoperability Arrangements.  Such recommendations would be in the AIP-2 Engineering Reports.

AIP-2 Engineering Reports

Each WG should consider how to document their results at the end of the AIP-2.  It is recommended that each WG develop an Engineering Report (ER) that documents that conclusions, agreements, recommendations for their topic area.  The AIP-2 ERs may then be posted to the GEOSS Best Practice Registry Wiki .    For example the Metadata WG ER would include agreements on metadata and would include metadata example schemas.  The Access Services WG ER would contain agreements on services and examples of services that have been registered and tested with clients for binding.  SBA working groups need to develop scenarios and enterprise view models which could be documented in an ER. The SBA ER's would also map the scenarios to services.

The development of Scenarios and Use Cases is described on this page . 

A template for an AIP-2 ER will be developed and posted here.

• ERs for Community WGs include: enterprise description of the community; scenarios including detailed steps; components and services to support the scenario. 
• ERs for Transverse Technology WGs include: use case for the services; candidate Interoperability Arrangements; examples

A Test Facility ER has been drafted and can serve as an example.

Communication Plan

• Telecons
• AIP Plenary Telecon - Tuesdays
• Alternating topics: SBAs and Trans Tech
• Beginning 30 September
• WG telecons as defined by WG leaders
• E-mail list-servers
• AIP Plenary e-mail list sign-up page
  
• The point of contact for each AIP-2 Participant should send the link to the plenary sign-up page to the persons in their organization.
• One list per work group have been established.
• WG leaders asked OGC to set up the lists.
• Collaborative Workspaces
• Status page for each workgroup - see links in table above
• This page is to provide a WG Summary.
• All of these pages to have a uniform look and would be more stable for external readers.
• Contains a link to the Working Group collaboration workspace
• Working Group Collaboration spaces for AIP-2 on Google Sites.
• dynamic workspace suited to the working groups day-to-day needs