GEOSS AIP Pilot - Initial Scenario

GEOSS Architecture Implementation Pilot: Template

(This page is currently a template provided by GEOSS-OGC that will be completed. )

If you have a position paper on this session either send your position paper to George Percivall and it will be posted and linked to this Workshop Session or add a comment on this page below and include a link to your paper.

Summary

• Provide a summary of the scenario and the community that the scenario supports.
• Identify the specific decisions to be made.
• Provide references for additional information.

Context and pre-conditions

• Identify the actors in the scenario. Actors are any persons involved in the scenario.
• List, at a summary level, the specific information assumed to be available before the scenario begins.
• List, at a summary level, the specific processing and collaboration functionality assumed needed in the scenario.

Scenario Events

• The scenario should be elaborated as a set of steps that result in the creation of decision support products developed in collaboration by the actors.
• Use the table to identify the main sequence of events in the scenario. In the course of the scenario you may identify an alternative branch step that could be taken, but then return to the main sequence steps.

GEOSS Architecture Implementation Pilot: Air Quality Scenario Development

(This page is currently a template provided by GEOSS-OGC that will be completed. )

If you have a position paper on this session either send your position paper to George Percivall and it will be posted and linked to this Workshop Session or add a comment on this page below and include a link to your paper.

Summary

• Provide a summary of the scenario and the community that the scenario supports.
• Identify the specific decisions to be made.
• Provide references for additional information.

Context and pre-conditions

• Identify the actors in the scenario. Actors are any persons involved in the scenario.
• List, at a summary level, the specific information assumed to be available before the scenario begins.
• List, at a summary level, the specific processing and collaboration functionality assumed needed in the scenario.

Scenario Events

• The scenario should be elaborated as a set of steps that result in the creation of decision support products developed in collaboration by the actors.
• Use the table to identify the main sequence of events in the scenario. In the course of the scenario you may identify an alternative branch step that could be taken, but then return to the main sequence steps.

Scenario Development Process

Pilot on OGC Site

The scenarios provide a narrative description of functionality to be supported by the Pilot. Scenarios are written from an end-users point of view, e.g.,

• policy maker
• decision-maker
• researcher, etc.

Scenarios such will be used to develop the demonstrations. Demonstrations are the main outcome of the pilots.

The Call for Participation invites GEO Members and Participating Organizations to:

• Identify GEOSS Components with services relevant to GEOSS Clearinghouse and GEOSS Web Portals, e.g, specific EO portals, catalogs, and other services;
• Participate in confirming the interoperability of those identified services using standards and interoperability arrangements of the GEOSS architecture; and,
• Participate in the collaborative development of societal benefit scenarios to guide testing and demonstrations of the identified interoperable services.

Scenario Examples

2007 Architecture Implementation Pilot - List of scenarios