FW: EDXL-DE 2.0 Example

This is the document
mentioned on the call. It may be a use case for RIM but it was meant to be an
example for EDXL-DE 2.0 enhancements.

 

-hans

 

From: Doug Allport
[mailto:] 

Sent: Tuesday, February 16, 2010
9:17 AM

To: Hans Jespersen

Cc: 'Elysa Jones'; 'Ellis, David'

Subject: EDXL-DE 2.0 Example

 

Hans, cc Elysa and Dave

This email provides an example that supports EDXL-DE
2.0 issues #9 (Non-XML content) and #10 (Area) from the face to face meeting. 

Please review and return comment when you return from
vacation. I plan to use this email in my EDXL and system educational efforts
here in Canada.

Example:

1.       Canadian agency A issues a CAP-Canadian Profile (CAP-CP) alert in
English to all through an open network.

 

2.     
Service
provider B captures the CAP-CP alert from agency A and electronically creates
English and French audio and short message scripts for television broadcast
from the CAP content, as well as a map image that includes a national symbol
that corresponds to the event code used in the CAP-CP alert. 

 

a.      
Note: Our
national aggregator does not convert or add value; they simply aggregate. 

 

3.     
Service
provider B packages the English and French audio and short message scripts, the
applicable symbol, and a map image with the symbol, with the CAP-CP alert, in
an EDXL-DE envelope. 

 

a.      
The English
and French audio and short messages, scripts, symbol and map (non-XML content)
or their references (in XML) are associated with the CAP alert.

b.     
The English
and French audio, and similarly the scripts, may need to be associated with one
another as being the same, except for language.

c.      
EDXL-DE 1.0
does not currently support associations of content within an EDXL-DE packages.

 

4.     
Service
provider B addresses the EDXL-DE envelope with the same Canadian recognized
location code used in CAP-CP.

 

a.      
The location
codes used in Canada are
similar to FIPS codes in the US,
and are much finer. They include every geopolitical area in the country,
including townships, towns, etc. 

b.     
EDXL- DE 1.0
does not currently support their use in Area.

 

5.     
Service
provider B publishes the EDXL-DE package into the same open network (or another
closed network).

 

6.     
Broadcaster C
monitors the open network for EDXL-DE packages with Canadian location codes
that relate to their broadcast area, from Service provider B.  They open
them and used the content in support of their distribution of public alerts. 

 

Cheers,

 

Doug
Allport

Executive
Director

Canadian
Association for Public Alerting and Notification (CAPAN)



(613)
271-1040 Tel

(613)
294-4425 Blackberry

www.CAPAN.ca