PRISM Information Integration System The Bloodstream

1
PRISM Information Integration SystemThe
Bloodstream

• Miles Logsdon
• Bruce Campbell
• Harvey Greenberg
• Sarah Rodda

2
DRIVERS MODELS
OUTPUT

UrbanSim CRYSTAL
Surface Field
Land
MM5
Urban
Conversion

Interpolation
Model


Initial
48hr Weather
Impervious

Surface Field
Boundary
Forecasts
Surface
NCEP
to Sound

Circulation
Coordinate Transformation
Resources

SST
Interpolation PRISM
Use

Domain
3-D Fields

WEB
Water


Short- Long-wave
Demand
Land


Precipitation

Temperature

Cover

Humidity
River Flow

P. S. Template

Wind Speed
Emissions
Basin Sums

Surface pressure
(biophysical)
Soils
Infrastructure

Topography
WEB

Transportation
Miles' 1998
DHSVM
WEB

Climate
Flow

Energy
Visuals

Soils
Visuals

Water Sewer
Routing
Tidal
Elevation
Salinity
Sound
Circulation
Current
Mixing
POM
Lateral Boundary
Temperature

Tidal Elevation

River Flow
WEB

River Temp.
Visuals
3
Miles explains PRISM '99 - '00
Hunter Hadaway CEV
4
We started drawing arrows
5
SeaWiFs
AVHRR
urbdp467
Landsat TM
Water Resource Allocation
More Arrows
CRYSTAL
6
PRISM Information Integration System
Architecturethe Bloodstream

• Fewer Arrows
• Less lines
• A circle!

7
Key Points

• Its about Data Integration and Data Sharing
• Everyone is either one or more of these
• A data source
• An Occasional default data sink (proactive)
• A hardwired data sink (proactive)
• A query sink (retroactive)
• Weve begun
• Relay Node plasmus.ocean.washington.edu
• Wiring for example sink and source services
• Default source and sink services
• Investigation of 39 program languages suited for
  XML-RPC services

8
Design Basis a framework that simplifies all
aspects of scientific data networking, allowing
simple access to data

• Built upon the design principles of
• Division of Atmospheric Sciences (ATM) of the
  National Science Foundation (NSF) NSF UNIDATA
  program, and the Internet Data Distribution (IDD
  ) system, and
• The NASA Earth Science Information Partners
  (ESIP) Federation

9
Design Principle

• Data are most appropriately described updated and
  distributed by those that develop them
• Users desire access ready for their existing
  application/software
• It isnt the scientists job to responding to data
  request
• Users want access to data from anywhere that is
  served by the PRISM project regardless of its
  native format

10

Data SOURCE servicesData RELAY servicesData
SINK services

• Multiple SOURCES Data can be injected into the
  BLOODSTREAM from multiple sources where SOURCE
  SERVICES have been installed.
• Data recognition SINKS Through a data
  recognition mechanism, users select from the
  available data only those needed for their needs.
  
• Reliable data delivery RELAYS Reliable transport
  protocols ensure data accuracy at all sites. A
  queuing system buffers data flows at relays,
  preventing losses from network congestion and
  short outages.
• Load distribution designed to avoid excessive
  concentration of network traffic. Generally,
  metadata flows with data. Only new data flow when
  needed.

11
What is XML-RPC?

• A specification and a set of implementations that
  allow software running on disparate operating
  systems, running in different environments to
  make procedure calls over the Internet.
• Remote procedure calling services using HTTP as
  the transport and XML as the encoding. XML-RPC is
  designed to be as simple as possible, while
  allowing complex data structures to be
  transmitted, processed and returned.

12
XML-RPC Implementations

• AOL Server client/server
• Apache client/server
• AppleScript client
• ASP client/server
• Axapta client/server
• C/C client/server
• C client/server
• Cold Fusion client/server
• COM client/server
• Delphi/Kylix client/server
• Dylan client/server
• Eiffel client/server
• Flash client
• Frontier client/server
• Guile client/server
• Internet Expolrer client
• J2ME client
• Java client/server
• JavaScript client

• Microsoft .NET client/server
• Mozilla client
• Objective C client/server
• Perl client/server
• PHP client/server
• Pike server
• Python client/server
• REALBasic client
• Rebol client/server
• Ruby client/server
• Scheme client
• Tcl client/server
• Tintware client/server
• WebObjects client/server
• Zope client/server

13
Default Sink Client (available 11/15/2002)
Filtering Available based on XML hierarchy
Applet or Application
Query results of latest catalog entries

• Data Access Methods
• Web via URL
• FTP via anonymous FTP
• Email via request form
• Database Query
• Other methods required by us

Status Updates
14
Default Source Client (available 11/15/2002)
Applet or Application
For Querying and Filtering
15
Miles Parting Shots

• Remember Were trying to say
• Collaboration begins with sharing information
• Each of our projects is both a data source and
  data sink within the PRISM program
• By communicating through our data and
  information, we reduce the need for numerous
  solutions to similar tasks of data distribution,
  formatting, archiving, and retrieval tasks

16
Have Fun!