[EAS] The coming evolution of CAP-EAS

[Richard_Rudman]

Thanks, Gary:

As you are apparently suggesting, it may be time to direct this discussion to action items.

Some thoughts:

1. Since the payload for CAP-enhanced EAS messages cannot propagate via legacy EAS, what's to stop us from asking for 
a new code or codes that would be used expressly for CAP messages with data "payloads" ?

2. Planting URL's in CAP messages is an efficient way to point to files that would bog down transmission of the primary  "carrier" message. Files that the URL's point to could be downloaded separately and assembled into completed messages for audiences. Something else new to design and build.

3. Issues like agreeing on the use of ADR and other codes could/should be addressed by an EAS national advisory group built around broad stakeholder representation. Suggested participant stakeholder groups include but may not be limited to SECC's , NASBA, NAB, the EM community, BWWG, and representatives of the hearing and sight impaired communities. 

4. I believe that research and development money is needed to move new ideas for CAP-EAS forward. Money for this as well as training and education should come from funding that would be part of pending legislation. No one to my knowledge has proposed R & D as part of legislative funding yet. Should we propose this?

Keep the ideas coming!

Richard

On Nov 3, 2012, at 5:38 PM, Clay Freinwald wrote:

> One other option I see is a nationwide agreement that something like the ADR
> Administrative Message shall be for non-immediate-broadcast EAS messages.