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-11) Add flood category

    [ https://tools.oasis-open.org/issues/browse/EMERGENCY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37638#comment-37638 ] 

Art Botterell commented on EMERGENCY-11:

Yes, that's the problem with subject-matter taxonomies.  Even if this group were expert in all the possible disciplines, any fixed scheme will be awkward at least some of the time.  That's why for the most part the TC has namespaced subject-matter schemes using valueList/value structures and delegated their definition to expert bodies.  Neither productive nor necessary to put ourselves in the middle of specialist technical debates.

As I recall, though, the early discussions of <category> had mainly to do with providing subscription topics for pub/sub distribution schemes.  As a practical matter they amounted more to a categorization of the type of agency/organization sourcing the alert than to a taxonomy of hazards.  This is another area where we accepted a degree of ambiguity in the interest of moving ahead to initial adoption... but the bill for that may be coming due now.

In the 1.3 world we probably need to accept <category> a-priori and tweak it as best we can.  That, however, is how the U.S. SAME codes gradually grew into a mishmash of event, response-type and administrative categories... I don't think it's the best long-term strategy.

The two-stage thought-experiment I'd suggest (in the 2.0 context) is this: If <category> weren't there, what problems would arise?  And then, viewed afresh, how best might we address those problems?

> Add flood category
> ------------------
>                 Key: EMERGENCY-11
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-11
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
> Doug Allport: I'm proposing we give Flood its own category in the next version of CAP. We have CAP-CP event references that are not meteorological (E.g. Dam breach) and our national dam association is going to propose one or more for regular alerts associated with rapid changes to spillways associated with meeting electrical power demand. We have CAP users creating their own Flood category for the management of their event references.

This message was sent by Atlassian JIRA

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