18 November 2004 Connecting the Dots: CAP- WSRP 1.
52
18 November 2004 Connecting the Dots: CAP- WSRP 1 Connecting the Dots: CAP-WSRP
-
Upload
priscilla-wilcox -
Category
Documents
-
view
224 -
download
0
Transcript of 18 November 2004 Connecting the Dots: CAP- WSRP 1.
18 November 2004
Connecting the Dots: CAP-WSRP
1
Connecting the Dots:CAP-WSRP
18 November 2004
Connecting the Dots: CAP-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.
18 November 2004
Connecting the Dots: CAP-WSRP
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 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: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
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 > (pre-testing).
18 November 2004
Connecting the Dots: CAP-WSRP
7
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.
18 November 2004
Connecting the Dots: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
10
Web Services Support Structure & Stacks Start with
OSI:
18 November 2004
Connecting the Dots: CAP-WSRP
11
Web Services Stacks
18 November 2004
Connecting the Dots: CAP-WSRP
12
OSI & Web Services Stacks
18 November 2004
Connecting the Dots: CAP-WSRP
13
Standards, Web Stacks, OSI
18 November 2004
Connecting the Dots: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
17
DHS/FEMA/DMIS:Open Standards - Interoperability
18 November 2004
Connecting the Dots: CAP-WSRP
18
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.
18 November 2004
Connecting the Dots: CAP-WSRP
19
Enterprise Architecture
18 November 2004
Connecting the Dots: CAP-WSRP
20
Service-Oriented Architecture
18 November 2004
Connecting the Dots: CAP-WSRP
21
Service-Oriented Architecture: Business Example
18 November 2004
Connecting the Dots: CAP-WSRP
22
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.’
18 November 2004
Connecting the Dots: CAP-WSRP
23
Bottom-Up & Top-Down Design
18 November 2004
Connecting the Dots: CAP-WSRP
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 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: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
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
18 November 2004
Connecting the Dots: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
28
We Follow EMT Teams: Wireless Notebooks & PDA/Cell Units
18 November 2004
Connecting the Dots: CAP-WSRP
29
Portals Provide Varying Levels of Personalization
18 November 2004
Connecting the Dots: CAP-WSRP
30
Specialized Communities Available with XACML/ebXML
18 November 2004
Connecting the Dots: CAP-WSRP
31
ebXML Registry Allows Access by Roles - XACML Registration
18 November 2004
Connecting the Dots: CAP-WSRP
32
EMTs Access Medical Resources by CAP Message & Type
18 November 2004
Connecting the Dots: CAP-WSRP
33
EMTs Find Medical Resources by CAP Message & Type
18 November 2004
Connecting the Dots: CAP-WSRP
34
Examples Show Drilling Down in Database
18 November 2004
Connecting the Dots: CAP-WSRP
35
Examples Show Drilling Down For in Database
18 November 2004
Connecting the Dots: CAP-WSRP
36
Examples Show Drilling Down For in Database
18 November 2004
Connecting the Dots: CAP-WSRP
37
Examples Show Drilling Down For in Database
18 November 2004
Connecting the Dots: CAP-WSRP
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.
18 November 2004
Connecting the Dots: CAP-WSRP
39
GIS Portlet Provides Mission Critical Information
18 November 2004
Connecting the Dots: CAP-WSRP
40
GIS Portlet Provides Mission Critical Information
18 November 2004
Connecting the Dots: CAP-WSRP
41
GIS Portlet Provides Mission Critical Information
18 November 2004
Connecting the Dots: CAP-WSRP
42
Update From Second Source by Wireless Voice: Critical Feature
18 November 2004
Connecting the Dots: CAP-WSRP
43
Original Update From Second Source Available Separately
18 November 2004
Connecting the Dots: CAP-WSRP
44
Original Update From Second Source (A Service of GeoResponse.com)
Report an Event/ ViewStatus of call/ Reports/Conduct spatial analysis
Geocode the call region Create call list
Customize and approve the messageInitiate call Receive and
map critical responses
18 November 2004
Connecting the Dots: CAP-WSRP
45
Original Oracle Portlets in Oracle Portal
18 November 2004
Connecting the Dots: CAP-WSRP
46
Original Oracle Portlets in Oracle Portal
18 November 2004
Connecting the Dots: CAP-WSRP
47
Original Oracle Portlets in Oracle Portal
18 November 2004
Connecting the Dots: CAP-WSRP
48
Original Oracle Portlets in Oracle Portal
18 November 2004
Connecting the Dots: CAP-WSRP
49
WSRP Portlets from TC Vendorshttp://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
18 November 2004
Connecting the Dots: CAP-WSRP
50
WSRP Portlets from TC Vendorshttp://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
18 November 2004
Connecting the Dots: CAP-WSRP
51
More WSRP Samples
18 November 2004
Connecting the Dots: CAP-WSRP
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.
![Denial-of-Service Open Threat Signaling (DOTS). · architecture, called DDoS Open Threat Signaling (DOTS) [I-D.ietf-dots-architecture], in which a DOTS client can inform a DOTS server](https://static.fdocuments.in/doc/165x107/6018af73a358a566d57c4efb/denial-of-service-open-threat-signaling-dots-architecture-called-ddos-open-threat.jpg)
![Untitled-2 [] · 2 DOTS 1 DOT 1 DOT POWER BY CYLINDER 2 DOTS 3 DOTS 2 DOTS 2 DOTS ELECTRO-INJECTOR GREEN WHITE RED 6 CYLINDERS TYPE AND 8 CYLINDERS ELECTRO-INJECTORS REFERENCE TABLE](https://static.fdocuments.in/doc/165x107/5f083f2f7e708231d4210fbe/untitled-2-2-dots-1-dot-1-dot-power-by-cylinder-2-dots-3-dots-2-dots-2-dots.jpg)
