20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
1
Semantic Interoperability at Work:Improving Rapid First Response
The Right Informationat the Right Fingertips
at the Right Time
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
2
Semantic Interoperability at Work:Improving Rapid First Response
Part One
What DoesSemantic Interoperability
Really Mean?
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
3
Semantic Interoperability at Work:Improving Rapid First Response
First, Foremost,Interoperability
MeansTeamwork
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
4
Semantic Interoperability (SI)
• First Mentioned on Web in 2000• Apparently Quick Study:
SI Conference in Houston This Date Ontolog Forum on SWSF / FLOWS,
WSDL-S, OWL-S This Date
• Progression of Standards: SGML>XML/RDF>RDF/OWL>?
• SICoP, XMLCoP Keeping Pace
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
5
Semantic Interoperability
• Some Helpful, Simplified Similes
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
6
Semantics Symplified
• Semantics Studies MEANINGS Seeks Linguistic Clarity & Specificity wrt
LEVELS OF ABSTRACTION Seeks no confusion of map & territory
• Semiotics Studies SIGNS, SIGNALS & SYMBOLS Identifies Components of Communication Identifies Roles of Components
• Interoperability Needs Semantic Roadmaps, Guides, Dictionaries, etc. for Translating Similar but Disparate Vocabularies
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
7
Interoperability
• Interoperability Much Newer Term Coined Specifically for Software Popularizaton of XML Largely Grew
out of Improvement over Document Type Definitions (DTDs) to Salvage Legacy Databases
XML Schema Much More Useful, so Mistakenly Applied to Problems Not Targeted by XML
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
8
Semantic Interoperability in “Semantic Web” Foundation
• Needs Web Ontology Language (OWL), Written in RDF) Many Advantages, Pitfalls Not Ontology with Capital “O” yet
• Understanding Relationship of Terms to Domain-Specific Context Required EDI For Instance UBL, ebXML, etc Setting Standards for
Business Context
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
9
Semantic Interoperability Standards Required
• “Semantic Web” Requires Standards• TopicMaps an Early Attempt, Useful, but
Limited Structure Based on Associations, more than Relationships
• XML Domain-Specific Vocabulary Definitions Allow Document by Document Translations of Terms & Datatypes-Tedious and Repetitious though Templates Possible
• XML-based Standards Allows Document & Application Domain Vocabularies to be made Interoperable, but… Closely Related, Previously Defined Vocabularies
Problematic Inadvertent Duplicative Efforts can Conflict
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
10
XML-Based Standards Make Good Start
• OASIS Standards in Divergent Fields demonstrate promise Universal Business Language (UBL), Common Alerting Protocol (CAP) and Web Services for Remote Portlets (WSRP)
• Lag Time Difficult When Needs Press• Adoption is Extra Work for Volunteers• Momentum Slowly Building
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
11
First Key to Semantic Interoperability: RDF
• Resource Description Language (RDF) Defines Relationships of Entities Using
“Triples” Triples are “Statements” Consisting of:
Subject: (Resource) Defined by Universal Resource Identifier (URI)
Object: (Property) a Named Resource that can have its own properties
Predicate: (Value/Relationship) Statements like “x is a member of y” Allow
Reasoning, or Inference Engines to Operate over Populations of Documents, over Resources and over Business Process such as Policy & Security
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
12
Second Key to Semantic Interoperability: OWL
• Web Ontology Language (OWL) Allows Definition of Classification Systems
with Inheritance of Properties Comes in Three SubLanguages (so far)
OWL Lite Allows a Classification Hierarchy and Simple Constraints—Most Widely Used
OWL DL (Description Logic) Allows Maximum Expressiveness with Computational Completeness
OWL Full Allow Complete Expressiveness and Syntactic Freedom but no Computational Guarantees
Allows Much More Extensive Reasoning
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
13
Semantic Interoperability Allows Improved Search, Rules & Security
• Semantically Based Registries Can Allow More Focused Lookup for Compatible Web Services Partners
• Semantically-Capable Partners Can Align & Automate Mutual Business Processes over Larger Range
• Semantically-Based Security Rules Can Allow More Sharing with Security
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
14
Need for Standards Still Strong
• Semantic Interoperability Needs the XML Vocabulary Standard Work to Continue
• Companies, Agencies Need to be Shown that this work is in Their Interest Employee Time Justified Resources Justifed Benefits need to be measured in terms of
Time Saved as well as Costs Saved into Future
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
15
How are we Showing Semantic Interoperability?
• Within CAP 1.0, (and 1.1)the <event> Sub-element of the <info> Element is a String (Text), Intended to Supply an “Event Type” which we Use as a Semantic Key
We Use CAP 1.0, (CAP 1.1 was not yet an OASIS Standard When this Pilot Started)
We Use a Simulated Event Type ontology (Called an ontology Because it is written in OWL/RDF)
• Within The Emergency Data Exchange Language Distribution Element (EDXL_DE) the <keyword> Element Requires a Managed List Associated with the Keyword and the List--a Method made for Semantic Interoperability
EDXL_DE is not yet an OASIS Standard but Our Work Reflects its Functionality as a Routing Standard for Emergency Messages
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
16
SI Architecture Not Yet Defined
• Enterprise Architecture Foundation Fits Federal Enterprise Architecture Supports DRM
• Mulitple Service-Oriented Architecture Components Web Services Componentization Registries Make Mix-&-Match Possible
• N-Tier Architecture Allows Flexibility Databases, DBMSs, WebServers, Clients
Separated, Supported
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
17
What Does a Semantic Interoperability Architecture
Look Like?
• This Pilot is a Practical Example Emergency Management Centric Participants Represent Spectrum
• Following Slide Shows Most of the Components Portal and Secondary Support Services
To Come Collection of Participants Would Align
Themselves through Semantically Ordered Registries or Out of Band Web Services Bindings
Shows Messaging Flows Perspective
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
19
Enterprise Architecture
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
20
Service-Oriented Architecture
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
21
Registries Add Semantic Discovery of Services & Resources
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
22
Our Pilot of a Semantic Interoperability Architecture
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
23
Semantic Interoperability Summary
• Teamwork Through Semantically Ordered Web Services
• Registries Allow Related Companies/Entities to Locate Each Other
• Registries Allow Resources to be Located and Bound through Web Services
• Registries Add Layer of Role-Based Security• Third Party Portals and Communities, such
as Geospatial and Healthcare Can Aid Preparedness through Semantically Ordered, PreRegistered Web Services
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
25
Semantic Interoperability at Work:Improving Rapid First Response
Part Two
Train Derailment Example Based on January 6, 2005 Incident in Graniteville, South Carolina
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
26
Semantic Keys to Improving Rapid First Response
• Train Derailment Example: 6 January 2005, 3:50 A.M. Graniteville, SC Chlorine Tank Car Toxic Release
• Matching ResponseType with EventType
• Using Open Public Standards• Getting the Right Information to the
Right People at the Right Time
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
27
Original Timeline v. New Timeline
• Original Timeline: 17 Days• Incident Starts 2:00 A.M. 6 January
2005• All Clear 21 January 2005• New Timeline: 12 Days• Incident Starts 2:00 A.M. 6 January
2006• All Clear 17 January 2006
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
28
Original Timeline Problems
• Incident Starts 2:00 A.M. 6 January 2005 No Early Public Warning Alert First EPA Situation Report 10:00 A.M.
8 Hour Response Quick, Given Circumstances Injuries, Deaths Acknowledged, Chlorine
Hazmat Identified Second EPA Situation Report 4:00 P.M.
EPA Region 4 Operations Support Command (OSC)
Operations Underway
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
29
Original Timeline Problems
Third EPA Situation Report 7 January 2005
EPA Region 4 OSC on Scene - Air Monitoring Extent Hazmat Release Determined 76% of 131
Tons Fourth EPA Situation Report 7 January
2005 - Full Operations Begin
• Logistical Support Operations: Non-NIMS Organizational Impedance
• All Clear 17 January 2005
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
30
New Timeline Improvements
• Incident Starts 2:00 A.M. 6 January 2005 CAP Message with EDXL Header
Optimizes Immediate Public Warning Alert: 2:15 A.M.
Remote Sensors from Tank Cars Trigger Alerts, Trigger Train-Mounted Sirens/PA Systems
First EPA Situation Report 4:00 A.M. Less Than Two-Hour Severe Emergency
Response Triggered by Fatal-Level Hazmat Release
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
31
New Timeline Improvements
Second EPA Situation Report 9:00 A.M. Semantically Triggered Response Allows Full
Operations to Start within 8 Hours Versus Next Day
Hazmat Automatically Identified, Severity Semantics Push First Responses and Eliminate Jurisdictional Duplication of ICS
• Logistical Support Operations: NIMS Plus Semantics Reduces or Eliminates Organizational Impedance
• All Clear 12 January 2006
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
32
Semantic Keys to Improvement
• Common Alerting Protocol (CAP) 1.0 1.1 Recently Approved as OASIS
Standard, Pilot uses 1.0
• EDXL_DE 1.0 Committee Specification Simulated Event Type & Sender/Recipient
Type Ontologies Drive Improved Routing Simulated Event Type also Drives Lookup
for Secondary Healthcare & Geospatial Services
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
33
Event Type Ontology Application: Protégé: http//www.protégé.stanford.edu
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
34
Event Type Ontology in ContextApplication: Unicorn Workbench: http//www.unicorn.com
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
35
Ontological (Semantic) AnalysisElement & Data Asset Comparison
Result: No Duplicated Elements
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
36
Anatomy of CAP-EDXL Emergency Response Communications for New Timeline
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
37
Point-by-Point Details of Collaboration Diagram
• 1) Upon Notification of the incident, Sheriff calls in using his phone or PDA to trigger an emergency alert.
• 2) A CAP message is generated and posted to the ICS hub where it is posted as “Currently Active” in message repository regularly polled by Emergency Management Community. Rules-Based Registry Standards allows a publish-subscribe mechanism for propagating alert naming messages.
• 3) NIMS ICS Policy-Based messages are “automatically” routed to the Local EM Agency where operators can monitor and send out message updates.
• 4) The Secondary Providers Services switch to “Active” Polling for any immediate update-CAP messages routed by EDXL Distribution Header Component with a “PublicAlerting” value.
• 5) GIS map tool provider services respond to the CAP message and process the information, adding a new WSRP Portlet for this Incident. ICS incorporates mapping service.
• 6) A reverse 911 geo-coded lookup is performed and request for local area code-based automatic telephone notification is processes and performed.
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
38
Network Concept
• A network is a graph representation for modeling objects of interest and their relationships. It contains the following elements:
• Nodes: objects of interests Links: relationships between nodes Paths: ordered list of connected links
x0
x1
x2
s1
k1. x0
k2. s1
k3.s1
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
39
RDF Data Model
• RDF data stored in a directed, logical network
• Subjects and objects mapped to nodes, and properties to links that have subject start nodes and object end nodes
• Link represent complete RDF triples
S1 O1
S2 O2
P1
P2
P2
RDF Triples:
• {S1, P1, O1}
• {S1, P2, O2}
• {S1, P2, O2}
16
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
40
Semantic Web Connects Web Services
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
41
Adding Value with Web Services
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
42
Broadstrokes-Reverse 911
• Wireless/VoIP outbound and inbound voice services
• Combines TTS and ASR technologies• Support for web services, SOAP,
VoiceXML, CCXML, CAP, XQUERY and XPATH
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
43
Broadstrokes
Features• Message creation using Text-to-speech• Message creation using Voice Recording• Definition of call lists by static lists• Answering machine recognition• Call rules support• Call Escalation• Call Bandwidth control• Critical response collection & reporting• Call Status Reporting • Multiple Language Options
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
44
Broadstrokes-WSRP
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
45
MyStateUSA (Acting as National Incident Management System-NIMS Incident Command System-ICS)
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
47
TargusInfo• Alert the public in any given location — reach more
people with the most complete, up-to-date name, address, and telephone records.
• Identify unique, non-public resident information for emergency use — only TARGUSinfo can access and deliver telephone data that is not available through other public sources.
• Count on data availability during the most critical situations — our sophisticated network has fully redundant systems, ensuring 24/7 availability.
• Inform the community of non-emergency activities — current name and address means you can stay connected through continuity of operations (COOP) announcements, procedures, special assistance and new developments.
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
48
Humanmarkup.org, Inc.
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
49
Starbourne Communications Design
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
50
Starbourne Communications Design
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
51
Oracle 10g R2 Application Server & Database with RDF Network Data Model
Based on XML 2004 Presentation
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
52
Image MattersalertSmarts™ Application
20 October 2005 Semantic Interoperability at Work:Improving Rapid First Response
53
Full Roster of Pilot Participants
• CIM3 Engineering (Webhosting)• Oracle Corp (Database, Application Server, WSRP Portal)• RedHat (RedHat Enterprise Linux Operating System)• Humanmarkup.org, Inc. (Public Service Preparedness Portal)• Starbourne Communications Design (Portal Design
Development)• Broadstrokes, Inc. (Reverse 911 Service)• TargusInfo, Inc. (Ceolocation-based Telephone Directory
Service) • MyStateUSA (NIMS-ICS Simulated Network)• WarningSystems, Inc. (EAS, Siren Alerting System)• Sandia National Laboratories (Sensor Network Simulation)• NuParadigm (Alerting Framework Network Services)• Unicorn Solutions, Inc. (Ontology/Data Model Workbench)• ImageMatters, LLC
Top Related