Difference between revisions of "2006-07-30 GEOSS User V - AQ Data Systems"

From Earth Science Information Partners (ESIP)
Line 6: Line 6:
 
====..Current Situation====
 
====..Current Situation====
 
: Few users; limited, sporadic data/model; poor integration; Dedicated 'Stove Pipe' Systems -> Stiff and limited decision support
 
: Few users; limited, sporadic data/model; poor integration; Dedicated 'Stove Pipe' Systems -> Stiff and limited decision support
====..Near Furure====
+
====..Near-Term Furure====
 
: Diverse users, More sensory/model data-GEOSS; Extensive integration and 'mashing'-Web 2.0; Network effect ->Responsive decisin support
 
: Diverse users, More sensory/model data-GEOSS; Extensive integration and 'mashing'-Web 2.0; Network effect ->Responsive decisin support
 +
 +
====..How Do We Get There?====
 +
: Interop Experiments; Rapid Prototyping Plaforms; Google (rapid, continuous upgrades, sloppy) or Microsoft (slow, perfection)  philosophy?
 +
 
====..Paper purpose and outline====
 
====..Paper purpose and outline====
 
: Community assessment of AQ IT; User feedback to GEOSS Architecture; Aid to agency planners   
 
: Community assessment of AQ IT; User feedback to GEOSS Architecture; Aid to agency planners   

Revision as of 10:01, June 23, 2006

Architectures and Technologies for Agile, User-Oriented Air Quality Data Systems
A white paper prepared by an ad hoc virtual workgroup using open collaborative tchnologies
Possible presentation venues: GEOSS User Workshop, Jul 2006, Denver; Fall AGU, Dec 2006, San Francisco; HTAP Workshop, Jan 2007, Geneva

.

Current and Near Future AQ Information System of Systems

..Current Situation

Few users; limited, sporadic data/model; poor integration; Dedicated 'Stove Pipe' Systems -> Stiff and limited decision support

..Near-Term Furure

Diverse users, More sensory/model data-GEOSS; Extensive integration and 'mashing'-Web 2.0; Network effect ->Responsive decisin support

..How Do We Get There?

Interop Experiments; Rapid Prototyping Plaforms; Google (rapid, continuous upgrades, sloppy) or Microsoft (slow, perfection) philosophy?

..Paper purpose and outline

Community assessment of AQ IT; User feedback to GEOSS Architecture; Aid to agency planners

AQ Data System Architectures

..User-Driven: User Drives Design

..Distributed: Structure Extends over Many Dimensions

..Loosely Couppled: Software Components, System of Systems, Architcture of Participation

Information Technologies

..Software Components: Data as Service, Web Services

..Interoperability Technologies: Standards/Conventions, Wrappers and Adopters, Workflow Engines

..Web 2.0 Technologies: Searching, Tagging, RSS, AJAX ...

Challenges

..Human Factors

The 4 C's: Communication, Coordination, Cooperation, Competion, Coopetition
Attracting user participation

..Architecture

Maximize the 'Network Effect'....

..Technologies

Grasping and harnessing Web 2.0

AQ IT Support for End Users, Programs, Agencies and Projects

..End Users: AQ Managment, Science & Policy, Informing Public & Education

..Programs: GEOSS,

..Agencies: National, International

..Projects: ????

Prototype Agile AQ Application Examples

..FASTNET, CATT, Event Analysis

..GSN Demo

So? Next Steps?