See copyright information on last page
` Page 1 of 6
`
`
`
`
`
`
`
`
`
`
`
`DRAFT 6/20/2002
`Common Alerting Protocol (CAP) version 0.5a – Alert Message Data Dictionary
`
`future revision as guidelines for common vocabulary emerge.
`urgency, severity and probability, are usable placeholders, subject to
`* An important note: The event types and categories, like the values for
`
`• The XML Schema and a derived Document Type Definition (DTD)
`• The message examples have been removed to separate files.
`• The attribute names for the <cap:affects> tag have changed.
`
`are also posted with this update.
`
`• There have been various changes in the table of types and categories
`
`for the <cap:event> element. *
`
`• The “Recap” value for the <cap:urgency> element has been changed
`
`to “Report”
`
`• Elements are listed in schema order. Required elements are marked
`
`in boldface.
`
`• The sequence of elements has changed (to make it a more logical read
`gained while formalizing the alert message format as an XML schema:
`This is a minor but important update, incorporating a few insights we
`Changes in CAP Version 0.5a
`
`for humans.)
`
`(http://www.w3c.org/XML/)
`users and maintained by the World Wide Web Consortium (W3C).
`Recommendations for XML are developed and refined by a consortium of
`software providers.
`the world today. It is an open, non-proprietary standard shared by all major
`format for exchanging structured data between different computer systems in
`The eXtensible Markup Language (XML) is the most widely accepted
`About the eXtensible Markup Language (XML)
`
`public safety experts.
`through the efforts of a national ad-hoc Working Group of technical and
`The Common Alerting Protocol has been under development since 2001
`
`• Overall “situational awareness” will be enhanced, since CAP will permit
`message will be compatible with all kinds of warning delivery systems.
`
`• Workload on warning issuers will be reduced, since a single warning
`
`comparison and pattern recognition.
`the aggregation of all kinds of warning messages from all sources for
`
`• Warnings to the public will be better coordinated across the wide range
`important benefits for public safety:
`Development and deployment of a standard such as CAP will yield
`all types of hazard warnings and reports.
`systems. The CAP will be designed to facilitate the collection and relay of
`alerts and related information among emergency agencies and public
`proprietary, standards-based data formats for the exchange of emergency
`The Common Alerting Protocol is a draft specification of open, non-
`About the Common Alerting Protocol (CAP)
`
`of available warning and notification systems
`
`1 of 6
`
`IBM EX. 1007
`
`
`DRAFT 6/20/2002
`Common Alerting Protocol (v 0.5a) – Alert Message Data Dictionary
`Common Alerting Protocol Techincal Working Group
`
`

`

`See copyright information on last page
` Page 2 of 6
`
`
`
`
`
`
`
`
`
`
`
`DRAFT 6/20/2002
`Common Alerting Protocol (CAP) version 0.5a – Alert Message Data Dictionary
`
`(more)
`
` “Other”
`“Other”
`type=
`
`“Other”
`“Leak”
`“Service Restriction”
`“Outage”
`“Utility”
`type=
`
`“Other”
`“Special Provision”
`“Special Restriction”
`“Marine Accident”
`“Rail Accident”
`“Aircraft Accident”
`“Vehicle Accident”
`“Transport”
`type=
`
`“Other”
`“Distribution”
`“Quarantine”
`“Multiple Casualty”
`“Casualty”
`Disease”
`“Communicable
`“Air Quality”
`“Water Quality”
`“Hazardous Material”
`“Health”
`type=
`
`“Other”
`“Animal”
`“Emergency Relief”
`“Curfew”
`“Access Control”
`“Evacuation”
`“Abduction”
`“Search and Rescue”
`“Water Rescue”
`“Civil Disturbance”
`“Crime”
`“Structural Failure”
`“Explosion”
`“Flooding”
`“Fire”
`“Safety”
`type=
`
`“Other”
`“Cold”
`“Heat”
`“Dust”
`“Fog”
`“Icing”
`“Blizzard”
`“Snow”
`“Flash Flood”
`“Flooding”
`“Rain”
`“Thunderstorm”
`“Hurricane”
`“Tornado”
`“Wind”
`“Weather”
`type=
`
`“Other”
`“Tsunami”
`“Landslide”
`“Volcano”
`“Earthquake”
`”Geo”
`type=
`Optional attribute “type” sub-categorizes events.
`
`Event Category
`
`cap:event
`
`Text
`
`message originator
`Name or description of
`
`cap:source_desc
`
`domain name)
`Identifies the originator of this alert. Guaranteed by the originator to be unique globally (e.g., may be based on an Internet
`
`This tag should only be used in conjunction with <cap:status> values of “Exercise” or “Test”
`Text
`
`“Test” – Technical testing only, all recipients disregard
`“Admin” – regarding system operations, actionable by operators only
`“Exercise” – actionable only by designated exercise participants, all other recipients disregard
`“Actual” (the default) – this message is actionable
`
`Originator ID
`
`cap:source
`
`handling
`describing appropriate
`Descriptive label
`
`cap:status_desc
`
`handling of message
`Identifies appropriate
`
`cap:status
`
`required if the sender originates more than one message in a single second.
`May include an optional “id” attribute (text, defined by originator) to uniquely identify this particular message. This attribute is
`
`<cap:alert xmlns:cap=”http://www.incident.com/cap”>
`
`Surrounds CAP alert message body. Must reference explicit CAP namespace, thus:
`
`Attributes and Element Contents
`
`msg.
`Envelope tag for alert
`
`cap:alert
`
`Purpose
`
`Tag Name
`
`2 of 6
`
`
`
`

`

`See copyright information on last page
` Page 3 of 6
`
`
`
`
`
`
`
`
`
`
`
`DRAFT 6/20/2002
`Common Alerting Protocol (CAP) version 0.5a – Alert Message Data Dictionary
`
`(more)
`
`message is not longer in effect.)
`Date/Time in ISO 8601 format. (If this item is not provided, each recipient is free to make its own assumption as to when the
`
`no longer valid
`Date/Time when message
`
`provided, or of the mandatory “sent” date/time.)
`Date/Time in ISO 8601 format. (If this item is not included, it is assumed the same as the optional “effective” date/time, if
`
`onset of event
`Date/Time of expected
`
`cap:expires
`
`cap:onset
`
`Date/Time in ISO 8601 format. (If this item is not included, it is assumed the same as the mandatory “sent” date/time.)
`
`Date and time of message origination in ISO 8601 format (e.g., “2002-05-24T16:49:00-07:00” for 24 May 2002 at 16:49 PDT)
`
`information takes effect
`Date/Time the message
`
`cap:effective
`
`was originated
`Date/Time when message
`
`cap:sent
`
`“Unknown” – probability unknown
`“Low” – possible but not unlikely (approx. < 50%)
`“Moderate” – likely (approx. > 50%)
`“High” – highly likely (approx. > 85% probability) or certain
`
`“Unknown” – severity unknown
`“Minor” – minimal threat to life or property
`“Moderate” – possible threat to life or property
`“Severe” – significant threat to life or property
`
`Likeliness of event
`
`cap:probability
`
`Severity of event
`
`cap:severity
`
`“Unknown” – urgency not known
`“Report” – refers to an actual event that occurred in the past (not requiring further action)
`“Forecast” – refers to an event that is moderately probable in the near future
`“Impending” – refers to an event that is imminent (within next hour)
`“Immediate” – refers to an actual event that has occurred recently or is occurring
`
`Text (used to collate multiple messages referring to different aspects of the same incident)
`
`Text (used to collate multiple messages updating or correcting information about the same event)
`
`Attributes and Element Contents
`
`Urgency of this event
`
`cap:urgency
`
`for larger incident
`Originators reference name
`
`cap:incident_id
`
`name for event
`Originator’s reference
`
`Purpose
`
`cap:event_id
`
`Tag Name
`
`3 of 6
`
`
`
`

`

`See copyright information on last page
` Page 4 of 6
`
`
`
`
`
`
`
`
`
`
`
`DRAFT 6/20/2002
`Common Alerting Protocol (CAP) version 0.5a – Alert Message Data Dictionary
`
`
`
`(more)
`
`URL for additional or reference information
`
`information
`additional
`WWW link to
`
`Text
`
`by recipients
`action to be taken
`Recommended
`
`cap:info_url
`
`cap:action
`
`Text description of nature of event (within selected category.) Required if category is “Other”
`
`event
`Description of
`
`cap:event_desc
`
`Text
`
`identify item.
`Brief text “slug” to
`
`Text
`
`for this message
`target audience(s)
`Description of
`
`cap:headline
`
`4 of 6
`
`cap:audience
`
`<affects type="Description">San Bernardino County, California</affects>
`
`Element is a text description of the affected area. E.g.:
`type=”Description”
`
`<affects type="Location">+38.33,-121.55,25</affects>
`
`by a comma and a radius in kilometers. ). E.g.:
`Element is a geographic location described as a comma-delimited latitude / longitude paired (signed and decimal as in “poly”), followed
`type=”Location”
`
`121.31</affects>
`<affects type="Area">+38.33,-121.55,+38.26,-121.34,+38.53,-121.04,+38.70,-
`
`“-“ for South/West) and expressed in decimal degrees (datum is WGS-84). E.g.:
`Element is a GIS polygon described as a comma-delimited string of latitude / longitude pairs. Each value is signed (“+” for North/East,
`type=”Area”
`Attribute ‘type’ is required
`
`Attributes and Element Contents
`
`recommended.)
`alone is not
`the “desc” type
`permitted. Use of
`different types are
`of same or
`required, multiple
`At least one is
`(May be multiple.
`description
`Affected area
`Purpose
`
`cap:affects
`
`Tag Name
`
`

`

`See copyright information on last page
` Page 5 of 6
`
`
`
`
`
`
`
`
`
`
`
`DRAFT 6/20/2002
`Common Alerting Protocol (CAP) version 0.5a – Alert Message Data Dictionary
`
`
`
`(more)
`
`Text, name of organization
`
`Text, title of individual
`
`information
`which can provide more
`Name of organization
`
`information
`provide additional
`Title of individual who can
`
`cap:contact_org
`
`cap:contact_title
`
`Text, name
`
`cap:contact_name Name of individual who
`
`information
`can provide additional
`
`Text
`
`authoritative
`which this contact is
`Specialty or jurisdiction for
`
`cap:contact_role
`
`• Attribute “name” is required: Text name of parameter
`
`Element is the value of the parameter.
`
`associated with event
`Technical parameters
`
`cap:parameter
`
`contact structures
`Envelope tag for point-of-
`
`cap:contact
`
`5 of 6
`
`lang=”KO”>http://www.somebody.gov/audio/audio12345.mp3</audio_url>
`<cap:audio_url desc=”Warning message in Korean”
`
`Example:
`
`• Attribute ‘lang’ is optional: Two-letter ISO language code
`• Attribute ‘desc’ is required: Text description of audio content
`
`Element is the URL of an online audio file.
`
`etc.)
`(recorded announcement,
`Link to digital audio
`
`cap:audio_url
`
`probabilities”>http://www.somebody.gov/image/map12345.gif</image_url>
`<cap:image_url height=”480” width=”640” desc=”Map of strike
`
`Example:
`
`• Attribute ‘lang’ is optional: Two-letter ISO language code
`• Attribute ‘desc’ is required: Text description of image content
`• Attributes “height” and “width” are required: Integer pixels
`
`Element is the URL of an online image file.
`
`Attributes and Element Contents
`
`photo, etc.)
`Link to digital image (map,
`
`Purpose
`
`cap:image_url
`Tag Name
`
`

`

`See copyright information on last page
` Page 6 of 6
`
`
`
`
`
`
`
`
`
`
`
`DRAFT 6/20/2002
`Common Alerting Protocol (CAP) version 0.5a – Alert Message Data Dictionary
`
`Disaster Information Systems, National Science and Technology Council, November 2000.
`This work is based in part on concepts and specifications contained in the 'Effective Disaster Warnings' report by the Working Group on Natural
`of the license is available online at http://www.gnu.org/licenses/fdl.txt
`any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts and no Back-Cover Texts. A copy
`Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or
`Copyright © 2002 Art Botterell (for the Common Alerting Protocol Technical Working Group)
`proprietary development.
`The following copyright claim and licensing statement are made for the sole purpose of ensuring that this work remains freely available for open, non-
`Copyright and Licensing Statement
`
`
`
`
`
`
`
`Other contact mechanism Text (e.g., URL)
`
`cap:contact_other
`
`Text, Internet email address
`
`information
`Email address for more
`
`cap:contact_email
`
`Text, ten-digit telephone number (w. country code if appropriate)
`
`Attributes and Element Contents
`
`more information
`Telephone number for
`
`Purpose
`
`cap:contact_tel
`Tag Name
`
`6 of 6
`
`
`
`