RE: [emergency] Groups - EDXL/CAP Routing Concepts and Issues (OASIS Input of Routing Concepts IEPD Version 0.4.pdf) uploaded

Hi,

This speaks to the need to have a property concept (as in GML) that expresses the role of the geometry (area) in relation to the feature (event) of interest. This would deal directly with the question raised.

In GML one would make use of a property name something as follows:

	<abc:Alert gml:id="p1454">
		<abc:impactArea> .. polygon .. </abc:impactArea>
		<abc:alertArea> ... polygon ... </abc:alertArea>
	</abc:Alert>

Cheers

R

-----Original Message-----
From:  [mailto:] 
Sent: November 30, 2007 12:21 PM
To: 
Subject: [emergency] Groups - EDXL/CAP Routing Concepts and Issues (OASIS Input of Routing Concepts IEPD Version 0.4.pdf) uploaded

The document named EDXL/CAP Routing Concepts and Issues (OASIS Input of
Routing Concepts IEPD Version 0.4.pdf) has been submitted by David Ellis to
the OASIS Emergency Management TC document repository.

Document Description:
The current CAP standard requires the use of the "area" and sub elements to
be the union of all Area blocks.  This raises a problem for systems which
actual do GeoSpatial and GeoPolicitcal (Jurisdictional) routing of CAP
messages.  The lack of ability to label one area block as the "true" area
for alerting target population AOW (headline, instruction etc.) and another
area block as the time evolving plume from a "Hazmat" event (AOH) makes
meaningful use of CAP standard very difficult. 

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/emergency/document.php?document_id=26274

Download Document:  
http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/26274/OASIS%20Input%20of%20Routing%20Concepts%20IEPD%20Version%200.4.pdf


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration