Common Alerting Protocol Version 1.1
Approved Errata
2 October 2007
Specification URIs:
This Version:
http://docs.oasis-open.org/emergency/cap/v1.1/errata/approved/CAP-v1.1-errata.html
http://docs.oasis-open.org/emergency/cap/v1.1/errata/approved/CAP-v1.1-errata.doc
http://docs.oasis-open.org/emergency/cap/v1.1/errata/approved/CAP-v1.1-errata.pdf
Previous Version:
http://docs.oasis-open.org/emergency/cap/v1.1/errata/pr01/CAP-v1.1-errata-pr01.html
http://docs.oasis-open.org/emergency/cap/v1.1/errata/pr01/CAP-v1.1-errata-pr01.doc
http://docs.oasis-open.org/emergency/cap/v1.1/errata/pr01/CAP-v1.1-errata-pr01.pdf
Latest Version:
http://docs.oasis-open.org/emergency/cap/v1.1/errata/CAP-v1.1-errata.html
http://docs.oasis-open.org/emergency/cap/v1.1/errata/CAP-v1.1-errata.doc
http://docs.oasis-open.org/emergency/cap/v1.1/errata/CAP-v1.1-errata.pdf
Technical Committee:
Chair(s):
Elysa Jones, Warning Systems
Editor(s):
Elysa Jones, Warning Systems
Related work:
This specification is related to:
Related Schema:
http://docs.oasis-open.org/emergency/cap/v1.1/errata/approved/cap.xsd
http://docs.oasis-open.org/emergency/cap/v1.1/errata/approved/cap-v1.1-asn.1.asn
Abstract:
This document lists errata for the OASIS Common Alerting Protocol Version 1.1 OASIS Standard produced by the Emergency Management Technical Committee. The standard was approved by the OASIS membership on 1 October 2005.
Status:
This document was last revised or approved by the Emergency Management TC on the above date. The level of approval is also listed above. Check the "Latest Version" or "Latest Approved Version" location noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical Committee's email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committee's web page at http://www.oasis-open.org/committees/emergency/.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/emergency/ipr.php.
The non-normative errata page for this specification is located at http://docs.oasis-open.org/committees/emergency/.
Notices
Copyright © OASIS® 1993-2007.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The names "OASIS", "Common Alerting Protocol", and "CAP" are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.
Table of Contents
1.1 Section 1.6 Normative References. 5
1.2 Correction to Section 3.4. 5
1.3 Add Section 3.5 for ASN.1. 5
Added the following Normative References to support an equivalent ASN.1 representation of the CAP message
ITU-T X.680 ITU-T Recommendation X.680, Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation.
ITU-T X.691 ITU-T Recommendation X.691, Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER).
ITU-T X.693 ITU-T Recommendation X.693, Information technology - ASN.1 encoding rules: Specification of XML Encoding Rules (XER).
ITU-T X.694 ITU-T Recommendation X.694, Information technology - ASN.1 encoding rules: Mapping W3C XML schema definitions into ASN.1.
Insert <enumeration value = "Assess"/ "> to <element name = "responseType"… in the .xsd files section of the specification around line 337.
3.5 Use of ASN.1 to Specify and Encode the CAP Alert Message
The ASN.1 (see ITU-T Rec X.680) schema in 3.5.3 provides an alternative formulation of the XML schema defined in 3.4. If the ASN.1 Extended XML Encoding Rules (see ITU-T Rec X.693) are applied to this ASN.1 schema, the permitted XML is identical to that supported by the XML schema in 3.4. If the ASN.1 Unaligned Packed Encoding Rules (see ITU-T Rec X.691) are applied to it, the resulting binary encodings are more compact than the corresponding XML encodings.
3.5.2 Formal Mappings and Specification
The normative specification of the compact binary encoding is in 3.5.3 with the application of the ASN.1 Unaligned Packed Encoding Rules (see ITU-T Rec. X.691).
The semantics of the fields in the ASN.1 specification are identical to those of the XSD specification, and the mapping of the fields from the XSD specification to the ASN.1 specification is formally defined in ITU-T Rec. X.694.
Implementations can produce and process the CAP alert XML messages using either ASN.1-based or XSD-based tools (or other ad hoc software).
Implementations can produce and process the CAP alert compact binary messages using ASN.1-based tools (or by other ad hoc software).
Any XML encoded CAP alert messages can be converted to compact binary messages by decoding with an ASN.1 tool configured for the Extended XML Encoding Rules and re-encoding the resulting abstract values with an ASN.1 tool configured for Unaligned Packed Encoding Rules.
Any compact binary CAP alert messages can be converted to XML encoded messages by decoding with an ASN.1 tool configured for Unaligned Packed Encoding Rules and re-encoding the resulting abstract values with an ASN.1 tool configured for Extended XML Encoding Rules.
CAP-1-1 {itu-t recommendation x cap(1303) version1-1(1)}
DEFINITIONS XER INSTRUCTIONS AUTOMATIC TAGS ::=
-- CAP Alert Message (version 1.1)
BEGIN
Alert ::= SEQUENCE {
identifier IdentifierString,
-- Unambiguous identification of the message
-- from all messages from
-- this sender, in a format defined by the sender and
-- identified in the "sender" field below.
sender String,
-- The globally unambiguous identification of the sender.
-- This specification does not define the root of
-- a global identification tree (there is no international
-- agreement on such a root), so it relies
-- on human-readable text to define globally and
-- unambiguously the sender.
-- An internet domain name or use of "iri:/ITU-T/..."
-- are possible, but
-- the choice needs to be clearly stated in human-readable form.
sent DateTime,
status AlertStatus,
msgType AlertMessageType,
source String OPTIONAL,
-- Not standardised human-readable identification
-- of the source of the alert.
scope AlertScope,
restriction String OPTIONAL,
-- Not standardised human-readable restrictions
-- on the distribution of the alert message
addresses String OPTIONAL,
-- A space separated list of addressees for private messages
-- (see 3.2.1)
code-list SEQUENCE SIZE((0..MAX)) OF code String,
-- A sequence codes for special handling
-- (see 3.2.1)
-- The format and semantics of the codes are not defined in this
-- specification.
note String OPTIONAL,
-- Not standardised human-readable clarifying text for the alert
-- (see 3.2.1)
references String OPTIONAL,
-- Space-separated references to earlier messages
-- (see 3.2.1)
incidents String OPTIONAL,
-- Space-separated references to related incidents
-- (see 3.2.1)
info-list SEQUENCE SIZE((0..MAX)) OF info AlertInformation }
AlertStatus ::= ENUMERATED {
actual,
draft,
exercise,
system,
test }
AlertMessageType ::= ENUMERATED {
ack,
alert,
cancel,
error,
update }
AlertScope ::= ENUMERATED {
private,
public,
restricted }
AlertInformation ::= SEQUENCE {
language Language -- DEFAULT "en-US" -- ,
-- The language used in this value of the Info type
-- (see 3.2.2)
category-list SEQUENCE (SIZE(1..MAX)) OF
category InformationCategory,
event String,
-- Not standardised human-readable text describing the
-- type of the event (see 3.2.2)
responseType-list SEQUENCE SIZE((0..MAX)) OF
responseType InformationResponseType,
urgency HowUrgent,
severity HowSevere,
certainty HowCertain,
audience String OPTIONAL,
-- Not standardised human-readable text describing the
-- intended audience for the message (see 3.2.2)
eventCode-list SEQUENCE SIZE((0..MAX)) OF eventCode SEQUENCE {
valueName ValueName,
value Value },
effective DateTime OPTIONAL,
onset DateTime OPTIONAL,
expires DateTime OPTIONAL,
senderName String OPTIONAL,
-- Not standardised human-readable name of the authority
-- issuing the message (see 3.2.2)
headline String (SIZE (1..160,...)) OPTIONAL,
-- Not standardised human-readable short statement (headline)
-- of the alert (see 3.2.2)
description String OPTIONAL,
-- Not standardised human-readable extended description of
-- the event (see 3.2.2)
instruction String OPTIONAL,
-- Not standardised human-readable recommended action
-- (see 3.2.2)
web AnyURI OPTIONAL,
contact String OPTIONAL,
-- Not standardised human-readable contact details for
-- follow-up (see 3.2.2)
parameter-list SEQUENCE SIZE((0..MAX)) OF parameter SEQUENCE {
-- System-specific parameters (see 3.2.2)
valueName ValueName,
value Value },
resource-list SEQUENCE SIZE((0..MAX)) OF resource ResourceFile,
area-list SEQUENCE SIZE((0..MAX)) OF Area }
InformationCategory ::= ENUMERATED {
cBRNE,
env,
fire,
geo,
health,
infra,
met,
other,
rescue,
safety,
security,
transport }
InformationResponseType ::= ENUMERATED {
assess,
evacuate,
execute,
monitor,
none,
prepare,
shelter }
HowUrgent ::= ENUMERATED {
expected,
future,
immediate,
past,
unknown }
HowSevere ::= ENUMERATED {
extreme,
minor,
moderate,
severe,
unknown }
HowCertain ::= ENUMERATED {
likely,
observed,
possible,
unknown,
unlikely }
ResourceFile ::= SEQUENCE {
-- Information about an associated resource file
-- (see 3.2.3)
resourceDesc String,
-- Not standardised human-readable description of the type
-- and content of
-- an associated resource file (for example a map or
-- photograph)(see 3.2.3)
mimeType String OPTIONAL,
size INTEGER OPTIONAL, -- In bytes
uri AnyURI OPTIONAL,
derefUri String OPTIONAL,
-- An alternative to the URI giving the Base64-encoded
-- content of the resource file (see 3.2.3)
digest String OPTIONAL
-- SHA-1 hash of the resource file for error detection
-- (see 3.2.3) -- }
Area ::= SEQUENCE {
-- Identification of an affected area
areaDesc String,
-- Not standardised human-readable description of the area
polygon-list SEQUENCE OF polygon String,
-- Each element is a space-separated list of coordinate pairs
-- The complete list starts and ends with the same point and
-- defines the polygon that defines the area
-- (see 3.2.4).
circle-list SEQUENCE OF circle String,
-- A space-separated list of coordinates for a point and a radius
geocode-list SEQUENCE SIZE((0..MAX)) OF geocode SEQUENCE {
-- A geographic code designating the alert target area
-- (see 3.2.4)
valueName ValueName,
value Value },
altitude String OPTIONAL,
-- Specific or minimum altitude of the affected area
ceiling String OPTIONAL
-- Maximum altitude of the affected area -- }
ValueName ::= String -- A not standardised name for
-- an information event code, a parameter or a geocode
Value ::= String -- The value of the information event code,
-- parameter or geocode
String ::= UTF8String (FROM (
{0,0,0,9} -- TAB
| {0,0,0,10} -- CR
| {0,0,0,13} -- LF
| {0,0,0,32}..{0,0,215,255} -- Space to the start of the S-zone
| {0,0,224,0}..{0,0,255,253} -- Rest of BMP after S-zone
| {0,1,0,0}..{0,16,255,253} -- Other planes -- ) )
StringChar ::= String (SIZE(1))
SpaceAndComma ::= UTF8String (FROM (
{0,0,0,32} -- SPACE
| {0,0,0,44} -- COMMA -- ) )
IdentifierString ::= String (FROM (StringChar EXCEPT SpaceAndComma))
Language ::= VisibleString(FROM ("a".."z" | "A".."Z" | "-" | "0".."9"))
(PATTERN "[a-zA-Z]#(1,8)(-[a-zA-Z0-9]#(1,8))*")
-- The semantics of Language is specified in IETF RFC 3066
DateTime ::= TIME (SETTINGS "Basic=Date-Time Date=YMD
Year=Basic Time=HMS Local-or-UTC=LD")
-- This is the ISO 8601 format using local time and a
-- time difference
StringWithNoCRLFHT ::= UTF8String (FROM (
{0,0,0,32}..{0,0,215,255}
|{0,0,224,0}..{0,0,255,253}
|{0,1,0,0}..{0,16,255,255}))
AnyURI ::= StringWithNoCRLFHT (CONSTRAINED BY {
/* Shall be a valid URI as defined in IETF RFC 2396 */})
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
GLOBAL-DEFAULTS CONTROL-NAMESPACE
"http://www.w3.org/2001/XMLSchema-instance" PREFIX "xsi"
NAMESPACE ALL, ALL IN ALL AS "urn:oasis:names:tc:emergency:cap:1.1"
PREFIX "cap"
NAME Alert, Area AS UNCAPITALIZED
UNTAGGED SEQUENCE OF
DEFAULT-FOR-EMPTY AlertInformation.language AS "en-US"
TEXT AlertStatus:ALL,
AlertMessageType:ALL,
AlertScope:ALL,
InformationCategory:ALL,
InformationResponseType:ALL,
HowUrgent:ALL,
HowSevere:ALL,
HowCertain:ALL AS CAPITALIZED
WHITESPACE Language, AnyURI COLLAPSE
END