CAP 1.2 OS Submission
May 15, 2010
Table of Contents
1 Link to
approved committee specification. 2
2 Editable
version of all files. 2
3
Certification that all schema are valid. 2
4
English-language summary. 2
5 Statement of
relationships to other standards. 2
6 Statements
of Use. 2
7 Public
review. 3
8 Results of
voting. 3
9 Earlier
attempts to standardize. 3
10 Publicly visible
comments archive. 3
11 Committee
specification minority reports. 3
1 Link to
approved committee specification
http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/37820/CAP-v1.2-CS01.doc
2 Editable
version of all files
http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/37822/CAP-v1.2-CS01-files.zip
3 Certification
that all schema are valid
The Committee certifies
that all schema and XML instances are well-formed to the best of of its
knowledge, and have been tested to establish validity.
4
English-language summary
The Common Alerting
Protocol (CAP) is a simple but general format for exchanging all-hazard
emergency alerts and public warnings over all kinds of networks. CAP allows a
consistent warning message to be disseminated simultaneously over many
different warning systems, thus increasing warning effectiveness while
simplifying the warning task. CAP also facilitates the detection of emerging
patterns in local warnings of various kinds, such as might indicate an
undetected hazard or hostile act.
5 Statement
of relationships to other standards
The relationships to
other standards are inclusions and references noted in the Related Work and
Normative References section of the specification, which includes previous
versions of CAP. CAP is also a component of a larger framework, the
Emergency Data Exchange Language family of standards.
6 Statements
of Use
These three OASIS member
companies have certified that they are using CAP 1.2:
Warning Systems, Inc.
http://www.oasis-open.org/apps/org/workgroup/emergency/email/archives/201004/msg00029.html
Evolution Technologies
http://www.oasis-open.org/apps/org/workgroup/emergency/email/archives/201004/msg00032.html
Mitre Corp
http://www.oasis-open.org/apps/org/workgroup/emergency/email/archives/201004/msg00031.html
7 Public
review
Public Review 01 - 28 May
2009 to 27 July 2009
http://lists.oasis-open.org/archives/emergency/200905/msg00055.html
Comments: http://www.oasis-open.org/apps/org/workgroup/emergency-msg/download.php/34254/CAPv1.2-PR01-IssuesList-5.xls
Public Review 02 - 8 November 2009 to 23 November 2009
http://lists.oasis-open.org/archives/emergency/200911/msg00007.html
Comments: http://www.oasis-open.org/apps/org/workgroup/emergency-msg/download.php/36664/CAPv1.2-PR02-IssuesList-4.xls
Public Review 03 - 24 March 2010 to 8 April 2010
http://lists.oasis-open.org/archives/emergency/201003/msg00129.html
No comments submitted.
8 Results of
voting
The ballot to approve CAP
1.2 as a Committee Specification closed May 3, 2010.
Of the 19 eligible voting members, 15 voted Yes, 1 voted Abstain, and 3 did not
vote.
http://www.oasis-open.org/apps/org/workgroup/emergency/ballot.php?id=1867
9 Earlier
attempts to standardize
CAP 1.0 and 1.1 were
successfully standardized. There have been no previous attempts to standardize
CAP 1.2.
10 Publicly visible comments archive
http://lists.oasis-open.org/archives/emergency-comment/
11 Committee specification minority reports
There were no minority reports indicating disapproval.
At 09:07 PM 5/15/2010, Mary McRae wrote:
Please send plain text in the body of an email message. Thanks!
Mary
On May 15, 2010, at 5:45 PM, Elysa Jones wrote:
> Dear Mary,
>
> The Emergency Management Technical Committee is ready for the CAP 1.2 OS
Submission. The ballot where the TC agreed to bring this Committee
Specification to an OASIS-wide vote can be found at http://www.oasis-open.org/apps/org/workgroup/emergency/ballot.php?id=1870
>
> Please find the submission document attached.
>
> Best regards,
>
> Elysa Jones, Chair
> OASIS EM-TC
> CTO Warning Systems, Inc.<CAP-1.2-submission.doc>