Connecting the Dots: CAP-WSRP

1
Connecting the DotsCAP-WSRP
2
Summary

• Standards Meant to be Used Together.
• Modular, Flexible Approaches will Find More
  Success than Single Vendor Solutions.
• Promoting Adoption Necessary for Continued
  Development Improvement.
• New Standards Will be Needed in Foreseeable
  Future.

3
Overview

• The Evolution of Web Services
• OASIS WSRP 1.0 Scopes Simple, Basic Functionality
  
• CAP Approved April 2004
• CAP Designed to Work with Web Services, Fits
  WSRP
• CAP in WSRPEA-SOA Enterprise Architecture Using
  Service-Oriented Architecture
• EMT Units Leveraging Power of Information -
  Locate Medical Resources, GIS,

4
XML Ready to StartConnecting the Dots

• Common Alerting Protocol 1.0 -
• CAP Approved OASIS Standard
• April 2004.
• Web Services for Remote Portlet 1.0 - WSRP
  Approved OASIS Standard August 2003.
• Despite Inconsistencies, XML Leads Open Standards
  Efforts.

5
Complementary Standards Support Expansion of XML

• ebXML Registry/Repository gains Crossover
  Support from W3C.
• UDDI ebXML Reg/Rep Provide Discovery for
  Potential Partners.
• SAML (moving to 2.0), WSS 1.0 Approved OASIS
  Standard April 2004 XACML (also moving to 2.0),
  Stabilizing XML-based Security.

6
Adopting Open Standards Necessary for
Interoperability

• Initial Standards Provide Starting Points, but...
• Learning from Implementation Leads to Genuine
  Usability Refinements.
• Extensibility Key to Requirements for v. 2.x gt
  (pre-testing).

7
XML Ready for Phase 2 Harvesting Experience

• Phase 1 Standards Process Provides Pattern -
  Use Cases gt Requirements gt Formal Standards.
• Standards are not Standards unless Adopted
  Widely.
• Remember Browser Wars and the inevitability of
  de facto Standards.
• IT, like Nature, Abhors Vacuum, so Standards WILL
  Emerge where Needed - even if Poorly Conceived.

8
Standards Work Scoped to Audience-Market

• ISO-Based on National Representation.
• W3C-Based on Corporate (Paid) Academic
  Interests (ARPANet CERN Founding Members).
• OASIS-Based on Corporate (Paid) Representation
  Specializes on Structured Information-XML.
• IEEE, IETF, ANSI, etc. Subsets Tend Specific
  Interests.

9
Web Services - From Hyperbole to Hard Work as Y2K
Fades

• Web Services Concept Emerges as Dot-Com Bubble
  Bursts.
• Hyperbole Gives Way to Global IT Recession - IT
  Spending Decline.
• WSIA-WSRP Begins January 2002.
• WSRP 1.0 Approved August 2003
• WS-I Evolves as Interoperability
  Testing/Incubator Adjunct to Standards Groups.

10
Web Services Support Structure Stacks Start
with OSI
11
Web Services Stacks
12
OSI Web Services Stacks
13
Standards, Web Stacks, OSI
14
OASIS WSRP 1.0 Scopes Simple, Basic Functionality
First

• Focus on Reusing Content Units (Portlets) from
  Multiple Sources.
• Model-View-Control Design Pattern Sets
  Fundamental Architecture.
• Primary Actors (Roles) Defined Producer,
  Consumer, User.
• Started with Stateless Portlets, then Simple
  Interactivity and Stateful Portlets.
• Security Left to Security Committees.

15
OASIS Finishes CAP 1.0

• CAP Brought into OASIS Process at Start of
  Emergency Management Technical Committee (EMTC)
  March 2003 - Approved April 2004.
• Partnership for Public Warning (PPW) Worked Two
  Years Before Bringing CAP Project to EMTC.
• Scoped for Broad Use, Transport (Delivery)
  Independence, Emphasis on Alert Warning
  Terminology with XML Schema.

16
CAP Designed to Work with Web Services, Fits WSRP

• CAP Adopted XML Schema to Standardize
  Terminology.
• CAP Adaptable to Web Services Delivery through
  DHS/FEMA/DMIS.
• DMIS - Disaster Management Interoperabilty
  Services - Pioneers Pre-testing Interoperability
  Standards to Work with DHS and Emergency
  Management Community.
• DMIS a Founding Member of EMTC.

17
DHS/FEMA/DMISOpen Standards - Interoperability
18
CAP in WSRPEA-SOAEnterprise Architecture
UsingService-Oriented Architecture

