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


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

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

Subject: RE: [emergency] Fwd: [emergency-comment] CAP aspects of EAS standardsdevelopment


Gadfly, Frank?  I think not!

I recall Frank has been on this issue for while now.  Notice that what is really going on here is expediting moving forward within the OASIS process.

Plan A - start a new TC from scratch, discussion list, promoters, sponsors, approval, charter, etc.

Plan B - have existing TC add work to their deliverables and/or form sub-committee.

I believe Frank is thinking Plan B here!
So - having looked at the PPT - I'd ask the following:

1) Is the use case valid?

2) Is the scope correct?

3) Is this something the TC wants to take on?

4) Does this get promoted as a standard delivered by the TC?

5) What is the level of effort to get this done?

6) Can Frank lead this or are there restrictions on him doing that?

I'm not offering up any answers - just scene setting here...
Thanks, DW

-------- Original Message --------
Subject: [emergency] Fwd: [emergency-comment] CAP aspects of EAS
standards development
From: Rex Brooks <rexb@starbourne.com>
Date: Wed, April 08, 2009 9:50 am
To: emergency-cap-profiles@lists.oasis-open.org,

Hi Folks,

First, I don't believe that this is a specific comment on the
CAP-IPAWS Profile, though it is related. It is more of a suggestion
for future work.

I am forwarding this message and attachments from the comments list
because I think it deserves to be understood. I don't necessarily
endorse it, but this is not a casual, whimsical or unqualified
individual submission. I don't think we are the best choice to
consider it, but it was sent respectfully and given clear thought, so
I do think it is worth reviewing. When I first saw it, I was
concerned that it might be an example of the odd gadfly that
occasionally appears in our work and the work of other similar
groups, but it doesn't appear to be that.


>Mailing-List: contact emergency-comment-help@lists.oasis-open.org;
>run by ezmlm
>List-Post: <mailto:emergency-comment@lists.oasis-open.org>
>List-Help: <mailto:emergency-comment-help@lists.oasis-open.org>
>List-Unsubscribe: <mailto:emergency-comment-unsubscribe@lists.oasis-open.org>
>List-Subscribe: <mailto:emergency-comment-subscribe@lists.oasis-open.org>
>Delivered-To: mailing list emergency-comment@lists.oasis-open.org
>X-USANET-Source: IN frank.w.bell@usa.net
>X-USANET-Auth: AUTO frank.w.bell@usa.net cmsweb02.cms.usa.net
>Date: Wed, 08 Apr 2009 07:40:39 -0400
>From: "FRANK BELL" <frank.w.bell@usa.net>
>To: <emergency-comment@lists.oasis-open.org>
>Z-USANET-MsgId: XID433NDHLOn7072X38
>Subject: [emergency-comment] CAP aspects of EAS standards development
>X-Nonspam: Statistical 62%
>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
>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.
>Frank W. Bell
>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

Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:

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