Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
Cap Ones Iscram09
1. CAP-ONES: An Emergency
Notification System for all
Alessio Malizia, Pablo Acuña, Teresa Onorati, Paloma Díaz,
Ignacio Aedo
DEI Lab
Departamento de Informática
Universidad Carlos III de Madrid, Spain
{amalizia, pacuna, tonorati, pdp}@inf.uc3m.es,
aedo@ia.uc3m.es
12/05/2009
Gothenburg ISCRAM 2009
3. Introduction
• Emergency Notification Systems (ENS) for
communicating alerts in emergency situations.
• Accessible notifications depend on peopleʼs abilities,
device characteristics and kind of emergency.
• ENSs must adapt notifications to the most appropiate
media and format to support alerts for all.
12/05/2009
Gothenburg ISCRAM 2009
4. Introduction (2)
• Keynote talk today - Martha Grabowski
– Situational awareness
• Situational disabilities
– Smoke during a fire can cause low vision problem
• Accessibility (be aware of the alert)
12/05/2009
Gothenburg ISCRAM 2009
5. Introduction (3)
• Common Alerting Protocol (CAP) provides a conceptual
framework to achieve interoperability.
– FEMA Announces Intention To Adopt Common Alerting Protocol 1.1
– Emergency Management Committee seeks feedback from CAP users
– U.S. National Weather Service Starts Multi-Phase CAP Improvement Project
– US Department of Homeland Security: quot;CAP Keeps Nation Steps Ahead of
Disasterquot;
– U.S. Congressional Report Recognizes CAP
• We have developed a knowledge base in the form of an
ontology
• We have built a system that:
– reasons over the ontology
– to generate the most adequate notification
– according to the user, the emergency and the device features.
12/05/2009
Gothenburg ISCRAM 2009
6. The SEMA4A Ontology
• Simple Emergency Alerts fo[u]r All interrelate knowledge
in the emergency alert space.
• SEMA4A is formed by three main classes linked through
a number of relations among their subclasses:
– EMEDIA: contains concepts and relations about emergencies
and media technologies.
– WAfA: contains concepts and relations needed to model
organization, structure and navigation of information.
– AccessOnto: contains information related to Web accessibility
guidelines, userʼs profiles and actions that users can perform.
• Malizia, A., Astorga, F., Onorati, T., Diaz, P., Aedo I.: “Emergency Alerts for All: an Ontology
based Approach to Improve Accessibility in Emergency Alerting Systems”. ISCRAM 5th
International Conference Information Systems for Crisis Response and Management, 2008, pp.
197-207.
12/05/2009
Gothenburg ISCRAM 2009
7. The SEMA4A Ontology(2)
Internet communication capabilities
Guidelines for deafblind
12/05/2009
Gothenburg ISCRAM 2009
8. CAP-ONES
• Common Alerting Protocol-based Open Notification
Emergency System, takes as basis SEMA4A ontology
and creates automatically personalized emergency
notifications.
SMS
MMS
Profiles
.
…PARSING… ...PROCESSING...
. Personalized notifications
.
Information parsing
SEMA4A Ontology
CAP Alerts
12/05/2009
Gothenburg ISCRAM 2009
10. CAP-ONES: Alerts
• The emergency information is extracted from a CAP alert,
containing data like source, status, description, location,
etc.
• Our prototype supports entering information via a Web
page, importing a CAP file or providing an URL pointing
to one.
12/05/2009
Gothenburg ISCRAM 2009
11. CAP-ONES: Profiles
• The profiles file is the second input, including:
– Personal and Contact Information: name, address, etc.
– Abilities: level of userʼs abilities (low, medium or high) in 6
categories (Cognitive, Hearing, Coordination, Tactile Sensation,
Visual and Colour) codified in the ontology.
– Devices: a selection from a list of possible devices according to
the userʼs abilities, extracted from relations defined in the
ontology.
12/05/2009
Gothenburg ISCRAM 2009
13. CAP-ONES: Ontology Queries
• Using the information from the profiles and the
emergency, SPARQL queries are executed on the
ontology:
1. Retrieve the media that can be used by this emergency, using
the RDF property mayUse defined in SEMA4A.
2. Retrieve what can be communicated through the media
obtained in step 2, using the RDF property can-communicate
defined in the ontology.
3. For each profile, obtain the media and devices that the user is
able to manage depending on his/her abilities, previously
obtained when entering the profile with the system.
12/05/2009
Gothenburg ISCRAM 2009
15. CAP-ONES: Notifications
• Using the set of media and the set of devices that can be
used for the emergency defined in the CAP message,
• Using the media and devices for each profile,
• A final result set per profile is computed with the
intersection of these sets.
• The notification is created by selecting the appropiate
content from the CAP alert, according to the media and
devices contained in the final result set.
12/05/2009
Gothenburg ISCRAM 2009
16. Use Cases
• Profile: using our system, a “low hearing” and a “blindness”
profile are entered, corresponding to the Deafness and
Blindness class in our ontology.
User abilities Selecting Devices
• Emergency alert: a CAP XML message of an earthquake
(class Earthquake in SEMA4A), including an auxiliar image
resource, and a geographical location of the emergency.
12/05/2009
Gothenburg ISCRAM 2009
17. Use Cases (2)
• Our system response is the following:
– Profile Deafness may use the following media classes (from
interface): [Figure, Text, mms, email, sms, vibration]
– Profile Blindness may use the following media classes:
[Sound, Text, mms, email, sms, vibration]
– By querying the ontology, class Earthquake may use the media:
[tv, radio, mobile_phone, phone, internet];
and can-communicate the following set: [Video, Sound,
multiple_languages, Figure, Text, mms, email, sms, vibration]
– Making an intersection with the sets, we get that e-mail, sms and
mms are feasible to send notifications in this situation.
– Personalization: the CAP message contains an image and a
geographical location (that can be shown using figures), we validate
this against our results. Since the emergency can-communicate
Figures, as well as the Deafness profile, so a link to Google Maps™
pointing to the location can be added to an e-mail; however, this is
not added in the Blindness profile, since Figures can not be used.
12/05/2009
Gothenburg ISCRAM 2009
19. Use Cases (4)
• Our system also allows sending SMS/MMS to users.
Since the emergency CAP message contained an
image, we may use a MMS to send it as an auxiliar
resource. As mentioned before, the Deafness profile can
use MMS and Figures; however, the Blindness profile
only allows sms.
MMS sent to SMS sent to
Deafness Profile Blindness Profile
12/05/2009
Gothenburg ISCRAM 2009
20. Conclusions
• We presented CAP-ONES, a prototype for adapting alert
notifications to different kinds of users depending on their
abilities, the kind of emergency and the devices they can
access.
• Our system supports the CAP standard, for allowing
interoperability with existing systems, e.g. EDIS
(http://edis.oes.ca.gov/)
• Our system is based on SEMA4A ontology, that has proven to
contain valid and useful concepts and relations.
– Validate by experts (Sidar, Civil Protection)
• This is a first step towards a system that could automatically
adapt alert notifications and interoperate with other systems.
12/05/2009
Gothenburg ISCRAM 2009
21. Future Works
• Extend the ontology to other classes
– Situational disabilities, new kind of devices
• Test with scenario and users
12/05/2009
Gothenburg ISCRAM 2009
22. SPARQL Query
• SPARQL query example: to obtain the devices and media for a
specific emergency class (e.g. Earthquake):
SELECT DISTINCT ?mayUse WHERE {
:earthquake rdfs:subClassOf ?restrict ;
rdfs:subClassOf :Emergency .
?restrict rdf:type owl:Restriction ; owl:onProperty
:mayUse ;
owl:someValuesFrom ?emgMayUse .
?emgMayUse rdfs:subClassOf ?emgMayUseClass .
?emgMayUseClass owl:onProperty :can-communicate ;
owl:someValuesFrom ?mayUse }
• This query takes the earthquake class, a subclass of Emergency,
and retrieves the object values from property mayUse, which gets
the media that can be used for this emergency; from these media,
the query retrieves the object values from property can-
communicate in order to obtain the tools that can be used to send
the notification.
12/05/2009
Gothenburg ISCRAM 2009
23. Ontology Validation
• The expert on accessibility evaluated, totally, 155
elements extracted from our ontology.
• Results were:
– • Coverage 91% (have all the lexons to be discovered actually been
discovered?)
– • Precision 84% (are the lexons making sense for the domain?)
– • Accuracy 79% (are the lexons not too general but reflecting the
important terms of the domain?).
• The expert on emergency evaluated, in total, 265
elements extracted from our ontology.
• Results were:
– • Coverage 66%
– • Precision 65%
– • Accuracy 45%
12/05/2009
Gothenburg ISCRAM 2009
