[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: [CAP] The "User Experience" of Warnings in E AS
HI Everyone, I think this message has some significant points we need to be aware of as we collect issues related to the CAP work we will take up again. Cheers, Rex >From: Art Botterell <acb@incident.com> >To: cap-list@lists.incident.com >Date: Thu, 8 May 2008 19:29:36 -0700 >Subject: [CAP] The "User Experience" of Warnings in E > AS >X-BeenThere: cap-list@lists.incident.com >List-Id: Common Alerting Protocol Public Discussion > <cap-list.lists.incident.com> >List-Unsubscribe: <http://eastpac.incident.com/mailman/options/cap-list>, > <mailto:cap-list-request@lists.incident.com?subject=unsubscribe> >List-Archive: <http://eastpac.incident.com/pipermail/cap-list> >List-Post: <mailto:cap-list@lists.incident.com> >List-Help: <mailto:cap-list-request@lists.incident.com?subject=help> >List-Subscribe: <http://eastpac.incident.com/mailman/listinfo/cap-list>, > <mailto:cap-list-request@lists.incident.com?subject=subscribe> >Sender: cap-list-bounces@lists.incident.com >X-Nonspam: Statistical 62% > >Apologies for cross-posting myself, but I think these questions are >going to be important to the whole CAP community, not just >broadcasters... - Art > >http://www.incident.com/blog/?p=50 >---------------------------------- >The User Experience of Warnings in EAS >May 8th, 2008 > >In the runup to the May 19th EAS Showdow um Summit in Washington, >DC, most of the discussion has focused on the nuts and bolts of >moving the nations broadcast alerts across digital networks based >on CAP. > >But CAP only defines the information payload of a warning. It >doesnt specify how that information should be presented over HD >radio, digital TV, computers, PDAs, digital signage or any of our >various other windows into the infosphere. > >This is going to become a crucial question in the very near future, >I think. As digitization drives broadcast content onto ever more >diverse platforms were going to need to give these >presentation/user interface issues as much attention as we have to >transport/relay-network design. > >We may want to develop some common elements consistent visual, >aural, even tactile (e.g., portable device vibrator cadences) cues >that one might almost call branding elements to ensure that >emergency alerts have a degree of consistency across all media. >Otherwise we risk letting diversity deteriorate into confusion. > >The Australians have made an interesting foray in that direction >with their Standard Emergency Warning Signal (SEWS) basically a >standard sounder that can be used consistently over broadcast, >wireless, wireline and even acoustical (siren and public address) >delivery systems. However they havent tried yet to set a comparable >standard in the visual or other domains. > >Last year the FCCs cellular alerting advisory committee (the >CMSAAC) took a few first steps toward designing a consistent user >experience for a basic text-messaging interface. > >But as we start talking about digital television and HD radio and >the things that lie beyond them, were going to need to bring some >real world-class user-interface expertise to bear alongside our >enormous pool of transmission engineering experience. > >The Common Alerting Protocol (CAP) provides a rich standard data >payload that can be presented hopefully consistently over all >media, broadcast and otherwise. But the details of how best to >present that richer message are still to be determined and require >immediate skilled attention. >_______________________________________________ >This list is for public discussion of the Common Alerting Protocol. >This list is NOT part of the formal record of the OASIS Emergency >Management TC. Comments for the OASIS record should be posted using >the form at >http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=emergency >CAP-list mailing list >CAP-list@lists.incident.com >http://eastpac.incident.com/mailman/listinfo/cap-list > >This list is not for announcements, advertising or advocacy of any >particular program or product other than the CAP itself. -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-898-0670
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]