520 likes | 622 Views
Connecting the Dots: CAP-WSRP. 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. Overview.
E N D
Connecting the Dots:CAP-WSRP Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
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 WSRP=EA-SOA: Enterprise Architecture Using Service-Oriented Architecture • EMT Units Leveraging Power of Information - Locate Medical Resources, GIS, + Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
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 > (pre-testing). Connecting the Dots: CAP-WSRP
XML Ready for Phase 2: Harvesting Experience • Phase 1: Standards Process Provides Pattern - Use Cases > Requirements > 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. Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
Web Services Support Structure & Stacks Start with OSI: Connecting the Dots: CAP-WSRP
Web Services Stacks Connecting the Dots: CAP-WSRP
OSI & Web Services Stacks Connecting the Dots: CAP-WSRP
Standards, Web Stacks, OSI Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
DHS/FEMA/DMIS:Open Standards - Interoperability Connecting the Dots: CAP-WSRP
CAP in WSRP=EA-SOA:Enterprise 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. Connecting the Dots: CAP-WSRP
Enterprise Architecture Connecting the Dots: CAP-WSRP
Service-Oriented Architecture Connecting the Dots: CAP-WSRP
Service-Oriented Architecture: Business Example Connecting the Dots: CAP-WSRP
DMIS Shows CAP in Web Services Design Principles • Architecture Follows Process Follows Function. • Bottom>Up Reporting, Top>Down Administration. • CAP Incident Alerts Start at Local Level>Report Up Chain>DMIS. • DMIS Distributes Globally. • Currently ‘Pull,’ Can be ‘Push.’ Connecting the Dots: CAP-WSRP
Bottom-Up & Top-Down Design Connecting the Dots: CAP-WSRP
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 WSRP=EA-SOA: Enterprise Architecture Using Service-Oriented Architecture • EMT Units Leveraging Power of Information - Locate Medical Resources, GIS, + Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
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 Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
We Follow EMT Teams: Wireless Notebooks & PDA/Cell Units Connecting the Dots: CAP-WSRP
Portals Provide Varying Levels of Personalization Connecting the Dots: CAP-WSRP
Specialized Communities Available with XACML/ebXML Connecting the Dots: CAP-WSRP
ebXML Registry Allows Access by Roles - XACML Registration Connecting the Dots: CAP-WSRP
EMTs Access Medical Resources by CAP Message & Type Connecting the Dots: CAP-WSRP
EMTs Find Medical Resources by CAP Message & Type Connecting the Dots: CAP-WSRP
Examples Show Drilling Down in Database Connecting the Dots: CAP-WSRP
Examples Show Drilling Down For in Database Connecting the Dots: CAP-WSRP
Examples Show Drilling Down For in Database Connecting the Dots: CAP-WSRP
Examples Show Drilling Down For in Database Connecting the Dots: CAP-WSRP
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. Connecting the Dots: CAP-WSRP
GIS Portlet Provides Mission Critical Information Connecting the Dots: CAP-WSRP
GIS Portlet Provides Mission Critical Information Connecting the Dots: CAP-WSRP
GIS Portlet Provides Mission Critical Information Connecting the Dots: CAP-WSRP
Update From Second Source by Wireless Voice: Critical Feature Connecting the Dots: CAP-WSRP
Original Update From Second Source Available Separately Connecting the Dots: CAP-WSRP
Report an Event/ View Status of call/ Reports/ Conduct spatial analysis Geocode the call region Create call list Customize and approve the message Receive and map critical responses Initiate call Original Update From Second Source (A Service of GeoResponse.com) Connecting the Dots: CAP-WSRP
Original Oracle Portlets in Oracle Portal Connecting the Dots: CAP-WSRP
Original Oracle Portlets in Oracle Portal Connecting the Dots: CAP-WSRP
Original Oracle Portlets in Oracle Portal Connecting the Dots: CAP-WSRP
Original Oracle Portlets in Oracle Portal Connecting the Dots: CAP-WSRP
WSRP Portlets from TC Vendors http://wsrp.dyndns.org:9081/wps/portal/!ut/p/.cmd/cs/.ce/7_0_A/.s/7_0_1UN/_s.7_0_A/7_0_1UN Connecting the Dots: CAP-WSRP
WSRP Portlets from TC Vendors http://wsrp.dyndns.org:9081/wps/portal/!ut/p/.cmd/cs/.ce/7_0_A/.s/7_0_1UN/_s.7_0_A/7_0_1UN Connecting the Dots: CAP-WSRP