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: CAP Implementation Workshop on Identifiers

Thanks Elysa,

I think this is very important because it appears 
that we need to beef up our traction in Europe. 
Unfortunately, CAP appears to be our best 
ambassador in EU politics, but CAP is not much 
help with real problem with setting the stage for 
a unified approach to Emergency Management.

If the EU takes a completely different approach 
than EDXL, as seems likely from what I've heard, 
we're looking at decades of difficulties that 
prevent or maintain obstacles and barriers to 
interoperability, especially in large scale 
relief efforts that need to be coordinated 
between and amongst national and international 
agency stakeholders. Even with a more robust 
world economy, we won't be able to afford that. 
It directly concerns both medical and emergency 

Our immediate difficulty is travel and 
representation in Europe that shows our 
willingness and agreement on identifiers. Even 
such a basic issue needs to be mutually supported 
and mutual support needs to be encouraged for the 
future, but we don't have ready funding for 

I suspect that it is at small workshops like this 
that the seeds for future cooperation are sown. 
Also, I think we need to be careful with how we 
ask for funding from the Member Section. While it 
is not directly related to this, I think we need 
to invest in upgrading our investment in 
Enterprise Architect and purchase two or three 
more floating licenses so we can use it as a way 
to unify all the work we conduct, at least at the 
conceptual and presentation level. So I have a 
hard time asking for travel funding which is 
money that simply disappears, however much it is 
needed, versus tools which provide ongoing 
utility and the benefits of continuity in 
approach and in the way collateral support is 


At 5:41 AM -0500 5/15/09, Elysa Jones wrote:
>EM-TC Members,
>Please find the forwarded email below from Eliot 
>Christian of WMO.  He is announcing the CAP 
>Implementation Workshop we have discussed in our 
>Elysa Jones, Chair
>CTO, Warning Systems, Inc.
>>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
>>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
>>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
>>Also, please share this announcement with any discussion lists
>>or individuals involved in CAP implementation who may wish to
>>ITU - Tony Rutkowski <trutkowski@netmagic.com>
>>OASIS - Carol Cosgrove-Sacks <Carol.Cosgrove-Sacks@oasis-open.org>
>>WMO - Eliot Christian <echristian@wmo.int>
>Attachment converted: Macintosh HD:flyer20081.doc (WDBN/«IC») (017480D3)
>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:

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]