OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

members message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: FW: CAP v1.1 submitted for OASIS Standard


OASIS Members:

The OASIS Emergency Management TC has submitted the following 
specification, which is an approved Committee Specification, to 
be considered as an OASIS Standard:

Common Alerting Protocol (CAP) v1.1

The TC's submission is attached below.

In accordance with the OASIS Technical Committee Process, 
the specification has already gone through a 60 day public 
review period:
http://lists.oasis-open.org/archives/tc-announce/200505/msg00006.html
OASIS members now have until the 15th of September to 
familiarize themselves with the submission below. OASIS 
members should give their input on this question to the 
voting representative of their organization.

By the 16th of the month we will send out a Call For Vote 
to the voting representatives of the OASIS member 
organizations, who will have until the end of the month 
to cast their ballots on whether this Committee Specification 
should be approved as an OASIS Standard.

The normative TC Process for approval of Committee 
Specifications as OASIS Standards is found at
http://www.oasis-open.org/committees/process.php#3.4

Any statements related to the IPR of this specification are posted at:
http://www.oasis-open.org/committees/emergency/ipr.php

Mary

Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org
phone: 603.232.9090


----------------------------------

Submission for OASIS Standard Vote

   1. Links to the approved Committee Specification in the 
TC's document repository.

http://www.oasis-open.org/committees/download.php/14204/emergency-CAPv1.1-Committee%20Specification.pdf

   2.  The editable version of all files that are part of 
the Committee Specification

http://www.oasis-open.org/committees/download.php/14205/emergency-CAPv1.1-Committee%20Specification.doc

   3.  Certification by the TC that all schema and XML 
instances included in the specification, whether by inclusion 
or reference, including fragments of such, are well formed, 
and that all expressions are valid;

The Committee certifies that all schema are valid to the best 
of of its knowledge, and have been tested to establish validity.

   4. A clear English-language summary of the specification;

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.  A statement regarding the relationship of this 
specification to similar work of other OASIS TCs or other 
standards developing organizations

The only known relationships to other standards are inclusions 
and references noted in the Normative References section of 
the specification, and the expectation that in the future CAP 
may become a component of a larger framework, such as the 
Emergency Data Exchange Language.

   6.  Certification by at least three OASIS member 
organizations that they are successfully using the 
specification;

These OASIS member companies have certified that they are 
using CAP 1.1:

Warning Systems, Inc.
http://www.oasis-open.org/archives/emergency/200508/msg00185.html
Anteon
http://www.oasis-open.org/archives/emergency/200508/msg00194.html
Innovative Emergency Management
http://www.oasis-open.org/archives/emergency/200508/msg00187.html


   7.  The beginning and ending dates of the public review(s), 
a pointer to the announcement of the public review(s), and a 
pointer to an account of each of the comments/issues raised 
during the public review period(s), along with its resolution;

The public review was held:
May 16 to July 15, 2005
http://lists.oasis-open.org/archives/tc-announce/200505/msg00006.html
Comment log:
http://www.oasis-open.org/committees/download.php/14206/CAP_1.1_Issues_7-22-05-2.xls

   8.  An account of and results of the voting to approve the 
specification as a Committee Specification, including the date 
of the ballot and a pointer to the ballot;

The ballot was opened to committee members on August 5, and 
closed on August 12, 2005. Results of the voting can be found here:
http://www.oasis-open.org/committees/ballot.php?id=823

   9.  An account of or pointer to votes and comments received 
in any earlier attempts to standardize substantially the same 
specification, together with the originating TC's response to 
each comment;

CAP 1.0 was successfully standardized in March of 2004. There 
have be no previous attempts to standardize CAP 1.1.

  10.  A pointer to the publicly visible comments archive for 
the originating TC;

http://lists.oasis-open.org/archives/emergency-comment/

  11.  A pointer to any minority reports submitted by one or 
more Members who did not vote in favor of approving the 
Committee Specification.

There are no minority reports.

Elysa Jones,
Chair, OASIS Emergency Management TC



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]