Thanks Frank,
I only speak as an individual, but I am relaying
your message separately to the TC list and the
CAP-Profiles SC list to ensure that your concerns
are heard by those to whom they are most directly
relevant. We can discuss this in both fora,
though I am not sure if we can schedule time in
the next TC and SC meetings to discuss your
suggestions because they are not scoped directly
to the CAP-IPAWS Profile currently in Public
Review, nor to the specific work underway for
CAP. However, your thoughtful work deserves to
considered well.
I'm not sure we as a TC can take on the work you
outline. We should at least discuss it.
I suggest you give thought to passing it along to
the other groups you mention, legislators and
agencies, too. I suspect that enabling
legislation may be advisable, and building a
support base of groups in whose interest this
lies would provide momentum for an effort to be
brought to the TC in a more formal submission.
Thanks again.
Best Regards,
Rex Brooks
At 7:40 AM -0400 4/8/09, FRANK BELL wrote:
>Dear Sirs and Mesdames,
>First, there are some comments attached, largely they are about CAP aspects of
>an improved EAS standard. This proposed standard I am calling EAS+ and I
>hereby give OASIS permission to use this name and the terms "EAS+
>compatibility" and "EAS+ compliance". The copyright control may be by OASIS or
>another organization e.g. FEMA, subject to discussion and relevant legal
>restraints.
>
>A powerpoint presentation is the next attachment which gives some overview of
>EAS+ as it currently stands. This is work in progress, and OASIS is not the
>only relevant standards organization, ATSC is also and perhaps others. Also
>Dolby and Ibiquity are two relevant companies.
>
>The final attachment is a proposed implementation of CAP in EAS+. The latter
>part of the paper, as explained in the introduction, is a manufacturers group
>proposal for EAS. A goal of EAS+ is to be suitable to generate messages that
>can be used to generate valid and appropriate CAP messages. The latter CAP
>messages are not expected to be identical to the source message. The purpose
>of this is that in the event of a failure of the CAP message distribution
>network, an EAS+ message can be the source to get a CAP message through.
>Consumer electronics may take an active role in EAS+ alerting, primarily to
>provide selectivity and also to turn themselves on to give alerts at night or
>other times for example.
>
>Another goal of EAS+ is to be able to carry CAP messages or other push
>broadcast files (e.g. pdf files) to computers via ISPs, corporate or campus
>LANs, etc.
>
>I hope that this submission is in a suitable format and manner of handling, as
>although I am an individual member of OASIS, I would appreciate your
>assistance. I do have other material that can address questions that may
>arise, but at present that does not appear appropriate.
>Sincerely,
>
>Frank W. Bell
>Cp:(973)460-0722
>
frank.w.bell@usa.net>
>Attachment converted: Macintosh HD:OASIS
>comment1 FBell.xls (XLS4/«IC») (01595F98)
>Attachment converted: Macintosh HD:EAS+ Overview.ppt (SLD3/«IC») (01595F99)
>Attachment converted: Macintosh HD:CAP-EAS+2.doc (WDBN/«IC») (01595F9D)
>--
>This publicly archived list offers a means to provide input to the
>OASIS Emergency Management TC.
>
>In order to verify user consent to the Feedback License terms and
>to minimize spam in the list archive, subscription is required
>before posting.
>
>Subscribe:
emergency-comment-subscribe@lists.oasis-open.org>Unsubscribe:
emergency-comment-unsubscribe@lists.oasis-open.org>List help:
emergency-comment-help@lists.oasis-open.org>List archive:
http://lists.oasis-open.org/archives/emergency-comment/>Feedback License:
http://www.oasis-open.org/who/ipr/feedback_license.pdf>List Guidelines:
http://www.oasis-open.org/maillists/guidelines.php>Committee:
>http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency
--
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670