Biology Reference
In-Depth Information
a menu choice “Draft” in addition to the other status values to enable the
creation of preliminary templates that can be saved for use when needed.
Importantly, however, the research team recommended that message cre-
ation software be designed to prevent messages with “Draft” status from
being sent to the distribution subsystem. This would help to reduce incidents
of accidental alerts sent when drafting templates.
Other considerations identified by the research team included the need to
consider establishing unique identifiers for messages that refer to exercises and
simulations as distinct from those that refer to actual alerts. This would provide
users and system administrators with an additional degree of redundancy in
the event that the {status} attribute failed to be displayed on an end-user device.
Furthermore, there is a need to establish clear specifications and rules for using
the values “System” and “Test” within the scope of the RTBP project to ensure
that issuers and recipients are aware of when and how these are to be assigned.
14.5.5 Message attribute {
msgType
}
Each RTBP message must indicate whether it is an original alert, update,
or cancellation of a previous alert. PHIN PCA specifies enumeration values
“Alert” (to indicate an original alert), “Update” (to indicate that a prior alert
has been update and superseded), “Cancel” (to indicate that a prior alert has
been cancelled), or “Error” (to indicate that a prior alert has been retracted).
If {
m sgTy p e
} is “Update,” “Cancel,” or “Error,” then the message attribute
{
reference
} must be included in the message to provide a unique identifier of
the message being updated, cancelled, or issued in error. CAP v1.1 specifies
this as a required sub-element within the alert element as <
a l e r t. m sgTy p e
>.
CAP v1.1 further specifies that it is to be represented as one of five desig-
nated code values, each with specific meaning and intent:
•
“Alert”—initial information requiring attention by targeted recipients
•
“Update”—updates and supersedes the earlier message(s) identified
in <references>
“Cancel”—cancels the earlier message(s) identified in <references>
•
•
“Ack”—acknowledges receipt and acceptance of the message(s) iden-
tified in <references>
“Error”—indicates
•
rejection
of
the
message(s)
identified
in
<references>
CAP v1.1 requires that <alert.references> sub-element be used to provide an
unique message identifier when message type is “Update,” “Cancel,” “Ack,”
or “Error.” CAP v1.1 suggests that <alert.note> sub-element be used to pro-
vide an explanation when message type is “Error.”
