[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: CAP Implementation Workshop on Identifiers
This is a repost of the message sent to the list 5/14. Elysa >Delivered-To: 108-ejones@warningsystems.com >X-Mailer: Novell GroupWise Internet Agent 8.0.0 >Date: Fri, 15 May 2009 10:26:31 +0200 >From: "Eliot Christian" <EChristian@wmo.int> >To: <echristian@usgs.gov> >Subject: CAP Implementation Workshop on Identifiers >X-pstn-neptune: 0/0/0.00/0 >X-pstn-levels: (S:99.90000/99.90000 CV: 5.2766 FC:95.5390 >LC:95.5390 R:95.9108 P:95.9108 M:87.7820 C:99.5902 ) >X-pstn-settings: 5 (2.0000:2.0000) s CV gt3 gt2 gt1 r p m c >X-pstn-addresses: from <EChristian@wmo.int> [419/14] > > >Together with the International Telecommunication Union (ITU) >and OASIS (the Organization for the Advancement of Structured >Information Standards), the World Meteorological Organization >(WMO) will host a small, single-issue workshop at the WMO >building in Geneva, 22-23 June 2009. The Document Plan with >meeting details and information about the venue is available at > >http://www.wmo.int/pages/prog/www/ISS/Meetings/WIS-CAP_Geneva2009/DocPlan.html > >This workshop will focus on best practices among implementers >in the matter of identifiers associated with Common Alerting >Protocol (CAP, ITU Recommendation X.1303) messages. This >CAP Implementation Workshop on Identifiers supports actions >from the December 2008 CAP Implementation Workshop (see >http://www.wmo.int/pages/prog/www/ISS/Meetings/WIS-CAP_Geneva2008/DocPlan.html >) > >Participants in this Workshop will also meet jointly with >participants in the MeteoAlarm Workshop on the morning of >June 23 in the same building. > >CAP Background > >CAP is a simple and general format for emergency alerting and >public warning. CAP is designed for "all-hazards", addressing >weather events, earthquakes, tsunami, volcanoes, public health, >power outages, and many other emergencies. CAP is also designed >for "all-media", addressing communications media ranging from >sirens to cell phones, faxes, radio, television, and various >digital communication networks including the Internet. > >The standard CAP format enables consistent alerts for any kind >of emergency simultaneously over many different alerting systems, >thus increasing effectiveness while simplifying the alerting task. >CAP also facilitates the detection of emerging patterns in local >alerts of various kinds. > >ITU, WMO, and others are promoting CAP as the foundation standard >for public alerting is societies worldwide. It is also notable >that the U.S. FCC (Federal Communications Commission) issued an >order requiring use of CAP by all communications providers in the >U.S. (For further details, see the attached flyer prepared for >the December 2008 CAP Implementation Workshop.) > >CAP Implementation Workshop on Identifiers > >Different alerting authorities, intermediaries, and alerting >user groups are implementing CAP in operational applications. >Especially as CAP messages become available from many different >sources, implementers should harmonize how they identify alerting >authorities, alerting policies, particular hazard threats/events, >and particular CAP messages. > >This small implementation-oriented workshop among CAP experts and >users will produce a draft "CAP Implementors Note on Identifiers". >Thereafter, the draft CAP Implementors Note will be circulated >broadly to seek consensus among CAP communities worldwide. > >Mindful of the paramount importance of trust in alerting systems >and the enormous diversity and autonomous distribution of CAP >implementations, we can envision the draft Implementers Note >to discuss matters such as: > > - general requirements concerning simplicity, usability, > flexibility, extensibility, scalability, and deployability; > > > - issues or recommendations concerning distributed versus > centralized management approaches for the various types of > identifiers; > > - issues or recommendations concerning non-intelligible > identifiers (e.g., GUID's) versus more intelligible > identifiers (e.g., OID's). > >Call for Participation > >If you find these matters of interest, the organizers of the >Workshop hope that you or a representative of your organization >will participate and/or provide a written contribution on any >related topic that you would like to bring to the attention of >the participants. Participation by telephone call-in will be >supported as well. > >Please contact one of the organizers listed below if you intend >to participate, and do feel free to contact us for any additional >information. > >Also, please share this announcement with any discussion lists >or individuals involved in CAP implementation who may wish to >participate. > >Organizers: > >ITU - Tony Rutkowski <trutkowski@netmagic.com> >OASIS - Carol Cosgrove-Sacks <Carol.Cosgrove-Sacks@oasis-open.org> >WMO - Eliot Christian <echristian@wmo.int> > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]