Connecting the Dots CAPWSRP 18 November 2004 Connecting
Connecting the Dots: CAP-WSRP 18 November 2004 Connecting the Dots: CAPWSRP 1
Summary n n 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. 18 November 2004 Connecting the Dots: CAPWSRP 2
Overview n n n 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 WSRP=EA-SOA: Enterprise Architecture Using Service-Oriented Architecture EMT Units Leveraging Power of Information - Locate Medical Resources, GIS, + 18 November 2004 Connecting the Dots: CAPWSRP 3
XML: Ready to Start Connecting the Dots n n n 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. 18 November 2004 Connecting the Dots: CAPWSRP 4
Complementary Standards Support Expansion of XML n n n eb. XML Registry/Repository gains ‘Crossover’ Support from W 3 C. UDDI & eb. XML 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. 18 November 2004 Connecting the Dots: CAPWSRP 5
Adopting Open Standards Necessary for Interoperability n n n Initial Standards Provide Starting Points, but. . . Learning from Implementation Leads to Genuine Usability Refinements. ‘Extensibility’ Key to Requirements for v. 2. x > (pre-testing). 18 November 2004 Connecting the Dots: CAPWSRP 6
XML Ready for Phase 2: Harvesting Experience n n Phase 1: Standards Process Provides Pattern - Use Cases > Requirements > Formal 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. 18 November 2004 Connecting the Dots: CAPWSRP 7
Standards Work Scoped to Audience-Market n n ISO-Based on National Representation. W 3 C-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. 18 November 2004 Connecting the Dots: CAPWSRP 8
Web Services - From Hyperbole to Hard Work as Y 2 K Fades n n n 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. 18 November 2004 Connecting the Dots: CAPWSRP 9
Web Services Support Structure & Stacks Start with OSI: 18 November 2004 Connecting the Dots: CAPWSRP 10
Web Services Stacks 18 November 2004 Connecting the Dots: CAPWSRP 11
OSI & Web Services Stacks 18 November 2004 Connecting the Dots: CAPWSRP 12
Standards, Web Stacks, OSI 18 November 2004 Connecting the Dots: CAPWSRP 13
OASIS WSRP 1. 0 Scopes Simple, Basic Functionality First n n n 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. 18 November 2004 Connecting the Dots: CAPWSRP 14
OASIS Finishes CAP 1. 0 n n n 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. 18 November 2004 Connecting the Dots: CAPWSRP 15
CAP: Designed to Work with Web Services, Fits WSRP n n CAP Adopted XML Schema to Standardize Terminology. CAP Adaptable to Web Services Delivery through DHS/FEMA/DMIS - Disaster Management Interoperabilty Services - Pioneers Pre-testing Interoperability Standards to Work with DHS and Emergency Management Community. DMIS: a Founding Member of EMTC. 18 November 2004 Connecting the Dots: CAPWSRP 16
DHS/FEMA/DMIS: Open Standards - Interoperability 18 November 2004 Connecting the Dots: CAPWSRP 17
CAP in WSRP=EA-SOA: Enterprise Architecture Using Service-Oriented Architecture n n n WSRP Portal/Portlets Show EA-SOA Across Government-Business, Public. Private, J 2 EE-. NET Boundaries. Enterprise Architecture (EA) Provides Comprehensive Structure for Organization-Wide IT Integration. Service-Oriented Architecture Provides Reusability of Customizable Service Components. 18 November 2004 Connecting the Dots: CAPWSRP 18
Enterprise Architecture 18 November 2004 Connecting the Dots: CAPWSRP 19
Service-Oriented Architecture 18 November 2004 Connecting the Dots: CAPWSRP 20
Service-Oriented Architecture: Business Example 18 November 2004 Connecting the Dots: CAPWSRP 21
DMIS Shows CAP in Web Services Design Principles n n n Architecture Follows Process Follows Function. Bottom>Up Reporting, Top>Down Administration. CAP Incident Alerts Start at Local Level>Report Up Chain>DMIS Distributes Globally. Currently ‘Pull, ’ Can be ‘Push. ’ 18 November 2004 Connecting the Dots: CAPWSRP 22
Bottom-Up & Top-Down Design 18 November 2004 Connecting the Dots: CAPWSRP 23
CAP Summary n n n 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 WSRP=EA-SOA: Enterprise Architecture Using Service-Oriented Architecture EMT Units Leveraging Power of Information - Locate Medical Resources, GIS, + 18 November 2004 Connecting the Dots: CAPWSRP 24
Public Service Portal Shows Use of CAP-WSRP Interoperability n n n 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. 18 November 2004 Connecting the Dots: CAPWSRP 25
Public Service Portal Shows Use of CAP-WSRP Interoperability n n 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 18 November 2004 Connecting the Dots: CAPWSRP 26
Scenario: Series of Incidents Demonstrate CAP-WSRP n n n 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. 18 November 2004 Connecting the Dots: CAPWSRP 27
We Follow EMT Teams: Wireless Notebooks & PDA/Cell Units 18 November 2004 Connecting the Dots: CAPWSRP 28
Portals Provide Varying Levels of Personalization 18 November 2004 Connecting the Dots: CAPWSRP 29
Specialized Communities Available with XACML/eb. XML 18 November 2004 Connecting the Dots: CAPWSRP 30
eb. XML Registry Allows Access by Roles - XACML Registration 18 November 2004 Connecting the Dots: CAPWSRP 31
EMTs Access Medical Resources by CAP Message & Type 18 November 2004 Connecting the Dots: CAPWSRP 32
EMTs Find Medical Resources by CAP Message & Type 18 November 2004 Connecting the Dots: CAPWSRP 33
Examples Show Drilling Down in Database 18 November 2004 Connecting the Dots: CAPWSRP 34
Examples Show Drilling Down For in Database 18 November 2004 Connecting the Dots: CAPWSRP 35
Examples Show Drilling Down For in Database 18 November 2004 Connecting the Dots: CAPWSRP 36
Examples Show Drilling Down For in Database 18 November 2004 Connecting the Dots: CAPWSRP 37
GIS Portlet Provides Mission Critical Information For Emergency Managers, EMTs n n n 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. 18 November 2004 Connecting the Dots: CAPWSRP 38
GIS Portlet Provides Mission Critical Information 18 November 2004 Connecting the Dots: CAPWSRP 39
GIS Portlet Provides Mission Critical Information 18 November 2004 Connecting the Dots: CAPWSRP 40
GIS Portlet Provides Mission Critical Information 18 November 2004 Connecting the Dots: CAPWSRP 41
Update From Second Source by Wireless Voice: Critical Feature 18 November 2004 Connecting the Dots: CAPWSRP 42
Original Update From Second Source Available Separately 18 November 2004 Connecting the Dots: CAPWSRP 43
Original Update From Second Source (A Service of Geo. Response. com) Report an Event/ View Status of call/ Reports/ Conduct spatial analysis Receive and map critical responses 18 November 2004 Geocode the call region Initiate call Connecting the Dots: CAPWSRP Create call list Customize and approve the message 44
Original Oracle Portlets in Oracle Portal 18 November 2004 Connecting the Dots: CAPWSRP 45
Original Oracle Portlets in Oracle Portal 18 November 2004 Connecting the Dots: CAPWSRP 46
Original Oracle Portlets in Oracle Portal 18 November 2004 Connecting the Dots: CAPWSRP 47
Original Oracle Portlets in Oracle Portal 18 November 2004 Connecting the Dots: CAPWSRP 48
WSRP Portlets from TC Vendors http: //wsrp. dyndns. org: 9081/wps/portal/!ut/p/. cmd/cs /. ce/7_0_A/. s/7_0_1 UN/_s. 7_0_A/7_0_1 UN 18 November 2004 Connecting the Dots: CAPWSRP 49
WSRP Portlets from TC Vendors http: //wsrp. dyndns. org: 9081/wps/portal/!ut/p/. cmd/cs /. ce/7_0_A/. s/7_0_1 UN/_s. 7_0_A/7_0_1 UN 18 November 2004 Connecting the Dots: CAPWSRP 50
More WSRP Samples 18 November 2004 Connecting the Dots: CAPWSRP 51
Summary n n 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. 18 November 2004 Connecting the Dots: CAPWSRP 52
- Slides: 52