• WSRP Portal/Portlets Show EA-SOA Across
  Government-Business, Public-Private, J2EE-.NET
  Boundaries.
• Enterprise Architecture (EA) Provides
  Comprehensive Structure for Organization-Wide IT
  Integration.
• Service-Oriented Architecture Provides
  Reusability of Customizable Service Components.

19
Enterprise Architecture
20
Service-Oriented Architecture
21
Service-Oriented Architecture Business Example
22
DMIS Shows CAP in Web Services Design Principles

• Architecture Follows Process Follows Function.
• BottomgtUp Reporting, TopgtDown Administration.
• CAP Incident Alerts Start at Local LevelgtReport
  Up ChaingtDMIS.
• DMIS Distributes Globally.
• Currently Pull, Can be Push.

23
Bottom-Up Top-Down Design
24
CAP Summary

• The Evolution of Web Services
• OASIS WSRP 1.0 Scopes Simple, Basic Functionality
  
• CAP Approved April 2004
• CAP Designed to work with web services, Fits
  WSRP
• CAP in WSRPEA-SOA Enterprise Architecture Using
  Service-Oriented Architecture
• EMT Units Leveraging Power of Information -
  Locate Medical Resources, GIS,

25
Public Service Portal Shows Use of CAP-WSRP
Interoperability

• Humanmarkup.org, Inc. wishes to Express its
  Appreciation for the generous time and effort
  extended to this Project by Oracle Corporation.
• Interoperability as a Concrete Fact is only
  Achieved by such Efforts.
• This Presentation Shows how Interoperability can
  Improve Emergency Response Services.

26
Public Service Portal Shows Use of CAP-WSRP
Interoperability

• Humanmarkup.org Portal (Courtesy of Plumtree
  Software Inc,) with Oracle and Broadstrokes Inc,
  Apache Portlets
• CAP Alerts Available through DMIS
• Various Emergency Management Agencies Access
  Respond to CAP Messages
• Sample Public Service Portal Aggregates Medical
  GIS Portlets

27
Scenario Series of Incidents Demonstrate CAP-WSRP

• Hurricane Moving Northeast in September Week from
  Puerto Rico to Florida to Charleston to
  Chesapeake Bay-Washington, D.C.
• Early in Week Long Beach, CA Reports Suicide Bomb
  Attempt at LNG Terminal.
• Threat Level Increased.

28
We Follow EMT Teams Wireless Notebooks
PDA/Cell Units
29
Portals Provide Varying Levels of Personalization
30
Specialized Communities Available with XACML/ebXML
31
ebXML Registry Allows Access by Roles - XACML
Registration
32
EMTs Access Medical Resources by CAP Message
Type
33
EMTs Find Medical Resources by CAP Message Type
34
Examples Show Drilling Down in Database
35
Examples Show Drilling Down For in Database
36
Examples Show Drilling Down For in Database
37
Examples Show Drilling Down For in Database
38
GIS Portlet Provides Mission Critical Information
For Emergency Managers, EMTs

• Geospatial Information Translated into Useful
  Maps-Updates.
• Maps Indexed by Layers of Information Available
  by Clicking Emergency Symbols.
• Combined Resources Provide Common Operational
  Environment COE.

39
GIS Portlet Provides Mission Critical Information
40
GIS Portlet Provides Mission Critical Information
41
GIS Portlet Provides Mission Critical Information
42
Update From Second Source by Wireless Voice
Critical Feature
43
Original Update From Second Source Available
Separately
44
Original Update From Second Source (A Service of
GeoResponse.com)
45
Original Oracle Portlets in Oracle Portal
46
Original Oracle Portlets in Oracle Portal
47
Original Oracle Portlets in Oracle Portal
48
Original Oracle Portlets in Oracle Portal
49
WSRP Portlets from TC Vendors

• http//wsrp.dyndns.org9081/wps/portal/!ut/p/.cmd/
  cs/.ce/7_0_A/.s/7_0_1UN/_s.7_0_A/7_0_1UN

50
WSRP Portlets from TC Vendors

• http//wsrp.dyndns.org9081/wps/portal/!ut/p/.cmd/
  cs/.ce/7_0_A/.s/7_0_1UN/_s.7_0_A/7_0_1UN

51
More WSRP Samples
52
Summary

• Standards Meant to be Used Together.
• Modular, Flexible Approaches will Find More
  Success than Single Vendor Solutions.
• Promoting Adoption Necessary for Continued
  Development Improvement.
• New Standards Will be Needed in Foreseeable
  Future.