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


Help: OASIS Mailing Lists Help | MarkMail Help

Messages By Date: members message

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

Subject: Public Review of CAP v1.1 IPAWS Profile v1.0

To OASIS members, Public Announce Lists:

The OASIS Emergency Management TC has recently approved the following
specification as a Committee Draft and approved the package for public

Common Alerting Protocol Version 1.1 USA Integrated Public Alert and Warning
System Profile Version 1.0

The public review starts today, 3 March 2009, and ends 2 May 2009. This is
an open invitation to comment. We strongly encourage feedback from potential
users, developers and others, whether OASIS members or not, for the sake of
improving the interoperability and quality of OASIS work. Please feel free
to distribute this announcement within your organization and to other
appropriate mail lists.

More non-normative information about the specification and the technical
committee may be found at the public home page of the TC at 
Comments may be submitted to the TC by any person through the use of the
OASIS TC Comment Facility which can be located via the button marked "Send A
Comment" at the top of that page, or directly at 

Submitted comments (for this work as well as other works of that TC) are
publicly archived and can be viewed at 
http://lists.oasis-open.org/archives/emergency-comment/. All comments
submitted to OASIS are subject to the OASIS Feedback License, which ensures
that the feedback you provide carries the same obligations at least as the
obligations of the TC members.

The specification document and related files are available here:

Editable Source (Authoritative):

The OASIS EM TC requests comments on the advisability of including a
normative XML Schema for the CAP-IPAWS Profile within the CAP IPAWS Profile
Specification. Currently no schema is included and we note that other OASIS
profiles have been completed without schemas. It should be considered
whether the purpose of the profile is better suited by:
- including no schema;
- enforcing restrictions such as those for the <geocode> element; or,
- limiting changes to cardinality, such as requiring that at least one
<eventCode> element be included.

The OASIS EM TC requests comments on the inclusion of the complete IPAWS CAP
v1.1Profile Requirements v2.4 - Public document within the CAP Profile
Specification as non-normative information. Currently a reference to the
document is included as Non-Normative Reference, with an additional note in
Sec 1.6 of the Profile Specification. Comments will help the OASIS EM TC to
validate if the provision of this information will serve to help and inform
users/implementers of the CAP IPAWS Profile.

OASIS and the Emergency Management TC welcome your comments.

Mary P McRae
Director, Technical Committee Administration
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org  
web: www.oasis-open.org
phone: 1.603.232.9090

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