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: [OASIS Issue Tracker] (EMERGENCY-156) ETL: Insert new section 4.1


Jacob Westfall created EMERGENCY-156:
----------------------------------------

             Summary: ETL: Insert new section 4.1
                 Key: EMERGENCY-156
                 URL: https://issues.oasis-open.org/browse/EMERGENCY-156
             Project: OASIS Emergency Management TC
          Issue Type: Improvement
          Components: EDXL-CAP 
            Reporter: Jacob Westfall


Insert this content as the new section 4.1, renumbering other sections accordingly.

Â

4.1 Chosen Spectrums

Identifying a Spectrum begins with identifying a primary term (i.e. wind) and a broad term (i.e. Meteorological) and pairing them together to establish a range. The primary term needs to be an adjunct (another thing) otherwise the spectrum does not have a basis for comparison. The broad term will come from the list of CAP categories where the CAP category term applies. For example, âwindâ is paired with âmeteorologicalâ creating one spectrum, whereas, âwindâ is not paired with âsecurityâ as no identified pairing term is known at this time. NOTE: The CAP category CBRNE is broken up into its five constituent components for this exercise. The secondary event category ârescueâ is fine for a broad-spectrum end point as a ârescue issueâ is interpreted to mean an issue came up during a rescue event unrelated to the trigger event (i.e. âsuspended searchâ)



--
This message was sent by Atlassian Jira
(v8.3.3#803004)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]