Changes between Version 14 and Version 15 of Event/2012/GSoC/CAPBroker

Timestamp:

06/29/12 18:44:13 (13 years ago)

Author:

g0wda

Comment:

--

Event/2012/GSoC/CAPBroker

@@ -61 +61 @@
 d) <Reference> - if <reference> is empty, then <reference> = <identifier>; else leave whatever it already is.
     -- which identifier? :/ isn't reference supposed to refer to other alerts which are these if the field is empty? (shashi)
-e) <incidents> should be related to the same incidents list in the IRS module. Example: a mass movement that causes an accident, then incidents would be ="rock slide", "train derailment". I believe "rock slide" and "train derailment" may be archetypes of "mass movement" and "accident", respectively.
+e) ~~<incidents> should be related to the same incidents list in the IRS module. Example: a mass movement that causes an accident, then incidents would be ="rock slide", "train derailment". I believe "rock slide" and "train derailment" may be archetypes of "mass movement" and "accident", respectively.~~
+     --- err. I just copy-pasted the irs categories. This should be fixed as in they should share these things, can we find the EDXL standard incidents?
 
 
 Work flow you need is discussed in this ticket: http://eden.sahanafoundation.org/ticket/1026#no1 . Read the Attachments section and the Change History. For the create CAP Alert; specifically refer to the paragraphs beginning with Scrn03_CAP_Msg.png. Disregard the images added by Nostraa , you may get confused.
+            --> 
 
 Some notes on Scrn03_CAP_Msg.png
@@ -73 +75 @@
 
 We'll discuss the subsequent developments such as the <info> segment logic and layout when you get to that point; i.e. Scrn031_CAP_msg_Info.png, etc.
-
-
 
 * Student information: