[EAS] The coming evolution of CAP-EAS

[Richard Rudman]

Ed brings up some good points - among them are that the ideas/solutions recently posted -- including my own -- are not seeing the light of day here for the first time. 

My conclusion at this point is that Ed and others from the developer-stakeholder side of things, may have a better understanding of what can be done realistically than any of us.

Questions: 

1. Should CAP-EAS enhancements be thought of in a cross platform context? Should good ideas become standardized, or are we going to continue to see proprietary development create different flavors of EAS that may not play well together? 

2. Do ideas we have discussed here (and more) need to be advanced through further development and testing, or are they ready now?

3. If developer "A" can implement a good idea and developer "B" cannot, what happens?

4. Is there a need for funding for further development and "play nice" testing by FEMA (and FCC)? 

5. Will developers continue to pour $$ into enhancements?

6. If the answer to the question 4 is "yes", and the answer to question 5 is "no", and assuming that FEMA and FCC dollars for this are not there, where will the dollars come from?  

7. Should we take seriously the word "Integrated" that FEMA planted in their IPAWS acronym and apply it as much as possible?

I have more questions. Wish I had more answers right now...

Richard 

On Nov 3, 2012, at 8:13 PM, Ed Czarnecki wrote:

> Let's be careful of definitions here.  IPAWS is one CAP dissemination system
> that, to my knowledge, focuses on public scope warning messages.  Other CAP
> systems out there are currently capable of disseminating messions with a
> narrower scope (restricted or private), or non-EAS messaging.