[CAP] CAP 2.0 proposal

[Jim Trawick]

For us (and others I've talked with), one of the key problems in automating
the ingestion of CAP warnings (or other warnings, for that matter) is
discerning when a warning needs updating, i.e., when does an old warning
become a new warning, without becoming a new event (expected duration
change, affected areas added/removed, etc.). The "sent" sub-element is
commonly updated whenever a warning is fetched from its provider's database,
or never updated, rendering it virtually useless for such processing.

 

To that end, it would be useful to us to have something like a counter
sub-element in the "alert" element near the "identifier" sub-element, which
increments only when substantive changes are made to the warning content,
which for sake of discussion I'll call "CriticalContentRevNumber", and
another counter which increments when non-substantive changes are made to
the warning's wording, spelling or format, which I'll call
"OtherContentRevNumber". "CriticalContentRevNumber" would be a required
entry, and would require a major revision (CAP 2.0) and would obviate
calling it CAP 1.2. "OtherContentRevNumber" could be either required or
optional.

 

These fields would be input by the warning's originator only, who would be
responsible only for determining whether, in their judgment, the change
affected the "who, what, where, when" content of the warning.

 

Jim Trawick
Senior Software Engineer
viaRadio Logo Scaleable smaller no tag no background

viaRadio corporation

3153 Skyway Circle, Suite 102
Melbourne, FL 32934-7369
321-242-0001 x113

 <mailto:robina at viaradio.com> JimTrawick at viaRadio.com
  
This email contains PRIVILEGED AND CONFIDENTIAL information intended only
for the use of the addressee(s) named above. If you are not the intended
recipient of this email, or an authorized employee or agent responsible for
delivering it to the intended recipient, you are hereby notified that any
dissemination or copying of this email is strictly prohibited. If you have
received this email in error, please notify us by reply email and delete
this email from your records. Thank you for your cooperation.

[demime 1.01d removed an attachment of type image/png which had a name of image001.png]